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).
Briar fits into it's own niche (operational design), making it a choice for certain activities but not what I would call your general normie chat app. It makes tradeoffs (using the local network, no caching relays, etc.) to increase security posture at the expense of general use. IIRC, Jack Dorsey's BitChat was modeled after the same designs? (which is interesting, because Nostr his other pet doesn't)
It's been in DC for a few versions now, we've used a combination of: macOS desktop, Android mobile, Linux desktop, iOS Mobile - and haven't had problems more than usual getting apps access to the cam/mic on macOS.
They just dropped DC 2.57.0, it hit F-Droid and Arch repos in my morning updates. An update to the relay code was also dropped, 1.12.0, for relay operators.
I haven't tried SimpleX yet, as they can't share the same profile to multiple devices (it's explained in detail in the FAQ) which makes it a normie usability deal killer. I've heard it has really bad battery life on mobile too, but that's just reading random comments. Right now we're using Delta (and running a relay) and it's just fine.
100% - the game I play (Warframe) moved to hosting their own wiki, taking over from where it started on Fandom. Even with the entire gaming community trying to tell search engines that the new wiki is the source of truth, Google/Bing feed Fandom results. The Fandom wiki is "dead" compared to the real one and we use reddit/forums to tell people to not use Fandom.
It's not entirely dystopian (just barely), we have newer messengers like SimpleX and DeltaChat (I/we use Delta) on the up and coming which deliver on all the same e2ee promises as Signal. It's just network effects as usual, getting people to try is the real hurdle.
What they share in common (mostly) is the architecture - they're built natively decentralized, utilizing caching relays with no single source of truth, or device of truth, to be used to create a profile of you like a phone number does. Encryption keys owned by the user and no single servers. Generally this is the Nostr design as well, so we have 3 different teams all focusing on the same natively decentralized architecture patterns.
What I like about this one is the nerd friends cheering Sid on, celebrating his success in action. It is, to me, one of the quintessential parts of nerdery - to lift others up and watch them become great.
I would assume your system is using systemd (I don't use Kubuntu specifically); the laptop lid is (now in 2026) controlled by the systemd infrastructure - it's a matter of setting a config option and this should fix you up. Arch as usual has the best wiki on the subject:
You're probably looking at HandleLidSwitch* options. There's still nothing wrong with the manual disable to /proc/acpi/wakeup to cover your bases (layers of the onion), I'm fighting with a "modern" laptop that only has s2idle and it's terrible compared to S3 - I'm in ACPI wakeup hell and still trying to figure out what's causing it.
From my understanding (which could be incorrect, I mean I wasn't there), the pattern applied to the hull was done differently per ship. I imagine they applied the base pattern in a random tile-like build where things can be rotated and moved around in the design before painting.
My first thought when I saw this - "oh hey look, razzle dazzle clothes" which is my personal mental association of the famous scene in Stripes movie, with Dazzle Camouflage which I always thought was a neat idea.
In late May 2026 images appeared on social media showing Russian Ural and KAMAZ trucks painted in the classic dazzle camouflage. Supposedly the unusual paint scheme is to confuse Ukrainian drones controlled by artificial intelligence and disrupt their pattern recognition, and not to trick the human eye. Ukraine has experimented with AI for targeting as seen in Operation Spiderweb, and is conducting a deep strike campaign to disrupt Russian logistics.[72][73]
(just talking shop) I've poked at them, you'd think the old.lemmy.ca would be appealing but not for me - I rather like this Lemmy webUI overall as a design. Good font sizes, line spacing and so forth - it has a well formed comfortable feel which I can tell has an experienced eye to it (minor details matter). Conversely, when I look at, say piefed or old.lemmy I just got "ugh, those fonts! that line spacing!". The default UI is actually a well crafted piece of usability kit - the infobox is an Achilles heel.
Random: I've used the Lemmy webUI details to craft similar feeling looks to HackerNews and (old) Reddit using nothing more than uBlock filters. Nothing grandiose but the fine tuning makes them sorta feel like the Lemmy UI (but worse, holy cow is there so much hard coded HTML in these old sites - lipstick on a pig but it helps).
Honest input to your thoughts - as a registered/logged-in user, that Lemmy home page infobox is a UI/UX nightmare - it blocks my quick access to the second box below that has my subscribed communities. Upon visiting, I would immediately collapse that top box without ever looking at it; I now have a simple uBlock Origin rule that hides the top infobox on the home page for me automatically. On old.reddit, the list of subscribed things is a dropdown top left so they avoid this UI/UX problem with stacked infoboxes.
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).
Briar fits into it's own niche (operational design), making it a choice for certain activities but not what I would call your general normie chat app. It makes tradeoffs (using the local network, no caching relays, etc.) to increase security posture at the expense of general use. IIRC, Jack Dorsey's BitChat was modeled after the same designs? (which is interesting, because Nostr his other pet doesn't)
The UESP wiki is great when you have to name some new machines (IT stuff), lotta laptops out there named Bloodthorn right now. :)
It's been in DC for a few versions now, we've used a combination of: macOS desktop, Android mobile, Linux desktop, iOS Mobile - and haven't had problems more than usual getting apps access to the cam/mic on macOS.
They just dropped DC 2.57.0, it hit F-Droid and Arch repos in my morning updates. An update to the relay code was also dropped, 1.12.0, for relay operators.
I haven't tried SimpleX yet, as they can't share the same profile to multiple devices (it's explained in detail in the FAQ) which makes it a normie usability deal killer. I've heard it has really bad battery life on mobile too, but that's just reading random comments. Right now we're using Delta (and running a relay) and it's just fine.
100% - the game I play (Warframe) moved to hosting their own wiki, taking over from where it started on Fandom. Even with the entire gaming community trying to tell search engines that the new wiki is the source of truth, Google/Bing feed Fandom results. The Fandom wiki is "dead" compared to the real one and we use reddit/forums to tell people to not use Fandom.
My best friend's band is objectively the best hardcore show you've never been to yet. :)
Younger me thought this was a really cool show, I wonder how it holds up now...
It's not entirely dystopian (just barely), we have newer messengers like SimpleX and DeltaChat (I/we use Delta) on the up and coming which deliver on all the same e2ee promises as Signal. It's just network effects as usual, getting people to try is the real hurdle.
What they share in common (mostly) is the architecture - they're built natively decentralized, utilizing caching relays with no single source of truth, or device of truth, to be used to create a profile of you like a phone number does. Encryption keys owned by the user and no single servers. Generally this is the Nostr design as well, so we have 3 different teams all focusing on the same natively decentralized architecture patterns.
por qué no los dos?
What I like about this one is the nerd friends cheering Sid on, celebrating his success in action. It is, to me, one of the quintessential parts of nerdery - to lift others up and watch them become great.
I would assume your system is using systemd (I don't use Kubuntu specifically); the laptop lid is (now in 2026) controlled by the systemd infrastructure - it's a matter of setting a config option and this should fix you up. Arch as usual has the best wiki on the subject:
https://wiki.archlinux.org/title/Power_management#ACPI_events
You're probably looking at
HandleLidSwitch*options. There's still nothing wrong with the manual disable to/proc/acpi/wakeupto cover your bases (layers of the onion), I'm fighting with a "modern" laptop that only has s2idle and it's terrible compared to S3 - I'm in ACPI wakeup hell and still trying to figure out what's causing it.It's when you subsist on Lower Class Brats songs during the night hours.
From my understanding (which could be incorrect, I mean I wasn't there), the pattern applied to the hull was done differently per ship. I imagine they applied the base pattern in a random tile-like build where things can be rotated and moved around in the design before painting.
My first thought when I saw this - "oh hey look, razzle dazzle clothes" which is my personal mental association of the famous scene in Stripes movie, with Dazzle Camouflage which I always thought was a neat idea.
(just talking shop) I've poked at them, you'd think the old.lemmy.ca would be appealing but not for me - I rather like this Lemmy webUI overall as a design. Good font sizes, line spacing and so forth - it has a well formed comfortable feel which I can tell has an experienced eye to it (minor details matter). Conversely, when I look at, say piefed or old.lemmy I just got "ugh, those fonts! that line spacing!". The default UI is actually a well crafted piece of usability kit - the infobox is an Achilles heel.
Random: I've used the Lemmy webUI details to craft similar feeling looks to HackerNews and (old) Reddit using nothing more than uBlock filters. Nothing grandiose but the fine tuning makes them sorta feel like the Lemmy UI (but worse, holy cow is there so much hard coded HTML in these old sites - lipstick on a pig but it helps).
Honest input to your thoughts - as a registered/logged-in user, that Lemmy home page infobox is a UI/UX nightmare - it blocks my quick access to the second box below that has my subscribed communities. Upon visiting, I would immediately collapse that top box without ever looking at it; I now have a simple uBlock Origin rule that hides the top infobox on the home page for me automatically. On old.reddit, the list of subscribed things is a dropdown top left so they avoid this UI/UX problem with stacked infoboxes.
Look, I touched the bride's butt once at the reception. Never living that down am I?
GenX here, using the 80/20 rule 80% of my friend's marriages (probably higher %) have ended in divorce. Typically after kids are involved. :-/