Sven Slootweg @joepie91@pixie.town

(I don't really give a fuck about companies deciding to build on unpaid labour and getting burned in the process, but this stuff affects other people too, building community projects - often people who do *not* have copious amounts of time on company dime to fix and replace things later!)

Corollary: don't make your project website look like "a project that's in it for the long haul" if it's just meant to be a short-lived hobby project. Again, hobby projects are completely fine, but you need to communicate that that is what it is!

Please stop making "alternative to <other thing>" projects with no further information! Why does it exist, what is different about it, when and why might I want to use it instead, when and why should I not?

It's okay if the answer is just "it's probably not better, I just wanted to make my own thing" but then *say so*! Don't leave me and many others guessing what the purpose is, spawning all sorts of imagined differences and other misinformation as people try to explain away the existence of two options

Yet another bunch of people trying to make a quick buck off selling scammy products by misusing activist and anarchist aesthetic and rhetoric: https://activiststoolbox.com/

These same people are advertising on the website of the The Light paper, a fascist conspiracy rag in the UK.

Fuck people like this, honestly. Going off some of the text on the website, I'd not be surprised if they are trying to draw people into conspiracy shit *within* activist movements as well, so probably keep an eye out for them.

I swear, every time I see people bringing up 'spirituality' within supposedly leftist activist movements, it's some thinly veiled bullshit like this...

CNBC, this ostensibly economics-focused broadcaster, has a series of videos on YouTube analyzing why companies went to shit, and it's kind of funny how the conclusion is basically "because capitalism" every time

Once again I am being baffled by the Rust compiler giving me errors that make no sense because it seems to be doing some sort of implicit interpretation but isn't telling me what, so I can't reason about it

Ik zoek iemand om (grassroots) activistische dingen mee te organiseren, dingen die niet alleen maar een demonstratie zijn maar ook echt iets effectiefs bereiken, want ik begin me toch steeds hopelozer te voelen over de richting van de politiek.

Voor de volledigheid: ik kan niet meedoen aan dingen die illegaal zijn, om redenen. Dat laat nog genoeg opties, en ik sta voor een hoop open, maar ik kan het niet alleen.

(Graag alleen reageren als je interesse hebt om persoonlijk en actief ergens aan samen te werken, aan "hee kom eens naar <willekeurig activistisch cafe>" heb ik momenteel niet zoveel)

Hot take: if a company builds a product to be dependent on a service they run, then they should be on the hook for running that service for as long as people want to use the product, actually, even when it gets really old and expensive.

If you don't want to be stuck running an old service, then don't make your products dependent on it. If you choose to do so anyway, then that is *your* business risk, don't make it the problem of your customers.

I don't expect that this rewrite is going to be accepted as a PR upstream, given how significant the changes are, but in the worst case I just publish it as a fork :)

Despite the complete internal rewrite, and the move to async iterators instead of streams and promises instead of callbacks, it actually doesn't break any of the existing API; it's fully backwards compatible (and still passes all the original tests aside from some internals tests).

The new features probably won't all be supported with the old API, but internals improvements will.

Project status: nearly done with my LevelGraph refactoring, now I have a version that uses async iterators and promises and that should be much easier to extend with support for statement-level annotations and other neat features (without breaking stuff)