Your data has monetary value to google. Giving them access, without getting any money from them (or even knowing what ways it will be used) is not something you must do.

To be fair, while you may not be getting money in its direct form (cash, bank deposit, etc) from Google, they are providing you a service which costs them money for free. So they are providing something of monetary value.

Only the individual can determine if their data is worth that free (to the individual, not free to Google) service. I’m assuming that most people in a privacy community would be against that, though.

Graphene sucks the life of android in my humble option.

What’s not “fun” or lifeless about it? It’s a phone. I use it exactly as I would a normal Pixel, with the exception of having the convenience of Google Wallet.

Everything is about security with anything else being second.

Would you rather it be all about fun/having life with everything else being second? That doesn’t sound safe. And I’m still confused about you saying it having no life.

I will say what I do differently vs a normal Pixel, is I use the storage scopes and lock certain apps to certain folders as well as contact scopes to lock certain apps to only see certain people. I don’t use my phone for work, but if I did, that would be a separate profile/user.

• The video is a return to the creator’s previous “Top 5 Linux Apps” monthly series, which was popular in the past.
• The first app highlighted is Boxy, a graphic design tool for creating SVG images and logos, with a user-friendly interface compared to more complex tools like Inkscape.
• The second app is Eyedropper, a color picker tool that works well in Wayland environments and allows users to get color codes in various formats.
• The third app is Iotas, a simple, GTK-based note-taking app with Nextcloud integration, focused on basic note-taking functionality without advanced features.
• The fourth app is Plexamp, an electron-based desktop music player that provides access to the user’s Plex music library.
• The fifth app is Sigil, a niche tool for editing metadata in eBook (EPUB) files, particularly useful for adding series information to support self-hosted ebook platforms like Calibre.
• The creator acknowledges that Sigil has some quirks, working better in KDE than GNOME environments.
• The creator encourages viewers to provide suggestions for future “Top 5 Linux Apps” videos in the comments.
• The creator provides links to their social media and support platforms, including Mastodon, Odyssey, and Patreon.
• The overall tone is one of enthusiasm for sharing useful Linux applications with the audience, while also acknowledging the niche nature of some of the recommendations.

Courtesy of Kagi’s Universal Summarizer.

if used for work…Features? Don’t care.

Most organizations care about maintaining document compatibility, especially formatting, and that usually means Office365. Microsoft is notorious for publishing a standard and then ignoring their own standard, making it exceedingly difficult to use other office suites.

I’ve heard OnlyOffice does the best at maintaining compatibility.

With most PC things (RAM, disk space, CPU, etc etc), too much is better than too little, provided you have the resources.

There are no legal restrictions on cryptography in the US

That’s not what a quick search and Wikipedia says. To be fair, I didn’t fact check all their references:

https://en.m.wikipedia.org/w/index.php?title=Export_of_cryptography_from_the_United_States

backend of a sword

You mean the hilt?

People still use Ubuntu?

They’re currently number 6 on DistroWatch’s Last 6 Months. So people are at least still interested in it.

The DistroWatch Page Hit Ranking statistics are a light-hearted way of measuring interest in Linux distributions and other free operating systems among the visitors of this website. They correlate neither to usage nor to quality and should not be used to measure the market share of distributions. They simply show the number of times a distribution page on DistroWatch was accessed each day, nothing more.

NC is not for code.

No, they’re doing it for their comment, not suggesting others use it for code. It’s the new take on “I do not give Facebook permission to use…” trend that went on years ago.

It literally doesn’t. Please stop lying. Everybody can see you lying.

We’re done here, kiddie.

Calling me a liar (when it’s easily provable I’m not, I even included a screenshot for you) devolving to insults, calling me a kiddie and an idiot? If you can’t even formulate an argument without insults and you fail twice to read a link, yep, we’re done. Enjoy your day/night.

Nowhere in your link does it actually say that.

It’s hard for me to take you seriously when it does and I literally copy/pasted from the link. Even if you don’t read the whole page, you can’t even do a CTRL+F correctly.

I’m saying their source code is available to its users for auditing, changing, redistributing without risk of being sued for intellectual property violations.

Closed source means computer programs whose source code is not published except to licensees.

We’re saying the same thing, you just refuse to attach “closed source” to its definition. So answer me this: can anyone freely use it? Can only licensees use it? If the answers are no and yes respectively, that’s closed source.

I’m saying nothing of the sort.

You absolutely are. You’re using the word’s definition (source code available only to licensees), but won’t say the actual word (closed source).

if I were to call anything about it weird, it would be the use of a derpy, chonky dinosaur

Bluefin is a Deinonychus antirrhopus, a theropod dinosaur whose name means “terrible claw”. Discovered in the 1960s, she revolutionized our understanding of dinosaurs. Before Deinonychus, dinosaurs were often seen as slow, dim-witted creatures. However, she shattered these misconceptions, offering insight into the dynamic world of hot-blooded, rapidly evolving animals that were masters of their domain. We aim for our desktop to embody a similar nimbleness. Power and adaptability.

If you’re a customer of theirs, you can see the source code.

Are you saying that their source code is not published except to licensees?

You’re basically saying that something isn’t wet, it just has water on it.

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.

Why test patches before deploying to productions?

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?

with limited budget, what is the best way to get as many people as possible to have their communications encrypted?

They could dump their existing code that let users SMS non-Signal users and upgrade it automatically to E2EE if the other number has Signal. Oh wait, that would worth adoption, nevermind.

If I had to complain I wish they had used easy access bottom panel ports so you don’t have unscrew all 12 screws to access things like RAM and m2 slots.

How often are you switching those out where you want quick access?

Yeah, I’m not saying it’s hard, just illogical. To me, it came across similar as: “I’m moving to this other distro because they have Firefox.” Your current distro also has Firefox, so why are you moving again?