Show more

Folks, you know those things you share with me privately about the shit that’s going on in the industry and in the orgs that are supposed to be fighting for our rights… can you please start sharing them publicly too? I appreciate the info but we need more than me speaking out.

Me at the start of the week: “yes, Site.js absolutely needs proxy fallback on 404s and I will bend WebSockets to my will to achieve it in a manner that’s compatible with Express middleware and we’ll be able to extend any existing server and rein in a new era of URL-oriented programming and it will be glorious…”

Me at the end of the week: “yeah, no, apparently not necessary. Can achieve exactly the same thing for our actual needs today by supporting multiple web roots in Site.js”


Nothing like realising that the feature you spent the whole week struggling with implementing actually isn’t necessary and you can achieve the same thing differently and far more cleanly. Oh, well, that’s development :)

@fsi @aral @xerz @fsfe @conservancy Like that Privacy Conference at the University of Amsterdam some time ago. Main sponsors were Google and Palantir.

So @laura scoured the App Store and updated our reviews page for @better today.

Thank you to all the wonderful folks from 26 countries who made us smile. I guess we’re what you’d call critically acclaimed but not financially successful :)

@aral @xerz

We did not suspect that Google is since 2013 not only **a** sponsor, but **the main** sponsor, of the Free Software Foundation Europe @fsfe : . Thanks for the hint!

This is like if ExxonMobil was financing Greenpeace.

Just like for the SFC @conservancy above, we removed the #FSFE from the white paper.


When Google corrupts your politicians, your schools (#GSuite), your newspapers (#GNI), your web, your emails, your universities, .., you expect ".org"s like the #FSFE to be your last resort and to defend you.

But when you discover that also the FSFE is financed by Google (2013-2020), it is finally time to #panic:

#rms & #FSF fought #Google even in court:

Is the @fsfe in the position to do the same?

@FuckOffGoogle @aral

Apologies if any of you encountered a garbled page upon becoming a patron of Small Technology Foundation within the last week (instead of your patronage management page, which you can use anytime to change your patronage amount, pause it, or cancel it). We just caught a regression that was introduced by the addition of metadata in the header automatically pulling in a template variable placeholder for the main body of the dynamic content on that page. It’s now fixed :)

“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 (

Since an involvement of Google conflicts with our standards (as stated in our statute, 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

First update of 2020 coming today to Site.js (

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

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!