shrugal

Yes, that's basically what those schemas are about. You can create different schemas for different kinds of posts and content structures, so something like Lemmy should be possible. The Fediverse has something similar as well, but the way you introduce new schemas is different between the two as far as I understand it. In the former you'll have to adapt some features of the underlying ActivityPub protocol to your new usecase, or work with others towards extending the protocol. The later allows you to just declare and describe your new structure in a machine-readable way, and others can then choose to support it. So Bluesky is more flexible and open in that regard, but could also end up more fragmented.

ELI5:

In the Fediverse your account and identity is linked to a domain (e.g. you are @someone@domain.com), and you can't move that account somewhere else. You can't even change the domain of a server, because all the accounts on that server would be known by a different domain and be treated as separate new identifies. In Bluesky your identity is basically a random number, it's shown in the URL of a profile page for example. You can link that to a domain temporarily and get a nice user handle, but you can always move to another domain later. That means you can migrate between servers and keep all your friends and followers, something that's currently not possible in the Fediverse.

The thing about schemas is a technical detail, not really any consequences for users. Then there is a different format for user handles, so the Bluesky people don't like the double @ signs for those.

The last thing is about how you don't just pick one server/instance in Bluesky, instead you can pick different servers for different things. One server hosts your account, but a few others can fill and sort your news feed, block spam for you or let you search through content. It's supposed to create an open ecosystem for these services, and allow you to keep your account on a server that offers none of these by itself, e.g. a small home server. Of course there is nothing like that in the Fediverse, you pick a service and a server, and that's it.

I have to say Bluesky looks extremely interesting from a technical perspective, there's just the fact that it's completely dominated by the official server right now. People can create their own servers though, so we'll have to see how it evolves.

That's why we have the freedom to create different distros.

LibreY's "Framework and JS free" approach is an anti-feature as far as I'm concerned. If you really don't like those for some reason then sure, but I personally prefer getting a nicer UX with a bit of JS.

I think you're probably better off using something that's build for media servers. One really nice feature is adding more processing nodes to make things go faster, like a gaming PC while not playing anything. I don't think Handbrake can do that by itself.

I just finished setting up transcoding for my media library, and the options I found were Tdarr, FileFlows and Unmanic. They all use ffmpeg and/or Handbrake under the hood, so it kinda comes down to preference. I went with FileFlows because it seemed the most intuitive to me, and it can also process other media like photos, music, audiobooks and ebooks.

This actually IS theft, selling you something and then stealing it back!

The go-to 4-bay Synology NAS would be the DS920+, as the newer DS923+ doesn't support hardware transcoding.

Adding proper metadata to releases. Why are we still trying to decipher release titles, why not add a little metadata JSON file to every release and make the info available to the search API?

Also keeping multiple different versions of a release in Arr apps, like ebook and audiobook in different languages. Right now I'd need 4 Readarr instances to get the English and German audiobook and ebook versions of a book, and don't even think about letting them manage the same root folder!

Try SceneNZBs, they have tons of German content!

If you have Usenet try SceneNZBs

Piracy isn't even free! People pay thousands of dollars for hardware, and hundreds per year for electricity and various service providers.

But they actually get what they want for that money: Being able to watch whatever you want, anytime, on any device, in high quality and without ads. It must be really hard for streaming services to compete with features as futuristic as that!