It's not weird. I'd appreciate it if it were me.
Only in the same way that stealing code from a PoC would make me racist, stealing code from a Jew would make me anti-semitic or stealing code from a woman would make me sexist.
Since, without proof of any of that you're just making shit up I'm going to go with the reason that your post is being downvoted is that ITS JUST FUCKING STUPID.
Why unacceptable? As the runner of an instance I get to have control over my own little walled garden - it's literally the primary strength of federation. If anyone, at any time, is unhappy with the content moderation policies of the admins of their Mastodon/Calckey/Peertube/Lemmy/kbin instance then they are able to find a new home - or maybe start one of their own, like dbzer0 did.
From what I've seen the authors of the papers have listed the zenbleed mitigation impact as "statistically insignificant".
I imagine Larian care. Especially since they're pushing Steamdeck support.
The reason this is a "supported platform" issue is that the developers of Hogwarts legacy know their supported platforms support XeSS, so any work that is not "just turn it on" is additional work for no gain.
LinUX iS nOt A sUpPoRrtEd PlaTfOrm
I see that you, like me, always ends up with a few screws left over 😜
When you login initially it offers to follow all your Instagram follows. Even if they've never logged in. Its creating shadow accounts for all of them.
When they login initially they find they already have a bunch of followers.
So it's not all of Instagram. It's just all the people who've tried it + all the people they tried to follow.
Not to mention that the defacto package manager (composer) blows NPM out of the water in basically all metrics. From what I understand most languages package managers now look up to or even model themselves on it.
Large parts of my particular departments .gov.uk stack are PHP. All modern (8.1+) using established frameworks and to be honest, it's a joy. It's quick to write, easy to understand and very easy to test. The write, run, debug cycle is also essentially instant; although I really enjoy using Go (another bit of the stack) being able to quickly iterate changes is something I absolutely miss when I'm using it.
Laravel + Livewire is some sort of dark voodoo magic. I can write only PHP and have a functioning SPA with push updates and all sorts.
It has one. Minus an undocumented step (that's sat fixed in a pr). Bringing it up amounts to 4 lines in a console; 1 to bring up the stack and 3 to start a JS watch for asset compilation.
For an organisation hosting as many companies data as this one I'd expect automated tape at a minimum. Of course, if the attacker had the time to start messing with the tape that's lost as well but it's unlikely.