(#kfr5vja) If Sam Altman really wanted "AI" to be in the hands of the people, he a) Should not have made deals with multiple devils that turned OpenAI into a proprietary company. b) Sold most of the company to Microsoft.

hey @oevl you're still around right? I'm not imagining it 😅 How are ya? 🤔

(#l2uil4a) @prologic @movq @bender Yup, I second that. :-) We went to Ebersberg Castle with the scouts. It was great fun and very exhausting at the same time.

(#ghroc5q) @movq People just don't ask these questions. It's really a serious privacy issue, and I don't see it brought up very often. Not even in privacy-minded circles. If you're using a proprietary operating system on any Internet-connected device, you need to assume that the vendor can see everything you do on it and maybe even what you do on other devices as well..

(#yonaqra) @mckinley Looks pretry interestinf 🤔

(#ghroc5q) Actually, it looks like notifications using Google's service *can* be encrypted end-to-end. I don't know if this is used much in practice or if you can tell if the notifications on *your* device are encrypted. There seems to be some conflicting information out there. Even if the content is encrypted, though, you're still giving quite a bit of metadata to Google by using their notification service.

(#ghroc5q) It looks like ntfy.sh can work either through the OS's notification service or by maintaining its own connection to the server in the background. For privacy, you definitely want to use "Instant Delivery" and self-host the server.

(#ghroc5q) @movq I haven't done any app development, but I know notifications on phones are indeed dependent on cloud services run by the OS vendor which talk to servers run by the app vendor on your behalf. This is supposedly better on battery life, but it conveniently lets your OS vendor read all your notifications. Mobile XMPP clients usually implement notifications using XEP-0537 and it goes like this: ``` Your XMPP server -> Client vendor's notification server -> Client OS notification server -> User's device ``` It's not end-to-end encrypted so servers will usually just send a dummy message through (You received a message from juliet@capulet.lit!) so you have to open the app to see the (hopefully) encrypted message. It's a similar flow on both iOS and Android and I assume Matrix clients work the same way.

(#hw74veq) Sorry folks, it was a total disaster 🤣 Had to disable the new feature 😢 - ran out of disk space - blew up the db on this pod (_corrupted_) - lots of missing features and. broken shit™

(#2nqa6vq) And we're back!