- 0 Posts
- 11 Comments
So close! you have to do
cat < foo.txt:-) (/s)
Al, we need to optimize. Speed and efficiency to prevent Ctrl+C.
Write 16MB of zeros to the beginning of the boot device to overwrite the boot blocks (16MB being extra cautious, 8MB is fine) and if you want to double the roulette fun, have it fork in parallel and do the same thing to the EFI partition (if you have one). Extra credit: fork a 3rd time and write 16MB to the end of the disk, nuking the backup GPT structure sitting there. This can all be a fun inline “one-liner” to appeal to cut & pasters. curl pipe bashers.
It’ll happen so fast there’s no stopping it, their only way out now is to get the running system saved off that disk while it’s mounted.[1] But your nuke is invisible, how long until they find out trying to reboot? Devious Al, you’re just devious.
[1] there is a way to recover if you build identical machines, like VMs or VPSes - a tool such as gdisk can pull the table(s) off one to a file, which can be pushed onto another. We’ve recovered $customer mistakes at $ITjob doing this before, it works. It might not boot properly, but it can contain enough filesystem boundary information to be able to recover a partition manually (rescue).
3·2 months agoIt is, the ranges mark up the ammo (what business doesn’t) as they sell small quantities to a captive audience who will pay. Ammoseek represents the other end of the spectrum, ppl buying wholesale in larger quantities. Not represented are the hand loaders, typically sports-oriented going through a thousand a week in practice buying components at cost.
You can read and support all his art/comics via Mastodon and his store (gricklemart): https://mstdn.social/@grickle
I see folks mentioning going back to their dormant LFM accounts. The Metabrainz Foundation has a project ListenBrainz, a more open FOSS style version; if you’re going to spin some scrobbling cycles maybe check it out:
(I stopped scrobbling years ago, privacy concerns)
161·3 months agoStars are just someone’s bookmark (me included) because there’s no simple “bookmark this because I’ll forget in an hour and want to look at it later when I have time.” If one trusts Stars, you’re literally trusting a bookmark that I didn’t put more than 2 seconds of thought into clicking because I have a bad memory. Many I know do the same.
I go straight to code history, show me what the commits look like. One can derive a lot about the project based on just the way the commit messages are written before looking at the code being changed. How the code is changed over time (process, communication, methods, etc.) adds more layers to the qualitative observation. I move on to Issues when I want to see how the devs interact with the users having problems, which is another story.
The dichotomy here is you can’t be famous hosting exploits on smaller forges. Gotta be on the big platforms where you can be starred and forked for social media cred to make news stories to impress your friends. IIRC I think HeartBleed (maybe ShellShock?) was the tip of this popularity iceberg…
I have not tried/used it (yet?), but the kids are building Radicle for this very purpose. It gets a fair amount of techie coverage (blogs, comments, etc.) but sits in unique space compared to, say, Forgejo (classic self-hosted git).