flotzam
Joined 8 years ago
Karma
1,282
Submissions
261
Member since
Jul 29
Recent submissions
Comment · 7 days ago
Comment · 7 days ago
There's an animated visual pattern that induces this cerebrospinal fluid flow: https://news.ycombinator.com/item?id=41942775
I've found it helpful for getting rid of the frazzled feeling after a sleepless night.
Comment · 17 days ago
It's easy to buy eSIMs anonymously. Either directly with cryptocurrency, or with a prepaid virtual credit card bought with cryptocurrency.
Comment · 22 days ago
Depends on the OS. GrapheneOS can override a bunch of them: https://grapheneos.org/usage#carrier-settings-overrides
Comment · 1 month ago
Oh you're going to love the Penultimate Cut fanedit/restoration of Blade Runner:
https://fanedit.org/what-the-final-cut-shouldve-been/ (check out the Changes tab)
https://www.youtube.com/watch?v=nsdmYjF_064 (trailer comparison)
https://archive.org/download/blade-runner-the-penultimate-cu...
Comment · 2 months ago
Or just a .onion for the frontend and code forge + another server at some clearnet domain proxying it (until taken down and replaced with the new one) would probably work fine. The hidden service can even terminate TLS with a valid cert for the clearnet domain.
Comment · 2 months ago
Hoping we'll see more resilient development/hosting emerge
Comment · 2 months ago
Seemed worth a new post, now that they actually killed it today :(
Is there any frontend still standing?
Comment · 2 months ago
Comment · 2 months ago
I've been wondering about the Red Hat model! Seems like so much of modern development involves git blame or whatever to make sense of how the code came to be, and sometimes rule out an "obvious" modification that actually turns out to be a bad idea now that you know the historical context.
GrapheneOS might have a better case though if it's not just about understanding the code but about how the Android build system expects that everything is in Git.
Comment · 2 months ago
> If you had included the previous word, it would be blindly obvious that “on a medium“ is only talking about the transport layer, not the format of the data.
I can see your point. But OTOH if providing the "preferred form of the work for making modifications" requires not squashing commits into a big mess to frustrate someone trying to make sense of the code (I'm sure the Google engineers making modifications prefer to look at individual commits!), and Google is using Git anyway to create those commits, then it seems to me like there's an argument to be made that the customary medium used to interchange a range of Git commits is Git.
But the stronger argument is that the Android build system expects everything to be in Git: https://news.ycombinator.com/item?id=49368983
Comment · 2 months ago
> We didn't have git tags when GPL was written in 1989
The GPLv2 requires "a medium customarily used for software interchange", not "a medium customarily used in 1989 for software interchange". Customs are the customs of the time someone is releasing the work.
Comment · 2 months ago
GrapheneOS is arguing that throwing away the metadata of however many commits and squashing them into a messy tarball is not the "preferred form of the work for making modifications", and that a manual process where you have to fill out a form in order to get a Google Drive link a week later is not "a medium customarily used for software interchange" in current times. Those are quotes from the GPLv2.
I can't think of a legitimate reason to check this and refuse to run in a secondary profile. But banking apps sure love to cargo-cult invasive nonsense.