no they didn’t, yes it could have happened:

1. GCC: exists, not too good messages
2. rust gets made
3. rust gets popular
4. gcc error messages get improved by good example of rust

gcc is not a dead project. it is continuously maintained. its improvements can be influenced by other projects like rust

I think they didn’t enshrine the right to end to end encryption, it’s just that they did not renew the temporary law allowing voluntary scanning for tech companies

yes, it was that the phone was saving notifications to a database, because the notification history feature was not disabled by the user. but that affects non-push notifications too, and it only becomes a problem when your phone is compromised (malware, including police malware)

but if you don’t trust your phone with not leaking your notifications, you shouldn’t trust it not leak what you typed in and what you watch on it either, because the operating system has access to all of these too. in that case you are looking for a better phone brand, maybe even a custom rom that’s known for privacy

they didn’t say otherwise

preferring Rust over Rust? what do you mean?

do you think loosely typed python is easy to read and maintain?

an llm slopbot generates messages that are leagues more coherent and easier to understand

first result now in ddg

Edit: I figured out what was confusing me, the MEP just recently enshrined E2EE, which I remembered as a big win on the same level of no age verification.

oh that sounds interesting! could you throw a link?

one more thing: its not actually irrelevant for privacy whether lemmy sends our public comments across google’s push service. we are not anonymous, but we don’t use real names either so it’s partially private, but when google connects your notifications (or just the timestamp of them with comments here), they will be able to figure out what is your account. they can use that information for stalker marketing or give it to the authorities later on

ok. push notifications don’t universally leak your data. apps can receive either the message contents in the push notification, which is unsafe (less so if encrypted), or a ping that there is some kind of a new notification, upon which the app can connect to the server to fetch them. Popular messaging apps probably do the former for some reason. in mattermost its configurable by the server operator but defaults to leaking data. safe messaging apps don’t do this, they just send an empty notification or such, and the app checks in for updates. signal and matrix are like that, but in both cases they wouldn’t even be able to send the message when it is encrypted.

but back to voyager: to be able to use push notifications, the server needs to send them. Lemmy does not have the capability for that, probably not even in the 1.0 version they are working on. so the way for Voyager to fetch notifications is to check in periodically instead of using a push service.

not much better than eye scanning.

also does not solve the gifting problem, because normally you don’t know the ID of your friends

wait, I think maybe there is a misunderstanding in what happened in other apps. you are referring to the signal notifications thing, right?

oh, I thought OP’s point is Voyager does not even want you to bother with notifications that could make you more addicted

edit: someone else has taken it that way too: https://europe.pub/comment/7070900