bblb
Joined 9 years ago
Joined 9 years ago
We _still_ use TCP/IP and it's v4 is from 1981.
edit: I once looked deep into Remote PowerShell. How it's actually built. Dear. God. XML enveloped inside XML inside another XML wrapped around HTTP. Add some certificate based encryption for the HTTP envelope and some more encryption for the Kerberos messaging inside the serialized XML wrapped in envelopes and wrappings. Now THAT'S a communication protocol. :D
It can do file organizing and wrangling when needed, it has simple web access with the curl tool, it can analyze media file contents. It's analyzed my local data and written several little tools (cli, TUI, GUI) to manage it automatically or give comprehensive reports. I can create new media through ComfyUI and Krita AI.
Sure, it can't book a flight or organize the family calendar for the next month, but I don't have any need for those.
edit: llama.cpp LLM model and ComfyUI image/video models can't live in the VRAM at the same time, but I let it code a little KDE widget with two buttons: one unloads the llama.cpp model and another one unloads the ComfyUI models.
Probably curiosity.
If there's an AI version of code golfing, I'd be curious to see it. Maybe they golf worse or much better than us meat bags.
Sure it's bothersome to use the sneakernet once a month (manually copy data to USB stick and stash it somewhere), but when that ransomware hits (can happen on personal devices also), it literally can't access the offline copy, and try to encrypt that one also.
Immutable backup solutions are code and thus eventually defeatable from the remote attackers point of view. Offline requires physical access, and maybe a big enough wrench to get the USB stick's disk encryption PIN out of you.
There was a huge exodus of existing programmers/modders ~two years ago, due to paid mods and what not. The gamers took over with their LLM tools.
That's the whole 21 minute 59 second video in a nutshell.
A loud and hectic quick cut rambling video essay. Millions of views, naturally.
Although now that I think of it, stopping absorbing everything, or, _absorbing nothing_, might be a good mindfulness practice.
Do fast, deliver.
The 3-2-1 includes the production data itself.
You have one copy of data (the data that needs to be backed up), and you have two additional copies of that data (the "3" in the strategy), where one of the backup copies is stored offsite (the "1" part), which naturally follows that it satisfies the middle "2" also.
For over a decade we used 4-3-2 strategy, but it got expensive fast and due to ever evolving budget cuts, our (local gov) customers weren't ready to pay the extra.
There's also 3-2-1-1-0, but that's just a fancy way of saying you _really_ should be doing those restore tests you never seem to have the time, because ransomware can and _will_ corrupt your backup copies.
edit: the absolute minimal setup that still satisfies the 3-2-1 rule: 1) you have your data in production directory on local NVMe stick inside your computer, 2) you copy the original production data to another directory inside the very same NVMe, 3) you occasionally manually copy the production directory data to USB and store that USB inside the shed in your backyard. - That's it. Now your home data is covered by the coveted "3-2-1" enterprise ready backup strategy.
[My home computer] --> SSH --> [my hardcore IndieWeb local cloud]
That's about it. Safe enough.