https://grapheneos.social/@GrapheneOS Here you go, argue with GrapheneOS - it’s an open platform, go ahead and make a masto account and share your thoughts with them. Tell them what you think! The rep who handles their masto account is very well spoken and presents rebuttals of value so I advise you bring your A game.
- 0 Posts
- 11 Comments
mote@lemmy.cato
Selfhosted@lemmy.world•How do people handle authoritative DNS redundancy for their self-hosted workloads?English
6·13 days agoPut HE (dns.he.net) in your back pocket - they run a free DNS service which includes slave (do we still call it that?) service so that you can add their resolver as an ultimate failover / failback if your self hosted DNS takes a dive for whatever reason things break in our world.
Generally, hosting your own DNS “should” mean having a primary and secondary on separate AS networks, or at least different provider routes or locations. But if you’re doing all this from home, where is the second location for DR purposes… exactly? I sure don’t have one, power goes out here everything goes dark - in the old days everyone used to do this (share out tertiary DNS to each other) but it’s become a thing of the past in today’s world. HE can help fill that gap.
To your point - I use Gcore DNS and Bunny DNS for my stuff, as I mainly use online VPSes and don’t run racks of hardware at the house. The only things I physically selfhost at home are a pair of old laptops acting as storage servers which backup all my bytes and bits from online to some SSDs.
mote@lemmy.cato
Technology@lemmy.world•Nintendo Wipes Out 400+ Switch Emulator Repos in Single-Day GitHub Sweep * TorrentFreakEnglish
231·26 days agoI 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).
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).
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)
mote@lemmy.cato
Technology@lemmy.world•Microsoft's GitHub bans security researcher who posted zero-day Windows exploits because company 'ruined their life' — expert claims action is vindictive and promises further retaliationEnglish
161·4 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.
mote@lemmy.cato
Technology@lemmy.world•Microsoft's GitHub bans security researcher who posted zero-day Windows exploits because company 'ruined their life' — expert claims action is vindictive and promises further retaliationEnglish
551·4 months agoThe 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…

My bad, I didn’t think of that. My only thought was “$20 says this chucklehead won’t do squat” because we know.