Alonely0

@PrivateNoob @FragmentedChicken I think it's because graphene isn't done with the porting yet, because other features of the lockscreen like the shortcuts are also gone. They said that there was more work to do, so we'll see...

@ijeff that cuthole selfie camera is giving me so much OCD...

@phillaholic carriers have to "approve" updates; Google, Samsung, or whoever is your vendor can't actually push an update because the carrier must sign it with their key. Was it Google's fault for the vuln? Yeah. Was it AT&T's fault for your update to take 1 week longer to roll out to you? Yeah.

@phillaholic @ink if it takes a week for an update to get to you, you can blame your carrier for that. Google pushes updates very quickly to unlocked phones.

@el_bhm @floppy you americans are making a fool of yourselves in these threads, there are tons of comments about whatsapp being old or only for drug dealers & sex workers, and it's so funny how out of touch with the world outside of your borders y'all are. In basically any other place of the world; universal messengers like WhatsApp, Telegram, or WeChat are the de facto standard.

@recursive_recursion @snaggen It's just a glorified text editor, if it gets too bad it's not like your hands are tied.

@TheMadnessKing @floppy in Europe for most people iMessage is just the SMS app. Even though it pisses me off that Apple got away with it, having WhatsApp to comply with this is just huge. Everyone here uses WhatsApp, and now I won't be forced to leave Signal anymore.

@Hikiru @Squizzy I live in Spain and I'm planning to move to Denmark or Norway in a few years. Heat is impossible to manage here, and the political system is almost beyond salvation.

@snaggen the actual answer is having opt-out semver checks on cargo publish just like with git.

@thanevim @dantheclamman @kubica Unfortunately, that's not something you really wanna do. Depending on your domain, it might take years before your emails stop going to the spam box.

@ladfrombrad @QuazarOmega Root + trackercontrol + adaway does wonders

@soulsource @anlumo dude your whole code is UB. A reference & means that the data behind it never changes while any reference exists, allowing multiple pointers to point at it at the same time (aliasing); whereas a mutable reference &mut means that the data behind may only be read or written by that pointer, i.e. multiple pointers (aliasing) can't exist. The compiler uses this to optimize code and remove stuff that you promise never happens. Always use miri, and go read the nomicon.