Even just being rooted on the stock Pixel rom is a fight.
That, I can see being more of an issue than an unmodified, trusted 3rd party OS. If I remember right, rooting makes the device fail Verified Boot:
It establishes a full chain of trust, starting from a hardware-protected root of trust to the bootloader, to the boot partition and other verified partitions including system, vendor, and optionally oem partitions.
https://source.android.com/docs/security/features/verifiedboot
Courtesy of Kagi’s Universal Summarizer.
This chud uploaded potentially sensitive information to a public service.
A bill draft, which eventually/maybe gets signed and is public by its very nature is sensitive?
People really need education on how to intelligently use these services.
Agreed on principle, but I don’t see how what he did was wrong…other than calling ChatGPT a subject matter expert.
but if I’m going to pay for search it’s something like Perplexity.
Generative AI search engine Perplexity, which claims to be a Google competitor and recently snagged a $73.6 million Series B funding from investors like Jeff Bezos, is going to start selling ads, the company told ADWEEK…“Advertising was always part of how we’re going to build a great business,” said Shevelenko.
https://www.adweek.com/media/gen-ai-search-engine-perplexity-has-a-plan-to-sell-ads/
As of my understanding, immutable systems are useful for Devices that are more bound to change, like a Desktop…I do not see much benefit here for a stable server system.
This logic is kind of backwards, or rather incomplete. Immutable typically means that the core system doesn’t change outside of upgrades. I would prioritize putting an immutable OS on a server over a desktop if I was forced to pick one or the other (nothing wrong with immutable on both), simply because I don’t want the server OS to change outside of very controlled and specific circumstances. An immutable server OS helps ensure that stability you speak of, not to mention it can thwart some malware. The consequences of losing a server is typically higher than losing a desktop, hence me prioritizing the server.
In a perfect world, you’re right, the server remains stable and doesn’t need immutablitiy…but then so does the desktop.
Production environment is typically in the corporate world, not usually a homelab. Service providers often have a SLA uptime guarantee of 99%. They don’t often push patches as soon as available due to the varied nature of corporate environment. They don’t have one or two PCs to worry about: they can have tens of thousands. Downtime equates to money lost. So patches get tested before being deployed. Depending on the patch, that can be 48 hours to a week or two. Major OS upgrades can be months-long test, but the company usually does that and follows it while it’s still in beta.
Updates are pointed to a server the company controls, not the Internet. Updates get tested on test servers and test machines that replicate those in production. It typically gets monitored for 48 hours to measure glitches and performance. Once satisfied, the company controlled update server pushes into production machines.
Automatic updates are a thing and should be everywhere.
Absolutely not…most especially prior to production deployment. How else would someone see the change logs before hand or see/test if it would hurt their environment?
then rebased to ublue image because it has flatpak included in the image.
From Silverblue’s Getting Started Guide:
Flatpak is the primary way that apps can be installed on Fedora Silverblue (for more information, see flatpak.org). Flatpak works out of the box in Fedora Silverblue…
Just seems very odd to distrohop for one main reason (flatpak in this scenario), without even checking if that reason is available in your current distro…which it is, out of the box.
…when my Google search doesn’t take me where I need to go.
Tried Kagi?
No one offered to? Not even the business who runs the site nor the departments within said business who do the testing? From the link:
What we test - Canonical’s QA team performs an extensive set of over 500 OS compatibility focused hardware tests to ensure the best Ubuntu experience. Every aspect of the system is checked and verified.
Regular testing for up to 10 years - Roughly every 3 weeks, Ubuntu releases Stable Release Updates, ensuring a secure and reliable experience. These updates are carefully tested by the Hardware Certification team to make sure that systems work well with Ubuntu.
Our laboratories - Canonical conducts tests in dedicated laboratories, located around the world. The “Ubuntu Certified” label is applied to systems that have been verified and are continuously tested by Canonical throughout the Ubuntu release life cycle.
Sounds like it should be someone’s job at Canonical to update the list/site.
I used for a bit…
What changed?
There absolutely should be a Proton page to verify, in my opinion. Mullad has a banner on every page, and an indepth DNS leak test page.
Another cumbersome way to check is to do a curl on https://api.protonmail.ch/vpn/logicals (syntax depends on device you’re running it from).
Have you read their page about sudo? Gives some pretty good insight. For bonus points, at the bottom of that page are links for security and administration.
Wefwef is now Voyager.
And yet split tunneling and LAN access, combined with killswitch, are still broken on Android but work on Windows.