m0xEE @m0xee@librem.one

@romin
Toradora that is actually good? 😂
(Considering the post-apocalyptic cityscape in the background)

@lunar @swaggboi
Same here! Happens quite often when the first response makes you realise that there won't be any improvements and that giving up on the product and staying away from everything that company does might be not such a bad idea — saves your time.

My favourite tech obituary website 😅
Hell, when did that happen to Mitnick though? I must've missed that 🤔

@unsaturated
Maybe network engineers who had to deal with it in practice can shed some light. My "solution" is disabling it in clients where it is optional (it is in Firefox) and building software such as curl without support for it 😅
@urlyman

@unsaturated
TBH, I'm not knowledgeable enough myself about how QUIC, which HTTP/3 is based on, handles that. To me the idea of introducing congestion control into application level (and the implied added complexity of client implementation) seem bad enough, but you might be right, there might be even more to it than that.
@urlyman

@catto
Or… 😏
*walter_white.jpeg*

@urlyman
HTTP/3 is UDP-based — a strong departure from TCP-based HTTP1.1
Not without a few advantages — mainly parallelism, and it's a further development of HTTP/2, which was still TCP-based, but multiplexed.
Yet, dealing with datagrams on application level to work with streams of data seems a little controversial to me. Last, but not least: it mostly makes sense when in addition to 15 kB of main text content you have to carry large number of scripts, stylesheets, auxilary data fragments, etc

@newt
That's a very nice paper to have — might save you some time when interacting with the coppers.

US DoJ considers breaking up Google: https://www.gsmarena.com/us_doj_considers_breaking_up_google-news-64140.php

Google is a monopoly. The fix isn't obvious. A business breakup may be coming – but what comes after may not be better: https://www.theregister.com/2024/08/15/google_monopoly_fix/

I hope this "breaking up" involves cluster munitions in one way or the other 😈

@urlyman
*148 requests carried over UDP 🤦

To me this is one of the most bizarre parts!

@PurpCat
M-m-m… pox 😋

@Hyolobrika
As users don't usually audit the cryptographic algorithms themselves and we don't know much about what's happening with these servers, for the most it's "Just trust me, bro!"
Centalised systems are a sweet spot for attacks: you break into one system — you own all the users, but no one might ever get interested in hacking into your server for a dozen users. Centralisation is always weak from security POV — no amount of strong cryptography can change that.

@eevee @dragonarchitect

@Hyolobrika
That's the point, there can be no compromised servers: either everyone is safe or the whole system gets compromised — which as you rightly noted, isn't out of the question, because at present you might have the strongest cryptography behind your system, but vulnerabilities, including those in algorithms, get discovered all the time and black hat hackers might not even be interested in disclosing them, it might take time to realise the system got compromised.
@eevee @dragonarchitect

@dragonarchitect @eevee
Not to mention the fact that half of these problems don't exist on Signal simply because there is no federation at all — there is no home server to be compromised as there are no other home servers 😂

This ↑↑↑
And you set your own expectations higher when you're putting in more effort, which in a lot of cases never get met 😌

@solidsanek
@kaia

@chowderman @rvps2001
He has made about a dozen claims in the past few days, none of which sound particularly realistic or trustworthy.
I think they are using him as mouthpiece in hopes that Z-bloggers would be reluctant to make counterclaims — to avoid issuing public apologies on video a few days later 😱

@romin
Hexadecuple! Now we're playing 🫠

@GeriAQuin
1974 — Meet The Residents 🤪
(LP I suppose)