Knusper

I mean, I agree with that. Maybe "non-committal" isn't necessarily the best word. I'm mostly saying, assuming that POs realize backlog won't get prioritized nor they'll be gifted money to work on it, they should lean into that fact more.
They could sort backlog for chance of ever becoming relevant enough again and then delete the lower 90%.
Or I don't know, any card that sits around for more than 6 month is deleted. I've rarely seen an issue older than 6 months that wasn't wildly outdated anyways.

Or my preferred flavor of chaos: If it's actually a problem, you don't need a card on a board to remind yourself of it. You want a card for the when and how, but not that you need to do it.

I know, lots of services are currently going to shit, but quite the timing with Bandcamp imploding, too...

Thing is, most people want to listen to copyrighted music. Federating copyrighted music is a surefire lawsuit for anyone who hosts that federated service.

And you don't need federation for acquiring music files. Torrents are better for resilience than federation, since they form a distributed network, not just a decentralized network.

There is a piece of software that implements federation for music, called Funkwhale.

This is their flagship instance: https://open.audio
That flagship instance hosts basically only Creative Commons music and podcasts, due to aforementioned problem.
The other instances I've seen federating with it, were generally self-hosted by musicians or podcasters to share their own work.

I imagine, if an instance started federating copyrighted music (which wasn't separately licensed by the artist either), it would need to be defederated by everyone else in the network ASAP, to avoid lawsuits.

I always kind of hated how non-committal POs were with that. It seems like any experienced dev knows backlog is effectively /dev/null. So, if you actually treat it as such, you can skip refining stories that will not be tackled any time soon and you can purge stories from backlog aggressively (or work with filters to hide them), so that your board shows actually relevant stuff.

But POs will always be like, oh no, we can't delete this story that we spent all of 5 minutes to write. It might still be relevant. We must remember that we still need to do this (and then not do it anyways)...

I imagine, they stretch this out over a longer period, so no shitstorm forms...

Bro

I hear, it's so potent, you can dilute it all you want and it remains just as dangerous...

For the past few months, they have been rather aggressive with IP bans for Piped instances, yeah.

Or just make it a GIF, for when you're trying to cross during rush hour...

The GDPR literally does not apply for non-personal data. I don't get why companies are so ridiculous with their cookie banners. Nevermind that they have no qualms violating the GDPR in plenty other places.

Well, I'm not just talking about issues.

everything looks good, time to run it

This sounds like they did not or could not explicitly compile it. Pretty much all popular languages are compiled. JS isn't, but people are less likely to say that they 'run' that one. Ruby isn't, but it's not as popular as Python.

Well, and my preferred version of "everything looks good" is "everything compiles", which with a strict enough language does also make failure during the first run much less likely.

I'm also not saying that these aspects are unique to Python.

The language failing to tell you where the issue is also happens in JS/TS, C/C++ and I'm going to presume Ruby, too.
Python is just again rather popular and some of these choices don't make sense with my first hunch.

I am not saying that you don't get frustrated at your work in other languages. I'm saying this particular frustration is characteristic.