The web ui with integration of email ecosystem for all those things are one of core selling points of https://sr.ht/

I’d say this list is not about moving towards FLOSS, but more about breaking up with Google services. Some replacements are betters, some worse, but definitely in each column there is at least one non-floss application 🤔

I’ve been following the software forge federation some time ago, and didn’t feel to pick up even when it was discusssed initially. It is a neat idea on high-level, though it requires forges to implement it, which has a risk of not picking up (just look at how much iterations of social media federation protocols was there, until ActivityPub arose).

On the other hand, all of the forges are based on a distributed technology out of the box: git. Most of the “modern days” comforts there are, are just built on top, and there are different ways to approach it.

As an example, you can send patches directly to the author in email. Is heavily implemented and suggested by https://sr.ht/ (1) — a software forge, which focuses on building a federated workflow by using email for communication (which is federated by design). This way, you can create “Pull Requests” without having account on the forge — all you need to do is just submit a patch. Author is very vocal about supporting it (2), and provides quite useful guides to learn (3), (4)

Generally, I’d say that e-mail is the only federative implementation you can get so far :)

What I can see clearly is that nation overall supports the warfare, and the annexation of neighbouring country — either silently, or loudly. This sentiment was there for even pre-full-scale invastion time period, even in anti-putinists circles (the “Crimea is not a sandwich” statement supporting that1).

There is an extreme minority that is against war, though they are against war in principle, and make no action to support the warfare to any side.

Removed by mod

Russian text in the video makes me very suspicious…

Neither am I. It’s just sad…

RCS is a really nice thing in principle, because SMS/MMS infrastructure is just awfully outdated from security standpoint.

Though, replacing SMS/MMS infrastructure which is internetless yet cross-carrier by making it a internet-first and tied to a single meta-carrier under the hood kind of defeats the purpose overall. There was an attempt to build an independent carrier-deployable implementation of RCS, yet it turned out to be bought off by Google :(

They have been for a while now. It’s just that now it kind of becomes obvious

Wow, thanks for suggestion of Tdarr — that project indeed looks very nice. What is. your experience using it? Any quirks?

Staying with the original also for the performance reasons: UE5 makes it really hungry for resources, while original runs smooth and makes my computer not even turn on active cooling.