XMPP basically uses the same end to end encyption method as Signal, but due to it not being mandatory some things are easier but come with the footgun that you can accidentially disable it (but it is enabled by default in most modern xmpp clients).
Otherwise: since XMPP federates more servers can theoretically see some metadata, but since most servers are small and community run there isn't a single big target like with Signal where you can siphon off all the metadata. So you can make arguments for both. XMPP: more meta data but decentralized, Signal: less metadata but all in one place.
Security researchers always look at a specific thing, usually the encryption only. The message encryption of Signal is great, the problem is all the rest of it that never gets scrutinized that closely.
Hmm, not sure how they did it. To my knowledge that is only an upcoming feature although now that I think about it I somewhat remember that it was already partially available in the current release backend but not exposed in the UI or so 🤔
Mastodon etc. doesn't really differentiate between posts and comments. So imagine your Lemmy feed having all comments from all communities you are subscribed to just there scrolling through and no real way to know what they even comment on without clicking though to try to find the originally referenced message.
In addition Mastodon has no concept of consistent threads, so basically every person sees something different and you can't really comment on comments without it getting completely confusing.
No, have a proper separate view that only shows group posts like on Lemmy. Friendica and Mbin does it like that and Pixelfed has teased the same for a long time now. No work-arounds and semi-working hacks like now when you try to engage with a Lemmy community from Mastodon. But that you even ask how should show you just how incompatible these two social media concepts are. Basically you need two entirely different interfaces for each.
IMHO better would be the reverse: proper group support in Mastodon, Pixelfed etc. But the developers of these seem to be as reluctant to implement that as the Lemmy devs are regarding user microblogging.
Well, would it make sense for Peertube to add this?
It's just an entirely different concept of social media and while I personally would not be against adding it to Lemmy, I also do not miss it here and can understand that the devs are not enthusiastic about implementing it.
This has been long discussed and deemed part of a problem space that Lemmy isn't meant to solve. So probably never.
But there are Fediverse apps like Friendica or Mbin that support both, and it lookes like Pixelfed is going to sooner or later support the reverse, i.e. subscribing to Lemmy based groups.
Quick question: do you know if multiple hardware accelerators can be used in parallel? Like a Intel Quicksync and a Nvidia card, or two Nvidia cards etc?
I am still looking into it but it seems like the Peertube hardware transcoding extension does not support Quicksync by default and you need to use some fork or so.
There are some self-help chats (usually on Discord, IRC or Matrix) with other admins that you should join to get a feel of what typical problems arise and how to fix them. But it is usually not that much of a deal and you seem to be already on a good way.
Specifically for ActivityPub and other federated services it is important to know that even if there are only few people using your server the remote federated activities can have a quite significant impact on the performance of your server and RAM/Storage requirements.
Remote federated servers also usually "remember" who they talked to via special cryptographic keys and so on, meaning that if something goes wrong for some reason it might not always be possible to just delete everything and start new from scratch on the same domain as the remote servers will refuse to talk to your "new" server. Just something to keep in mind and another reason why backups are important.
If all you need is a photo backup solution (and for many people that is true) then Immich is a far more polished and less janky option. Nextcloud is a typical "jack of all trades, master of none" type of software.
In your example Immich is an alternative to Nextcloud that is more specialized. If you already run a Nextcloud there is no real need to run Immich indeed. But in reverse you might not need all the features Nextcloud provides and Immich would be a more streamlined alternative for sharing and storing images.
The tide lifts all the boats... there is also a noticeable uptick in Lemmy registrations, at least here on our instance.