joojmachine @ joojmachine @lemmy.ml

Designer, artist, part of Fedora's marketing team and ferociously communist

---

Read more

Posts

169

Comments

205

Joined

4 yr. ago

Your setup is already pretty good, but I can recommend Silverblue with my personal use.

Not OC, but per my last experience with it NVENC was way easier to work with.

You install the NVIDIA drivers, you install CUDA libs (in Fedora that's separate, at least) and it works.

For AMD, you need to figure out that you need the proprietary driver for AMF (which didn't have a proper installer for anything that wasn't Ubuntu the last time I tried it) or be stuck with the unfortunately not as good VAAPI. After that you usually had to hunt for guides on how to use the encoder in the program you want (OBS used to be a particular nightmare for it, hopefully it got better with time).

I hope things got and continue to get better, specially since I'm 100% going to get an AMD setup after my laptop eventually dies.

I really hope it does well, the business model really needs to change.

Everyone has to start somewhere. Mine was to create the .po files to translate a small program.

but my English is not fluent

that is one big barrier to entry that we should have at least some focus on trying to solve, depending on the distro you use they might have some communities that speak your language, on fedora we have a bunch of language-specific communities on our Matrix server, where people usually offer to help whenever needed

why the fuck would Asahi go with a Red Hat distribution!?

Because it isn't? community distro with RH sponsorship != RH distro

And to answer the question, because we asked and because we have the infrastructure to better support their project in a way they only need to focus on development, it's literally written in the blog post.

Simple, OP and some people just don't know what they are talking about. There was no "aesthetic reason".

One of the big changes in GNOME 40 (that would be 3.40) was the introduction of GTK4. People used to assume that the gnome major versioning scheme was tied to GTK, so loads of people were asking the devs when GNOME 4 was coming out.

To demistify this idea of one being tied to the other they just dropped the "3.", specially since that part wasn't that relevant and started with the 40.

the TL;DR is people were coming from HN to harass one of Asahi's devs mainly for being a trans woman

I can't say I am suprised but I sure am glad that the Asahi SIG has been so successful.

Kudos to everyone involved!

and how exactly does having telemetry (that can be easily turned off at any time) impedes your freedom to be left alone?

It's not mistaken for context, you're just missing the point. The switch is just part of it, the user would still have to consent to send their data before it is sent and the proposal proposes to have it detailing the data that is going to be sent and explaining the process.

Having it as a default guarantees it doesn't scare non-power users away from it. It's not about just having people clicking next and accepting it without consent.

Wrong again, the "switch" only sets the setting itself, but before finishing the setup process the user would be provided with a confirmation detailing the data that would be sent and provided with the option to send it or not. The process would have user consent.

Highly disagree. Although I'm not content with RH's decisions during the last few months (especially when it comes to their layoffs), this one shouldn't even be a controversy at all. It's just a proposal for a community project. There will be no RedHat threats or higher-up decisions without the consent of the community. That's the main difference between Fedora (which does have deep ties with RedHat but is through and through a community project) and RedHat (the downstream entreprise).

And once again, it isn't "without consent", it just means that the default state of the checkbox is on. Users will still be presented with a confirm option before any data is sent.

In other words, unbiased telemetry is not possible to do ethically.

Say that to the opentelemetry and Plausible folks, who have been on the vanguard of doing exactly that for years now.

No, this is not "ruining your beautiful Fedora", this is a proposal that both us users and the developers can pitch in to develop telemtry in a way that does not abuse its users.

And about the opt-in/opt-out nature of it, feel free to join the follow-up discussion about it on the forum:

https://discussion.fedoraproject.org/t/opt-in-opt-out-a-breakout-topic-for-the-f40-change-request-on-privacy-preserving-telemetry-for-fedora-workstation/85395

No need to apologize, I'm not mad at you, I found this thread while checking if someone had already posted it before doing so myself.

That's the worst part, to be honest, it's not even ragebait yet people just take everything at face value and start to spread FUD.

Right? People are reading this as BIG CORPO DOES BAD DECISION and ignore the fact that they can (and should) go to the forum to actively discuss the proposal with the people proposing it.

Please read the thing properly. It is nothing more than a proposal currently, which is being actively discussed with the community to make sure that users (including you) are satisfied with the result if it is implemented, or to make sure it is not implemented at all.

The problem with opt-in telemetry is that it messes with the scope of the research.

If you want to understand something about most users (and not just the ones that are active enough in the project to participate in opt-in) you need this, otherwise your results only tell the needs of this subset of your userbase and this sometimes can go completely against the needs of the majority of users.

The problem with telemetry isn't the telemetry itself, is how it is used, and the way the proposal is worded makes me very optimistic. They are trying 200% hard to make sure we understand that it will never be used in violation of the users' privacy.

How, exactly? They've been saying from the very beginning that they don't need or want personally-identifiable data.