It is already amazing!

I actually feel this is gonna make it harder for people to find out about the change, having something suddenly disappear from your feed is less visible than having reminders when you click on a new post.

At the same time, cosidering the .org one is new, not a lot of servers/instances will have the community federated, so it will not appear even in the All feed for people, especially in the small ones.

For those reasons I would advice for a transition period, if possible, but I can see how it could be annoying to manage.

If I can make a suggestion:

it would be useful for the time being if - in the comments of the posts that will inevitably still be made here - it could be added a crosspost to the new community. Or a bot automatic message.

Russia is actively in Syria from the end of 2015 as an official belligerent, it’s not something new for Russia to fight directly while others use only proxies.

But I can see your point; still - officially - this is only a three days military operation. When that stance will finally change in the official channels, it will mean they can’t hold the mask anymore.

Just out of curiosity, is the mouse bluetooth?

I heard there are some intermittent problems with them on linux because of proprietary blobs and similar driver issues, but I’ve never had one, so I’ve no direct experience.

I find it funny that this is the first video where I’m consistently getting the “This helps us protect our community” and “Log in to confirm that you are not a bot” errors while using an alternative Frontend.

I’m sure it’s just a random coincidence, but it is still funny to me.

This was an interesting question, so I took a quick dive in the docs, it seems it has an S3 integration to help with it, and some comments on the various supported services

More info here: https://owncast.online/docs/storage/

Still, depending on the chosen provider and the amount of viewers, it could be quite costly

It’s an error with a dependency written in Rust, the workaround is to use an older toolchain (1.72), it is fixed in the newer code of tokenizers, but probably it is not updated in AUTOMATIC1111 yet: you should check their bug tracker

To have more info you can read this issue: Link