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.

That’s a vibe for sure

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

This one was actually hard to spot!

Amazing.

I assume the thing is a representation of some software, so bloated it can barely be considered functional

When you want to get more understanding about the comic you can try and check the site, there are descriptions for each image, in this case:

This is one of the cutest, more adorable, murder-bird I’ve seen in a while~

Did she tell you why she was doing it or did she only give you some platitudes and thanks?

Because a lot of people are not used to be talked to, and even if they are all rage inside the car, they get scared quite fast when someone fully geared on a motorbike knocks on their window - and tbh I think it is pretty understandable.

Still, good on you, I usually just let them go and change road - when feasible. There’s no need to waste a good riding day with some knucklehead.

On the contrary, in my opinion if they are clearly labelled as a joke, they are a great way for people who don’t understand them to ask why and, in the process, being a little more informed on what not to do and what it’s dangerous.

Especially because there’s really no risk of emulation in this case.

Could you consider using ISO 8601 style dates (YYYY-MM-DD) ? Or words for the months?

Aside from that: great job!

Probably, but I want to point out that the - arguably - most important, intelligent and charismatic character in all of Star Trek lore is an Irish too.

You should consider the option of a semi-stable release cycle, like every second thursday you get all the minor improvements/not urgent fixes and slap them all into a new minor patch version (or even an alternate github beta/full release cycle, making the updates for the normal users a monthly occurence).

This is good for both not overwhelming the systems like gplay and f-droid, and for the users who could end up with update fatigue. And more time to cook the features is always nice to have.

You can always share blog like posts here and use them to talk about what you are working on in a more ground level. This can both be good for engagement and for you to learn how to better share technical subjects with the general public (IIRC you were doing this mainly as a learning effort?)

These are, obviously, just my two cents so take them for what they are worth.

Thanks for all the work!

Per chi non lo sapesse, l’app è anche presente su F-Droid, dove è sempre gratuita: link

Il codice sorgente dovrebbe esser su codeberg (link) per chi volesse compilarla da solo o avere maggiori informazioni.

Credo non vi siano differenze fra le due versioni, eccetto il fatto che per partecipare alle Beta bisogna avere la versione Google Play. Ma potrei sbagliare.

EDIT: Al momento di questo post la versione F-Droid sembra esser indietro qualche patch (2.13.0 invece di 2.13.3), che è abbastanza tipico per la piattaforma. Changelog

Because, as pointed in the page, Servo is being developed as a(n embeddable) Rendering Engine, not as a full blown end user Browser.
Its alternatives are not Chrome, Safari or Firefox, but Webkit, Blink and Gecko

There’s an example GUI called Servoshell, but it is more of a testing ground and example on how to embed the engine in an app than a serious alternative to anything currently in the market.

Already this kind of work is difficult and daunting. Adding to it a full GUI would make it completely impossible for the current size and financial backing Servo has.

Big words aside it just means that Servo wants to be only one of the parts that compose a real browser: the one that takes HTML, Javascript, WASM and translates them into the things you see on your monitor. All the user facing functionality are left to the devs of the app that embed it.

I feel there’s some kind of miscommunication going on here.

Probably I’m not understanding what you are putting forward, but to be clear: They are not doing this because they want to. They are doing it because they are forced to do it by the DMA.
It’s true that allegedly they were working on some kind of interoperability layer already. For years now. But no evidence of it being more than lip service to avoid being regulated has ever surfaced - as far as I know.

Which would have been in line with your “Do Nothing”.

as an unwilling Whatsapp user the ability to migrate without having to convince all my social circles to do anything but check a checkbox sounds like a huge step forward.

That’s the point. I feel it will not be a “simple checkbox”, and they will make it the most obnoxious process they can using the Best Dark Patterns the industry has to offer.

Already the general public is not interested in the alternatives or the concept of interoperability - wanting something that Just Works™ - putting in front even the smallest step (and some scary text!) will make the percentage of willing people become even lower.
And that’s not all. As it is portraited in the article by the Threema’s spokeperson it is pretty clear that Meta will just try to make the maintenance of the communication layer as cumbersome as they can - both technically and bureaucratically.
They are explicitly the ones keeping the reins of the standard, the features, the security model, the exchanged data and who, how and when will be approved.

So from one side if they make it hard and scary enough to tank the use rate, they will have the excuse of not being there enough people to give priority to fix it or add features, and from the other side if maintaining the interoperability will be difficult and time consuming enough, the people and businesses from the alternatives or wrappers will not have the incentive to do or keep doing it for the long haul. As we can already see in the article.

Is it better than nothing? Sure, probably. Will it be a slow cooking, easy to break, easy to get excluded from, just bare minimum to comply to the letter but not the spirit of the law? I feel that’s a pretty good bet to make.

Let’s be clear: I will be extremely happy if all the red flags and warning bells that I saw in the article will just end up being figments of my imagination. But yes, I’m very pessimistic - maybe even too much - when I see these kind of corporate speech and keywords.