I disagree that it’s the same for multiple reasons: first off the project and telemetry were never profit-driven. Their goal was always to use modern methods of software development to make the software better.

The fact is, these days all for-profit projects gather a ton of info without asking, and then use that data to inform their development and debugging (and sell, but that’s irrelevant to my point). To deny open source software the ability to even add the option of reporting telemetry is to ask them to make a better product than for-profit competition, with fewer tools at their disposal, and at a fraction of the pay (often on a voluntary basis). That’s just unreasonable.

Which is why the pushback wasn’t that they were using telemetry, it was that they were going to use Google Analytics and Yandex, which are “cheap” options, but are obviously for-profit and can’t be trusted as middlemen. They heard the concern over that and decided to steer away to a non-profit solution.

But as a software dev and a Linux user, I often wish I could easily create bug reports using open source, appropriately anonymized telemetry reporting tools. I want to make making a better system for me to use as easy as possible for the saints that are volunteering their time.

As for the issues in tenacity, it was likely specific to what I was doing. I was rapidly opening and closing a lot of small audio clips, and saving them to network mounted dirs under different names. I remember I had issues with simple stuff like keyboard shortcuts to open files, and I had to manually use the mouse to select a redundant option every single time (don’t recall what it was), and I think it would just crash trying to save to the network mounted dir, so I had to always save locally and copy over manually. So I just switched back and continued my work.

Afaik, back when it all went down, they heard the public reaction about the telemetry thing and completely reversed course. On top of that, many distros would be sure to never distribute a build with telemetry enabled anyway. So there has never been any cause for concern. Would love to be proven wrong, though.

Also, Audacity is handy, but it’s not perfect, and I’ll gladly use a better alternative. But the last time I tried Tenacity, it had a bunch of little differences that made the tool just a bit harder to use. So I still default to audacity.

Yeah, but I think it can feel too much like a circle jerk around here sometimes. I get that people want to win over new users, but some of it goes too far I think. The fact is Linux isn’t perfect, and while no OS is, there are some critical things you can do on Windows that are still a pain in the ass on Linux. Some of that is a vendor/proprietary software problem, but a good chunk of it is just people being willing to overlook a thin layer of jank in their normal workflows.

I think we’d all be better off to all acknowledge and clean up the jank rather than try to pretend it’s fine as is.

There was a time when there was an annual “Linux Sucks” presentation that I liked because it was a roundup of candid, yet constructive criticism of Linux (and then at some point the person running that went off the deep end and started yelling about woke agendas).

I wouldn’t mind there being a whole community devoted to pointing out shit that is poorly designed or just broken when running linux, and we as a community then try to fix them or find workarounds.

But as others have pointed out, that community isn’t a community, it’s literally just one account hanging out by themselves.

On top of all the other informative comments answering a plethora of questions you understandably have when entering the Linux ecosystem, I want to express: don’t feel like you need to learn all this stuff if it doesn’t interest you, or otherwise turns you off the idea of Linux.

It’s perfectly fine to ignore all the terminology, install whatever new-user friendly version of Linux you can, and just start using it. If it’s not to your taste, or it asks too much of you, maybe try a different one. But I’m of the firm belief that immediately inundating a new user with a bunch of new vocab and unfamiliar workflows is the mark of a bad new user experience, and you shouldn’t feel required to put up with that.

The fact is, unlike MSFT who has a bunch of terminology internal to the windows dev teams, Linux is developed in the open, so all the terminology leaks into the user world too. And you just need to get good at saying, “if this doesn’t help me use my PC better for what I need it to do, I don’t care”.

Hah. Tactfully copied to disk intact*

Since btrfs uses Copy on Write, as long as the data makes it onto disk in tact, any further btrfs operations on the data will be safe against sudden power loss. It might need the opportunity to repair some stuff once power is restored (scrub), but the data (and metadata) should still be there and recoverable, not left in some partial state that can’t be resolved.

This is really interesting, will have to give it a shot. Wonder if it can be integrated into grayjay.

Man, imagine how hard people worked to make sure that perfectly good hardware would turn into a useless paperweight one day.

Make sure to check out the params on it. I noticed by default it disables the ability to switch tty via the keyboard shortcuts. Seems the main use for it is in “kiosk mode”, so they don’t want users to be able to escape the app easily. There’s a param to disable that so you can still pop over to another tty (I forget what it is off the top of my head).

I’ve found cage to be really convenient when you want to run a single app from a tty. 5s to start gnome + ff is pretty good, though. Not sure how cage would compare.

https://github.com/cage-kiosk/cage

What wayland compositor do you use for that? Have you tried cage?

Best to wait until the last second and switch cold turkey. What could possibly go wrong?

It’s only insane if you have them all running at once.

Whole article? It’s 10 sentences.

Bought a Pinecil a few weeks ago. No problems.

Lol ok, then I guess I didn’t understand what the alternative would be when you suggested putting the OSes on different partitions.

They’re definitely not suggesting having both OSes in the same partition (even though that is technically possible using winbtrfs, it is objectively an insane thing to do).

Looks like this is in the standard Fedora /etc/skel/.bashrc.

Debian GNU/Linux 12 dullbananas-macbookpro161 tty1

dullbananas-macbookpro161 login:

What more do you need?!

Lol but seriously,

Remove: ...gnome-shell...

That’ll do it.

You should consider setting up btrfs w/ Timeshift.