337 karma · joined August 17, 2018
While not the most popular idea, I love Snaps ability to auto update packages. I configured my box to check for updates every 4 hours. This felt like a good compromise on security/annoyance if there was a security issue for a non-Enterprise environment. Docker I used to use one of the WatchTower images to check for updates/pull images, but it needed to monitor the Docker socket which is a big security no no.
I do find it strange that Canonical doesn't allow you point to/host a third party Store.
I see friends switching to Brave, but I dislike how they seem to be focusing their RnD into BAT/crypto features. Firefox also has the advantage of having addons on mobile.
It's a pipe dream, but I could see Google reverting to the don't be evil days with the rise of these Chromium forks and other ad agencies. Somehow change their business model away from ads, promote adblocking, and support addons on mobile. Checkmate Brave/Vivaldi/Edge/etc. Other than niche features or those apposed to Google will look elsewhere.
https://news.ycombinator.com/item?id=19828317
``We are working with the small number of networks with a higher network/ISP density than Cloudflare (e.g., Netflix, Facebook, Google/YouTube) to come up with an EDNS IP Subnet alternative that gets them the information they need for geolocation targeting without risking user privacy and security. Those conversations have been productive and are ongoing. If archive.is has suggestions along these lines, we’d be happy to consider them. ``
I use messenger.com or the app regularly as it's how large group of friends talk (sigh). I haven't personally viewed main FB UI in a few years now.
We need to know what packages will be unstable. People seem to be held up that Redhat releases will be taken from Stream, making it a "beta" of things to come instead of a free RH. I personally see this no different than Fedora > CentOS release cycle. I welcome newer features hitting our enterprise boxes sooner than later.
I have read that it's also not a true rolling release, and instead will have minor stop gap channel releases along the way. Unless there is another big shake up like init vs systemD, it will be excellent to have an enterprise grade rolling release option for long lived (non-cattle) servers. Updating our fleet from 5 to 6, 6 to 7 was painful...
Currently moved most of my Dev servers to Stream, and I am excluding a few packages from rolling with DNF-Automatic. Will this stay supported?
For those that are curious, I found on Distrowatch that it's based on Debian.
He imagines if Microsoft with their whole "We <3 Open Source" ideal either open sourced older versions of Windows (he mentions 3.1 for Work groups, or 98 back), or better, backs/contributes code to ReactOS themselves.
One of his arguments is that either method would take minimal effort from Microsoft, and would show their love of Open Source. The code could be made available as is, and allow the ReactOS project to continue burden of development/support.
His second major argument is that Microsoft would not take a financial hit from releasing these old versions. The OS's are no longer available for purchase in stores, and MS no longer provides support. Could also convince Embrace/Extend/Extinguish gray beards that Microsoft is "changing", making them more likely to trust MS.
Ultimately he theorizes Microsoft could only make finical gain from this. This comes from the positive community views (and wallets), and they could be positioned to repackage it as a "Windows Classic". This would allow them to "sell" and support old code again that would be perfect for legacy software, yet run on modern hardware.