Meh. No Flatpak, no worries. And no updates, no new software or security patches.
h3ndrik
joined 1 year ago
Ja ich bin auch nicht neidisch auf die Briten. Weiß nicht so recht ob ich was gegen die EU hab. Wer weiß wo wir ohne die wären. Wahrscheinlich hätten Schäuble und Zensursula schon vor 15 Jahren hier die Totalüberwachung eingeführt, wenn man sich nicht mit anderen Ländern einigen müsste.
- https://www.forbes.com/sites/stewartroom/2023/09/21/will-uk-online-safety-bill-break-encryption-for-mass-surveillance/
- https://www.gov.uk/government/news/home-secretary-urges-meta-to-protect-children-from-sexual-abuse
- https://www.justsecurity.org/87615/changes-to-uk-surveillance-regime-may-violate-international-law/
Weiß nicht wie weit die damit grad so sind... Aber generell war das UK uns schon länger voraus mit der Überwachung der Bürger. Auch sowas wie Anzahl der Kameras die überall aufnehmen, Porno und Internetfilter... you name it...
Hehe, vor allem steht im Satz davor "seit 44 Jahren". Also erstmal schockiert mich irgendwie dass die seit 1980 so einen Quatsch machen... Außerdem, ist es wirklich so, dass es weniger Hagel gibt als 1979? Ich dachte Extremwetterereignisse werden ohnehin häufiger? Und es hat auch Klimawandel stattgefunden seit den 60gern und 70gern bis heute.
Und "nicht wissenschaftlich nachgewiesen" bei Sachen die nicht erst gestern erfunden wurden, ist ja auch eher ein gängiges Code-Wort für: ... ist Humbug.
AI Is a Black Box. Anthropic Figured Out a Way to Look Inside
...Concerning our earlier disagreement about the inner workings of large language models and whether there are 'concepts' stored inside...
Haltet uns auf dem Laufenden. ☺️
Ah, you're right. Nostr uses relays. Now I know what the name stands for. Sounds a bit like your proposal in extreme. The "servers" get downgraded to relatively simple relays that just forward stuff. The magic happens completely(?) on the clients.
I'm still not sure about the application logic. Sure I also like the logic close to me (the user.) The current trend has been towards the opposite for quite some time. Sometimes the explanation is simple: If you do most things on the server, you retain control over what's happening. That's great for selling ads and controlling the platforms in general. On the other hand it also has some benefits for power efficiency on the devices. I'm not talking about computing stuff, but rather about something like Google Cloud Messaging which has the purpose of reducing the amount of open connections and power draw and combine everything into a single connection for push messages. In order to do decide when to wake a device, it has access to to the result of the filtering and message priorization. Which then needs to be done server-side.
I'm also not sure with the filtering of hashtags. I mean if you subscribe to a hashtag. Or want to count the sum to calculate a trend... Something needs to work through all the messages and filter/count them. Doesn't that mean you'd need all Mastodon's messages of the day on your device? I'm sure that's technically possible. Phones are fast little computers. And 4G/5G sometimes has good speed. But l'm not sure what kind of additional traffic you'd estimate. 50 Megabytes a day is 1.5GB for your monthly cellular data plan. A bit less because sometimes people are at home and use wifi... But then they also don't just use one platform, but have Matrix, Lemmy and Mastodon installed. And you can't just skip messages, you'd need to handle them all to calculate the correct number of upvotes and hashtag use. Even if the user doesn't open the app for a week.
I don't quite "feel it". But I also wouldn't rule out the possibility of something like a hybrid approach. Or some clever trickery to get around that for some of the things a social network is concerned with...
Or like something I'd attribute more to edge computing. The client makes all the decisions and tells the edge (router) exactly what algorithm to use to do the ranking, how to do the filtering and when it wants to be woken up... That device does the heavy lifting and caches stuff and forwards them in chunks as instructed by the client.
Hmmh. I can't really make an informed statement. I can't fathom qemu being experimental. That's like a 20 year old project and used by lots of people. I'm not sure. And I've yet to try Box64.
I looked it up. The Snapdragin X Elite "Supports up to 64GB LPDDR5, with 136 GB/s memory bandwidth" while the Apple M2/M3 have anywhere from 100 GB/s memory bandwith to 150/300 or 400. (800 in the Ultra). And a graphics card has like ~300 to ~1000GB/s)
(Of course that's only relevant for running large language models.)
Hmmh. But how would that then change Mastodon not displaying previous (uncached) posts? Or queries running through the server with it's perspective?
And I fail to grasp how hashtags and the Lemmy voting system is related to a client/server architecture... You could just implement a custom voting metric on the server. Sure you can also implement that five times in all the different apps. But you'd end up with the same functionality regardless of where you do the maths.
And if people are subscribed to like 50 different communities or watch the 'All' feed, there is a constant flow of ActivityPub messages all day long. Either you keep the phone running all day to handle that. Or you do away with any notification functionality. And replicating the database to the device either forces you to drain the battery all day, or you just sync when the user opens the App. But opening Lemmy and it takes a minute to sync the database before new posts appear, also isn't a great user experience.
I'd say we need nomadic identity, more customizability with the options like hashtags, filters and voting. Dynamic caching because as of now Fediverse servers regularly get overwhelmed if a high profile person with lots if followers posts an image. But most of that needs to be handled by servers. Or we do a full-on P2P approach like with Nostr or other decentralized services. Or edge-computing.
I don't quite get where in between federated and decentralized (as in p2p) your approach would be. And if it'd inherit the drawbacks of both worlds or combine the individual advantages.
And ActivityPub isn't exactly an efficient protocol and neither are the server implementations. I think we could do way better with a more optimized, still federated protocol. Same with Matrix. That also provides me with a similar functinality my old XMPP server had, just with >10x the resource usage. And both are federated.
I think I can agree with that. For me it's a bit the other way around. My friends aren't on Discord. But the network effect is kind of hard to overcome. I'd say you can learn about privacy and new (to you) software and protocols by spending two or three evenings of your life. But convincing all your friends so it becomes any fun is considerably harder. I'd just name the actual issue, then. Otherwise people confuse it with Linux or Signal/Matrix/whatever being harder to operate.
Because with all of that, messaging, email, xmpp, matrix and ActivityPub most of the magic happens on the server. Take email for example. The server takes care to be online 24/7. It provides like 5GB of storage for your inbox that you can access from everywhere. It filters messages and does database stuff so you can habe full text search. Same with messaging. Your server coordinates with like 200 other servers so messages from users from anywhere get forwarded to you. It keeps everything in sync. Caches images so they're available immediately.
That allows for the clients/Apps to be very simplistic. It just needs to maintain one connection to your server and ask if there's anything new every now and then. Or query new data/content. Everything else is already taken care for by the server.
OP's suggestion is to change that. Move logic into the client/App. But it's not super easy. If you now need to be concerned on the client with maintaining the 200 connections at all times instead of just 1 to see if anyone replied... Your phone might drain 200 times as much battery. And requiring the phone to be reachable also comes with a severe penalty. Phones have elaborate mechanisms to save power and sleep most of the time. Any additional network activity requires the processor and the modem to stay active for longer periods of time. And apart from the screen thats one of the major things that draws power.
I have Debian on my servers for a decade or so, and on several workstations. My past experience doesn't quite reflect that. The Debian guys and gals have always been pretty quick with patching the vulnerabilities. Like outstanding fast.
There is some merit to the bugfixing. But that's kind of the point of Debian Stable(?!) Like in the meme picture of this post I don't want updates each day. And I also don't want the software on my servers to change too much on their own. I know my bugs and have already dealt with them and I'm happy that it now works seamlessly for 6 months or so...
And that's also why I have Debian Testing on my computer. That gives me sort of an unofficial rolling distro. With lots of updates and bugfixes. I mean in the end you can't have no updates and lots of updates at the same time. It's either - or. And we can choose depending on the use-case. (I think the blame is on the admin if they choose a wrong tool for a task.)