Not really. See the support page regarding this:
As a new default, your phone number will no longer be visible to everyone in Signal. You can opt to display your phone number. However, people who have your number saved in their phone’s contacts will still see your phone number, regardless of your settings, since they already know it.
They know my phone number. Which in Europe is tied to me. They absolutely hold info about who talks to who
I get what you mean. GitHub and friends have pushed that back to a more centralized approach. However I think that it's not too bad actually. Most projects tend to be centralized too
I mean, it's decentralized alright, but it doesn't mean it's HA or automatically replicated. You can just use a different origin server and push/pull from it instead.
It's a game of cat and mouse. I'd be willing if I needed to use win11 myself but for my parents it's either gonna be Linux or a new computer
Yeah I work in tech and I'm the only one that cares enough to use Firefox. All my colleagues use chrome or chrome with makeup.
Maybe ad blocking will be what broke the camel's back, but I doubt more than a few will care enough to switch.
I hate the concept because it's just really wasteful of energy. If I recall correctly, only 30% of the power output of the charger goes into the device, versus 95+% for wired.
Dust?
Not sure about the latest Android version, but I managed to unlock and bypass a phone which had factory reset protection, and as far as I know a lot of vendors like Samsung have their own exploit available.
Using this you can manage to get to the settings app (while still locked, waiting for the previous owners google account) and remove the account, add your own or disable the security.
Done!
It's even funnier since "chat" is pronounced with a hard T at the end, and in French chatte is pussy.
So it's more like, pussy I farted
I did not yet upgrade to the latest version, but to migrate to compose I only had to copy the volume paths and the environment variables from Synology.
I can share my compose yaml by the end of the day if you need.
Before I upgrade I will try putting the cache on a SSD instead, seems it can improve performance quite a bit
From the incident report it seems the impact was limited to VMs in one DC in one region to be stopped, as the power was lost. And some service degradation in the region.
So not that much impact. Of course resources in this DC would stop working, but the rest of the region was still working properly. If you built your infra in this region in a resilient manner, your services should not have been impacted that much