No. The rate limit doesn’t work as they use huge IP Spaces to crawl. Each IP alone is not bad they just use several thousand of them.

Using the API would assume some basic changes. We don’t do that here. If they wanted that, they could run their own instance and would even get notified about changes. No crawling required at all.

The article links to 4 incidents that are reported on Hackernews. So yes. At least 4

You can bypass it by changing the user agent to not include Mozilla in the beginning.

Probably because the creator had a blog post that got shared around at a point in time where this exact problem was resonating with users.

It’s not always about being first but about marketing.

It also is an option to ensure everyone has the same dev environment.

Matrix still has it’s problems. All the meta data is still saved on every server permanently.

There is still space to improve from there.

It’s possible to stream from jellyfin without an account. Jellyfin should not be connected to untrusted networks, like the internet. Several API just don’t check the key or don’t require one in the first place.

https://github.com/jellyfin/jellyfin/issues/5415

Here is some more context. Are they biased? Probably in some shape or form.

Some of these are bonkers. The argument not to fix them because of backwards compatibility is even wilder. Which normal client would need the ability to get data for any other account that it hasn’t the Auth token for.

I don’t like the interface for setting up flows. Feels needlessly complicated.

Be the change you want to see.

That’s exactly what the cloud is good for, just use a cheaper holster like hetzner for it.

Rust libs for use in the kernel need an extra approval. But it turns out, whenever it’s easier to just include a dependency doing what you need, instead of writing a bad version of it yourself, most people take a dependency.

For the second step there is git blame-someone-else

No. Unless you use waydroid

crash from undocumented function parameter invariants

My favourite, as that was the exact point the dev was making in his talk, that the stuff is badly documented and that the function signature would document it perfectly.

Forgejo is working on that, but it’s not there yet.