My biggest concern with SteamDeck was that it would become a 1-2 year upgrade cycle device. I don’t expect the hardware to last 7+ years like normal console lifecycles but I’m very glad to hear they’re being patient and aggressively supporting the software side.
Borg backup is gold standard, with Vorta as a very nice GUI on machines that need it. Otherwise, all my other Linux machines are running in proxmox hypervisors and have container/snapshot/vm backups regularly through proxmox backup server to another machine. All the backup data is then replicated regularly, remotely via truenas scale replication tasks.
Just another stunt to stay in the media for any reason, no matter what.
Edit: having unwillingly thought about this more… no, this is just his overcompensation for the sick burn that people leave his rallies early. He’s too petty for this to be staged media attention performative art.
Going full homelab with a rack, battery backups, and 2.5gb backhaul on my home network. Absolutely game changing from an appliance management standpoint where any one node can go down for any reason and there’s a backup and replacement on hand in minutes with built in redundancy. Not to mention the learning and experience opportunities when setting up hardware and software services. Sure is sweet to have data redundancy and protections!
I agree on the actual human performance aspect. The technical details are fun to watch for in terms of team play and skill, where the minute differences matter in a sport. But I also get where OP is coming from. It’s kinda sad how long it took from a production standpoint to put tracking chips inside the footballs. I understand NFL as an institution wanting to keep the game a little sloppy but stats are interesting and data driven graphics really keep people engaged in today’s world. Look at some of the tech in broadcast golf, it’s incredible and makes for much more interesting watching these days, even if the sport or sports in general aren’t the most engaging *from a bystander point of view.
Was going to mention this. Finding a smaller community focused on a specific project can afford more collaborative learning while contributing to projects that need help. It’s also a good way to learn humility, like finding that one person in the corner of the office who constantly picks apart your PRs without any emotion or judgement and genuinely improves your own code by learning from mistakes.
So far it’s fine. Not much of a difference on the surface. Except floatplane videos in Firefox have distorted audio now after the update. Might be unrelated but it was directly after updating. Oh and my Application Menu crosses into the monitor to the left of my primary screen which is a bit annoying. Nothing showstopping here.
For clarity, the recommendation is specifically 3 copies of your data, not 3 backups.
3-2-1 backup; 3 copies of the data, 2 types of storage devices, 1 off-site storage location.
So in a typical homelab case you would have your primary hot data, the actual device being used to create and manage that data, your desktop. You’d regularly backup that data into warm storage such as a NAS with redundancy (raid Z1, Z2, etc). Followed by regular but slower intervals of backups to a remote location, such as a duplicate NAS with a secure tunnel or even an external drive(s) sitting at a friend or family member’s house, bank vault, wherever. That would be considered cold storage (and should be automated as such if it’s constantly powered).
My own addition to this is that at least one of the hot / warm devices should be on battery backup in case of power events. I’ll always advocate that to be the primary machine but in homelab the server would be more important and the NAS would be part of that stack.
Cloud is not considered a backup unless the data owner is also the storage owner, for general reliability reasons related to control over the system and storage. Cloud is, however, a reasonable temporary storage for moves and transfers.
Nice! I’ve been loving focus modes on iOS, it’s a real game changer when coupled with geofencing and calendar events and other automation. Glad more people will be able to utilize this!
Yeah I found which key and that has been a little more useful than nothing, but it’s a half-way solution, like showing shortcut next to menu items in a normal GUI application. Thank you for the suggestion!
I self host services as much as possible for multiple reasons; learning, staying up to date with so many technologies with hands on experience, and security / peace of mind. Knowing my 3-2-1 backup solution is backing my entire infrastructure helps greatly in feeling less pressured to provide my data to unknown entities no matter how trustworthy, as well as the peace of mind in knowing I have control over every step of the process and how to troubleshoot and fix problems. I’m not an expert and rely heavily on online resources to help get me to a comfortable spot but I also don’t feel helpless when something breaks.
If the choice is to trust an encrypted backup of all my sensitive passwords, passkeys, and recovery information on someone else’s server or have to restore a machine, container, vm, etc. from a backup due to critical failures, I’ll choose the second one because no matter how encrypted something is someone somewhere will be able to break it with time. I don’t care if accelerated and quantum encryption will take millennia to break. Not having that payload out in the wild at all is the only way to prevent it being cracked.
Wait, this sounds awesome! I haven’t had time to dig into it more yet but does this mean I could host my own “pod” allowing my data to stay where I want it and be backed up how I want, while allowing my fediverse identity to be used on multiple different federated services?
Exactly why you shouldn’t press the hang up button when unknown caller happens. Just mute the call and let it ring out in silence. Don’t press the voicemail button either to send them straight there. It’s like social media, any interaction is a positive for their bot system and the only way to avoid making things worse is to not interact at all.
astrsk @ astrsk @fedia.io Posts 2Comments 307Joined 11 mo. ago
My biggest concern with SteamDeck was that it would become a 1-2 year upgrade cycle device. I don’t expect the hardware to last 7+ years like normal console lifecycles but I’m very glad to hear they’re being patient and aggressively supporting the software side.