![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.dbzer0.com/pictrs/image/a18b0c69-23c9-4b2a-b8e0-3aca0172390d.png)
MlT (MlT
): please accept this honorary PhD
MlT (MlT
): please accept this honorary PhD
Sexagenarian Clown Pussy
I was thinking more like buttons for A-Z, but that sounds good too.
I would like at least 26 more buttons
Cryptocurrency is not necessarily anonymous. Buying bitcoin from a broker leaves a record connecting your payment method to your wallet. Even if you mine them yourself, doesn’t your IP address show up on the public ledger? I guess if you somehow bought bitcoin in cash…
Is there a more private cryptocurrency I’m not considering?
I have to run the .ps1 script in a new Command Prompt because the compilation takes a few minutes
I don’t follow this reasoning. Is it because you don’t want to take over the VSCode terminal with a long command? Couldn’t you can open multiple tabs, or run in the background, or use screen/tmux, etc.?
GNU Raster Editing Program - GREP
Graphical Image Tool - GIT
Photo Editing with Raster Layers - PERL
Visual Image Manipulator - VIM
They think… He is… A toad.
The implications of “magic is data” are fun. It leads to stories like Unsong where you can brute-force enumerate incantations until you find a good one. I also like the concept of Wizard’s Bane. I haven’t read it, but my understanding is that magic turns out to be Turing-complete, and the protagonist creates a LISP evaluator in magic, which enables them to outcast their enemies who are still doing the magical equivalent of writing assembly.
For completeness, we should review the involuntarily uploaded data as well.
Until then, we have simdjson https://github.com/simdjson/simdjson
It is clearer now without a pseudo-justification.
It’s about accountability
I don’t know, Schlitz beer is doing okay
Won’t someone please think of the children…'s unkicked faces
Don’t forget Tuxracer
Case in point: https://en.wikipedia.org/wiki/ADE_651
Basically a dowsing rod, totally incapable of detecting bombs, drugs, etc. But possibly still useful as a probable cause generator.
I don’t? You can apply a similar technique to bust file hashes. Add a new comment to each source file, or whatever.
My point is that automated methods to detect unwanted content will only get GitHub so far. It will have to be fuzzy, and that means it’s an arms race between detectors and obfuscators.
It would be possible to create a dummy “salt” commit and rebase every the branch onto it. The content would effectively be the same, but each commit hash would differ.
DRM = Direct Rendering Manager, in case anyone else was thinking Digital Rights Management…
https://en.wikipedia.org/wiki/Direct_Rendering_Manager