#QOTD : If you could redesign a fundamental internet protocol from scratch, which one would you choose and how would you improve it?

@aelaraji@aelaraji.com LOL which I block on purpose 🤣

@aelaraji@aelaraji.com Bahahaha 🤣 The domain for that image is blocked on my local network 😅

@aelaraji@aelaraji.com Good luck! 🤞

@mckinley@twtxt.net I see 🤔

@rrraksamam@twtxt.net I’m looking forward to my all-SSD Btrfs RAID5 NAS. I think it’ll be a while, though. I just paid $6.92/TB for a couple of used 12TB HDDs.

@prologic@twtxt.net They’re shutting down after 7 years. It was a great place to buy Monero with cash by mail. https://localmonero.co/nojs/blog/announcements/winding-down

50 Core CPU, 128GB RAM, 20TB SSD laptops when?

@mckinley@twtxt.net What happened to it? 🤔

@aelaraji@aelaraji.com Nice. Compiling problematic software is my #1 use of containers on my PC. I use a handful of them on my server.

@movq@www.uninformativ.de To be fair Twtxt has always been quite niche. Yarn picked up interest a bit a few years back, but then things died down a bit. I built yarnd for me, I continue to use it and improve it every now and again. But I guess the only uses we’ll continue to see and that includes new folks are folks that give a shit about simple things, and see value in a slow, privacy focused medium? 🤔

Cut my following list down to just a mere ~47 feeds. ~11 rss/news feeds, 23 local feeds from my pod, and 13 external feeds.

@lyse@lyse.isobeef.org Same here. Where does it not work, @movq@www.uninformativ.de?

@news Err I meant “junk” 🤣 (too late to edit, cbf editing it manually or via the API/CLI 😅)

New feature (not a great UX, sorry 😞) that displays the last fetched feed status, last error (if any) and error count in your “Following” list. Check it out and cleanup your feeds for “hunk” 👌

@movq@www.uninformativ.de Could also just be a shitty antenna 😅

I just unfollowed some ~200+ feeds that are basically dead “404 Not Found” 😳

@movq@www.uninformativ.de Well I used to have a handheld GPS device, probably before I lost most of my sight. I didn’t really feel that it took ~12m to get a fix, it was usually much faster. You may just find that all this A-GPS thing is all just bullshit anyway and just an excuse to collect and store your GPS location on some random web server that someone else owns 🤣

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? 🤔

@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 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.