Yes, 😅. Thank you for letting me know.
I typed correctly I’m pretty sure, but typing it again now it autocorrects to “C - C - P” now 🫤. Even more confused.
I’ll edit my original post.
Yes, 😅. Thank you for letting me know.
I typed correctly I’m pretty sure, but typing it again now it autocorrects to “C - C - P” now 🫤. Even more confused.
I’ll edit my original post.
Alpine on Pi4.
LMDE on recycled AMD systems (phenoms, opterons, FM2 APUs, oh and a recently dead bulldozer fx-8150).
TrueNAS, OPNsense on dedicated hardware.
VMware ESXi on my older workstations (currently transitioning toward LXD/Incus and XPG-ng XCP-ng with Xen Orchestra).
The essential part at the end:
“ When reached for comment, Reddit spokesperson Tim Rathschmidt directed me to Reddit’s API FAQ page and said the company couldn’t comment further because it’s in a quiet period and doesn’t “comment on confidential business conversations and/or agreements.” ”
We can infer that it was not the fountain of money they thought it would become.
More telling is their silence. Who doesn’t want to promote and advertise how profitable they are to potential shareholders just before an IPO.
I regularly “deep freeze” or make read-only systems from Raspberry Pi, Ubuntu, Linux Mint LMDE and others Linux Distros whereas I disable automatic updates everywhere (except for some obvious config/network/hardware/subsystem changes I control separately).
I have had systems running 24/7 (no internet, WiFi) for 2-3 years before I got around to update/upgrade them. Almost never had an issue. I always expected some serious issues but the Linux package management and upgrade system is surprisingly robust. Obviously, I don’t install new software on a old system before updating/upgrading (learned that early on empirically).
Automatic updates are generally beneficial and helps avoid future compatibility/dependency issues on active systems with frequent user interaction.
However, on embedded/single purpose/long distance/dedicated or ephemeral application, (unsupervised) automatic updates may break how the custom/main software may interact with the platform. Causing irreversible issues with the purpose it was built for or negatively impact other parts of closed circuit systems (for example: longitudinal environmental monitoring, fauna and flora observation studies, climate monitoring stations, etc.)
Generally, any kind of update imply some level of supervision and testing, otherwise things could break silently without anyone noticing. Until a critical situation arises and everything break loose and it is too late/too demanding/too costly to try to fix or recover within a impossibly short window of time.
I want that‽ 😆
When I’m old and decrepit with an out of sync heart, I would like to go with a nuclear pacemaker.
I could then say that I am henceforth Plutonium powered 😎.
Exactly! I always wondered about that particular issue.
Although, if one encrypt themself their email through GPG or other means before sending it, it’s almost a non issue excepting metadata (sender, receiving email address, timestamp, etc.).
This is beautifully familiar.
Am I seeing too many similarities between how Twitter/X was taken over and singlehandedly being irreversibly ruined?
While Windows is stubbornly becoming increasingly user-adversarial (advertising, constant intrusive updates, forced transition from your favorite browser to Microsoft Edge, etc.) and unintuitive (sometimes even counter intuitive) interface design, placement and inaccessible settings.
Well, delighting in schadenfreude, I won’t complain. Microsoft is inadvertently helping me help transition many friends, family and colleagues to various flavors of Linux systems, namely Linux Mint (whichever desktop they prefer) and/or Pop!OS most of the time, but also occasionally Fedora or a particular flavor of Ubuntu.
I never recommend Arch or rolling release systems or immutable systems to first time Linux user so as to preemptively avoid additional layers of complexity, learning curve, downtime and troubleshooting.