@alcinnz "running bloated software & webpages" is a huge contributer to climate change, wish people would realize that.

Someone close to me works for AT&T and they realized they would run out of energy to supply their growing server farms, so they put research and dev into fixing it and they did, for now. We need financial incentive to solve this on a large scale, a tax on shitty software perhaps (like carbon tax? lol

@freakazoid I think a lot but not all of this comes down to corporate propaganda.

But there's been a lot of promising developments recently in p2p. We just need to turn it into something useful, and stop focusing exclusively on blockchains!

@alcinnz I do find it interesting that even as it has become cheaper and more efficient than ever to have local storage and computation, we're centralizing it more and more heavily.

But I think Rob Pike had a point when he said he wants no local storage anywhere near him except maybe caches. Managing redundancy and backups is *hard*. And any p2p storage system that a) I would trust and b) mere mortals could be comfortable with, may not be very efficient energy-wise.

"rich" is a Python module for laying out rich text on the commandline, which I'd like to describe today. To continue my exploration of text rendering.

I won't discuss it's integration of pprint (pretty printing Python literals), Pygments (syntax highlighting), CommonMark (Markdown parsing), or Jupyter Notebooks any further than I just did.

And nor will I cover convenience APIs, in favor of the core logic.

I doubt it's much different in commandline browsers like Lynx.

1/

Don't get me wrong, computers can absolutely help us regain our environmental efficiency. They just *aren't*.

Not as long as we're:
* constantly syncing everything to the cloud,
* expecting same-hour delivery,
* funding our clickbait via surveillance advertising,
* buying a new phone every year,
* using AIs because they're cool rather than useful,
* running bloated software & webpages,
* buying into "big data"
* etc

Computing is environmentally cheap, but it rapidly adds up!

Show thread

Computation is a privilege that maybe we should not automatically extend to websites. Like the camera, or local storage.

@alcinnz way ahead of you. a supermajority of my website experience is broken already because I block googleapis.com from resolving.

That's how much of the web relies on these people. It's sad.

today's unlucky item is:

a link that's not an <a> and takes forever to click because the web site is designed for snails

Can the exfiltration of personal data by webtrackers be stopped? - Freedom to Tinker: freedom-to-tinker.com/2020/07/

Personally I like that option of a fundamental fix! Put first first & third party resources on a much tighter leash, at the cost of breaking popular websites.

Consider the following:

// In module "foo"
def example = enum {
OPTION_A,
OPTION_B,
};

// In user code
use foo;

let x = foo::example::OPTION_A;

Too verbose?

Show thread

We're making a new #Free and #OpenSource #logo!

Feel free to join us if you want to contribute to the logo! The logo will finalize the 17/07/2020.

framagit.org/reverseeagle/proj

#gpl #FOSS

@aeveltstra HTTP2 & 3 attaches identifiers.

In HTTP1 the second request flows through a seperate socket. Though many servers will indicate in their responses ("Connection: keep-alive" I believe) you can then reuse that socket for a new request, saving some overhead.

@aeveltstra Traditionally we opened a handful of sockets simultaneously connected to the same host. Now HTTP 2+ adds additional data to it's responses so it can be a single socket.

CPU Bugs: danluu.com/cpu-bugs/

Earlier I described the story as: when CPU's transistors got faster and faster than RAM's capacitors, optimizations were needed to address that bottleneck. Optimizations which get tripped up by conditions, so more optimizations were added to address that. Then we found these optimizations were vulnerable.

But as described in this link, that's ofcourse not the full story.

Show more
FLOSS.social

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).