Google Maps transit is still a frustrating experience
I used the stones to destroy the stones
They never really saw the potential (nor did they have the resources anyway) for GPGPU
Maybe ATI, which ended in 2010.
AMD launched ROCm in 2016, after the first AI boom of 2012, but before GANs and transformers exploded. In recent years they’re better positioned in than Intel ever was.
If anything it should’ve been AMD. Intel is barely keeping up with the CPU competition these days.
SSH carries design choices from the 90s that might not apply today.
But it’s the paper authors themselves who are talking about a redesign, not a random Lemmy user, so idk.
Point is - a system redesign is very much something worth looking into if improving the existing system will be too disruptive.
“use this rotary phone to enter your year of birth”
they are when fundamental assumptions change
In the worst case a privacy nightmare, and in the best case useless.
I won’t pretend I know better than the paper authors, what I can say is that some fixes are not incremental.
There are cases that mature tools and protocols should be left behind, and the danger lies exactly in using a protocol that was designed in the web 1.0 era.
It doesn’t look that simple to me. From the Terrapin paper:
Although we suggest backward-compatible countermea- sures to stop our attacks, we note that the security of the SSH protocol would benefit from a redesign from scratch. This redesign should be guided by all findings and insights from both practical and theoretical security analysis, in a similar manner as was done for TLS 1.3.
It seems the protocol itself needs a revision and implementation-specific patches are easier and less-than-ideal solutions.
One could argue that even these solutions they provide are already changes to the protocol, and not just fixes to implementation bugs. Both the Sequence Number Reset and Full Transcript Hash add or change functionality at the communication protocol level, rather than simply covering corner cases.
my downloads dir is ~/downloads/
but Firefox doesn’t create a file there, so it must use a temp location for the PDF that opens.
121.0 stable, .deb from Firefox’s ppa
interesting
it doesn’t download them for me, unless I explicitly save the PDF that opens
(akhtually it’ll always download in order to open it, I just mean it doesn’t create a PDF in the downloads directory)
Reddit is an open platform, and we love that
hah
Even with browser.download.open_pdf_attachments_inline
set to false
(default), Firefox already opens PDFs instead of downloading them, thanks to this setting:
For what use cases is that needed?
winter is hitting hard on some parts, I see
only if you choose one that logs data.
an ISP-only approach is objectively worse in every way: not only you often don’t even have an option to choose between them, but they have all your private info, are subject to your country’s laws, and they’re known to log and report data to 3 letter agencies, data that can probably also be stolen or purchased by other bad actors.
UTC and forget
1.2 Tb* ~ 150GB
Still impressive though
Buyers feel safer in a taller car, and car dealers are happy to sell this bullshit, even though SUVs are far more likely to roll over in a crash.