It's a thing, it happens a lot and Lemmy instances have the same problems to fight. Unwanted porn in my eyeballs is sadly a not uncommon experience until you've put in effort to set up blocks and filters on your personal accounts. Peertube being explicitly video based is a natural target for porn pushers.

    media.autoplay.blocking_policy
    media.autoplay.default

[1] https://ziggit.dev/t/migrating-from-github-to-codeberg-zig-p...

It would appear they listened to that feedback, swallowed their ego/pride and did what was best for the Zig community with these edits. I commend them for their actions in doing what's best for the community at the cost of some personal mea culpa edits.

In short: the complete lack of user-facing easy to use controls for data retention and culling in the Matrix (Element) clients is a deal killer for me. That painful experience taught me a lesson - now when I test something new, one of the first things I look for is "how do I extract from this thing?". I never want to go through my Matrix extraction pain again, so a personal life lesson was learned.

(a) the encryption between using a mobile and the webapp desyncs/breaks all the time, it just sucks. I mean you'll get "cannot decrypt" a lot, have to bounce back and forth and generally try and force it to re-sync properly again. Sometimes never worked at all. Lots of issues on GH over the years.

(b) as mentioned in this article, insane delays on new message notif and sending and receiving. Just logging in on the webapp every morning took minutes of some sort of mysterious sync process, often the mobile app had the same problems. The X stuff may fix this, we were pre-X.

(c) cleanup. There's no message retention set on matrix.org, when I wanted to extract and remove our past chats the process and experience was excruciatingly bad. It took tens of hours over several weekends of the webapp (mobile completely non-op in practice for this) polling and loading old content, just so I could select 100 at a time to delete and then it took an hour. Once I started culling back over a year or so, the loading got longer and longer and longer, until eventually it 100% stopped working at all to load old messages.

Signal and DeltaChat are far, far better experiences for one-on-one chats with friends & family. The Delta client is a bit UI/UX behind but not horrible; e.g. you can't correct a typo in a sent message in Delta, unlike Signal - because each msg is a unique gpg-encrypted "email" rather than a database object that can be re-manipulated.

Do these alternatives compare with just how well UWB serves regular, normal daily activity like this? Because to me, what I have is absolutely excellent in use with daily routine.

[1] https://mastodon.social/@_elena

Tangent, a friend and I started using Delta Chat with a chatmail relay and it's incredibly friendly to get started, and hides the fact GPG tech is being used from the user; one can export a bundle of the key data as needed and easily copy the key profile to a second device over local wifi (I was impressed at how smooth it was).

Not that I've kept track, but Delta Chat's UX is probably the first easy, no-nonsense implementation of using GPG tech as a foundation but keeping it away from the user experience I've encountered (and liked). It has it's pain points but I mean it just works and my buddy and I chat all day over it using a public relay.