Sven Slootweg (soft-deprecated) @joepie91@pixie.town

@jamey Aside from the obvious "honour response codes" (and probably report those back to the requester?), I think a lot of the issues can be avoided by setting a reasonable minimum interval (5 minutes?) and making sure that you only make one request per URL even if many users of the service are asking for it to be monitored. That would essentially guarantee that you make at most one request per 5 minutes to a given URL.

An addition could be to disallow or automatically delay monitoring of URLs that respond slowly, to account for the *really* intensive processes (eg. tarball generation) where even every 5 minutes would be too much.

@jacksonchen666 We'll just have to meet up at some other time and place then :p

@tachi @clarfonthey Honestly... probably neither. Sort of.

What happened to the JS ecosystem is a miniature version of what is happening everywhere in society; appropriation of the public commons, extractive businesses and capitalists taking over infrastructure and mindshare alike.

This means that trying to breathe life into it will most likely just result in doing more free labour for capitalists, because they own the ecosystem. Creating or moving to a new ecosystem, all else being equal, would just result in the same outcome again.

This is why (among some other issues) the deterioration of the JS ecosystem has made me think a lot about programming languages and their communities; I think we need some pretty fundamental changes in what "building a programming language" *means*, if we want to get a different outcome. The whole perception of both the scope of a programming language and the approach to support and community around it, is entirely based in the same "values-neutral" liberalism as most open-source, and by now we know where that leads.

I don't have any good answers to this, or at least not yet. But I just don't believe that "doing the same thing but in a different ecosystem" is going to fix anything in any sort of lasting way.

@jay The flatpak might work?

@jay Also not unimportantly, unlike the KDE client of which I forgot the name, it never freezes the UI when doing background work

@clarfonthey Yeah, it was a long time coming, I've even been yelling about it for a while already. Just sad to see that it ended up happening 'to completion'.

It's made me think a lot about the role that programming languages and their communities (should) have.

@LordCaramac @alina Like, JS is commonly seen as 'interpreted' and behaves like it from a developer perspective, but in practice it's JIT-compiled.

Common Lisp is (usually AOT) compiled but provides vastly more powerful introspection and debugging than just about anything else around, interpreted systems (!= languages) included.

Even Python can be run in a variety of modes; there are forms of Python which can be JIT-compiled, or even AOT-compiled.

@LordCaramac @alina I'm not sure what exactly that's in response to, but it doesn't seem very relevant nor particularly correct? The strict dividing line you're sketching here hasn't existed for decades.