@movq@www.uninformativ.de 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..
@mckinley@twtxt.net Looks pretry interestinf 🤔
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.
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.
https://docs.ntfy.sh/faq/#how-much-battery-does-the-android-app-use
https://docs.ntfy.sh/faq/#what-is-instant-delivery
@movq@www.uninformativ.de 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.
yarnd
😅 Let's see how many bugs I've created 🤣
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™
And we’re back!
@news@twtxt.net And we’re back!
👋 This Pod (https://twtxt.net) will go offline for ~15m shortly, while I perform an offline index of the archive.
👋 This Pod (https://twtxt.net) will go offline for ~15m shortly, while I perform an offline index of the archive.
yarnd
😅 Let's see how many bugs I've created 🤣
@xuu@txt.sour.is You got any time/energy to help me test this? 🤔 There’s a process for indexing an existing archive too…
Okay, I’ve built full search capabilities for yarnd
😅 Let’s see how many bugs I’ve created 🤣
@movq@www.uninformativ.de I think my daughter might be finally 🤔 She’s 9 now and getting into table tennis 🏓 whoot whoot! 🥳 So… Maybe…
Yeah nothing being logged, so all the “golden paths” are being executed hmm 🧐
@bmallred@staystrong.run I don’t think so. Let me check my pod’s logs now though that I know you’re pulling me feed…. One sec…
@movq@www.uninformativ.de Yeah I’ll see if I can get back into this, everytime I see you post stuff like this it makes me want to go out again 🤣 Bit hard for a blind guy to do it all, but still I try 😅
The weird this is I still see your profile as
bmallred may not follow you
I assume you share your followings publicly, I see them on your feed, so I assume so. I was going to debug this on my side too today to see if.I goofed something up but my pod is rather busy so I hadn’t done that yet 😅 (actually working again finally on search)
@bmallred@staystrong.run D’oh 😅 Just in the nick of time haha 😜 Good o, I’m very pleased this all works across very different pieces of software 👌
@movq@www.uninformativ.de Oh that’s hilarious 😆 I have the exact same setup (minus any filters, I only have those for my Celestron NextStar 4SE telescope) 🔭
@movq@www.uninformativ.de Wow! 🤩 That is impressive! 👌 Do you mind sharing how you went about doing this? 🙏
@movq@www.uninformativ.de Look forward to the results 🤞
Oh so it really does hit some stupid arbitrary endpoint at AWS 😱
Hey @bmallred@staystrong.run 👋 Can you see this? 🤔
I will be deleting 14 inactive and unused accounts (for >3 years) on my Gitea instance git.mills.io at some point over the next few days. One of those accounts is yours @adi@twtxt.net – If you’d like to keep it, I suggest you sign-in 😅
I can’t imagine it’s a static URL either, it surely has to be a unicast address of some sort. Relying on a static URL sounds like an utter disaster to me 🤔 I’d have to read the open spec on this…