“Canonical's write-up of the work done to improve GNOME is also interesting for the long list of what didn't work and how wrong some of the developers' initial assumptions were—especially regarding GNOME's use of JavaScript. It turns out JavaScript had next to no effect on performance.”


Maybe its time to boycott Conservancy and #fosdem until such time as they're no longer promoting GAFAM. I understand that the history is complicated, but in 2020 we now have a very clear picture of how toxic those companies are in a multitude of ways.

The oldies like me need to remember why they originally resisted Microsoft, and not end up rationalizing away similar or worse abuses coming from Google and Facebook. In a lot of ways the problems created by those companies are much more existential than a sweating Ballmer hurling lawsuits and office furniture.


We were not aware that @conservancy is financed by Google. Thanks for pointing this out!

The choice of including the Software Freedom Conservancy (SFC) in the paper was inspired by the role of Bradley M. Kuhn in the creation of the Affero GPL (sfconservancy.org/blog/?author).

Since an involvement of Google conflicts with our standards (as stated in our statute wiki.f-si.org/index.php/F-Si_S), we have removed the SFC from the white paper. Anyhow, they have not provided any feedback to it.

Just got proxy fall-through to Express middleware chain on 404s working in node-http-proxy and http-proxy-middleware… now working to implement it properly in forks of those packages to include in the next version of Site.js. This is going to open the door to a couple of very exciting new abilities ;)

You can be funded by Google or Facebook or some other surveillance capitalist, or you can advocate for human rights and democracy. Pick one.

Just read some JS code where they’d placed inner functions _after_ the return statement in an outer function. Now that’s legal and works well enough due to JavaScript function hoisting moving all declarations to the top of the current scope but bloody hell, people, why are you going out of your ways to write code to confuse people? :) *smh*

If you’re already running Site.js, just use:

site update

To update it to the latest version.

If you’re running it in production, it will automatically update within the next hour.

If you haven’t tried it yet, you can install it and have it up an running in the next 30 seconds from sitejs.org

First update of 2020 coming today to Site.js (sitejs.org).

It fixes an issue where automatic server reloads were not working for nested hidden folders (eg., in .get/ or .post/ folders for dynamic routes).

Just a quick update in case you miss my other toots: this fix has now landed in apt and it’s now safe to upgrade to Pop!_OS 19.10 again.

Details: github.com/pop-os/upgrade/issu

By the way, loving Pop!_OS 19.10. Snappy! And I love the fully-integrated dark mode. Yum!


w00t! Cooking on Pop!_OS 19.10 gas.

(Once the System76 folks fixed the bug I reported with the installer and released an update in record time and once and I figured out how to revert my packages to stock 19.04 – hint: aptitude is your friend – the actual upgrade process was buttery smooth. Great job on pop-upgrade, folks.)

Background: github.com/pop-os/upgrade/issu

I'd like to report a murder.

(The opening lines of Greta Thunberg's speech at Davos)

Any idea why I’m getting this error while trying to compile pop-upgrade (it’s a Rust app): github.com/pop-os/upgrade/issu

Anything obvious I’m missing? (still in trying to upgrade my Pop!_OS machine from 19.04 to 19.10 hell).

@aral And yet people buy it. The one I've talked to about it do not seem to care about theire privacy. I don't get it.

@der_On @aral

I know people who have "ALEXA", who change the room for "private discussions" - in their own house!

I don't get it.

@aral The answer from Amazon's spokerperson is priceless: "We’ll continue to invent more privacy features on behalf of customers.". You don't need to "invent privacy features" if you're not spying on people in the first place!

Warning: if you haven’t updated Pop!_OS 19.04 to 19.10 yet, wait until this bug fix lands before you do: github.com/pop-os/upgrade/pull

I’m currently running some sort of half-broken Frankenstein 19.04/19.10/half-Pop!_OS/half-Ubuntu hybrid.

Issue, with details: github.com/pop-os/upgrade/issu

Show more
Aral’s Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!