[-] biribiri11@lemmy.ml 12 points 1 month ago

I’m not sure if anyone said it was the fault of flathub. My point is that, regardless of fault, accessibility to the main instance is an issue for several reasons, and a good way to solve it is to build a system for mirrors.

[-] biribiri11@lemmy.ml 14 points 1 month ago

It’s not about funding. Many prefer mirrors because the main instance isn’t globally available (the GitHub issue I linked, for example, is all about people trying and failing to access flathub in China) or because they can’t for compliance reasons (many businesses already mirror stuff like epel, too, which is what throws off Rocky’s stat counters). Neither of those issues can be assessed by throwing more money at a CDN.

[-] biribiri11@lemmy.ml 14 points 1 month ago* (last edited 1 month ago)

The guy replying is a total dick, and for people that like to encourage change to create software that evolves with needs, they sure do refuse to change when needs evolve.

This is definitely just a dangerous cause of that one xkcd. At the very least, Debian unstable caught something before it could reach everyone else. That works, I guess.

[-] biribiri11@lemmy.ml 13 points 2 months ago

I’ve learned exactly 0 useful things at community college.

Funnily enough, this is why I left my university and went to a CC. The opportunities for me at a CC have been much greater (especially when it comes to part-time employment positions). The smaller course sizes in my digital design classes in Quartus Prime (which were not present in the lower division curriculum at my original university) allowed me to excel so much that I ended up as a TA for my class. In addition, because I wasn’t asphyxiating myself in a tiny auditorium of 400 people, I found it much easier to approach my professors 1 on 1 to talk about physics outside my course curriculum, which has helped me network and prepare to line up REUs next year. I feel as though the people at my CC are also more down to earth and hardworking than those at my university. The student leadership there didn’t feel as daunting, and felt action-oriented (as opposed to being a pure popularity contest), so I was able to join student government. What I have been achieving over the course of 6 months at a CC is infinitely better than what I was getting at a full university, and I am no longer depressed.

Everyone’s experience is different. In my case, my original university was highly hyped, and very expensive, but left me sorely disappointed, and I was not happy with what I’d be learning according to my course roadmap.

[-] biribiri11@lemmy.ml 12 points 2 months ago

Mmm Russian propagandists going hard today, or rather, as hard as ever, ensuring to amplify the messages of individuals who already have questionable allegiance to the US in the first place. Just keep in mind the Ukrainians still want to fight. It’s not like the US are the ones trying to kill the Ukrainian president to get their way.

[-] biribiri11@lemmy.ml 11 points 2 months ago

But how does this solve the problem of the config files of the various DEs (GTK rc files or other theme stuff) messing with each other in the home directory?

It does not. Your dotfiles will be a bit wrecked when you rebase. See: https://universal-blue.discourse.group/t/why-is-rebasing-between-desktop-environments-bad/690/4 It’ll also cause random issues like: https://discussion.fedoraproject.org/t/flatpak-apps-crashing-after-rebasing-from-silverblue-to-kinoite/83623/2

It’s mostly plasma fighting gnome, though. I haven’t seen any conflicts with say, sway.

[-] biribiri11@lemmy.ml 13 points 2 months ago

FWIW, gitlab-runner exec and earthly exist for running tests locally, with others things like nektos/act for GHA as a 3rd party solution. I’ll never get used to yaml, though, all my pipelines are mostly shell scripts. Using a markup language as a programming language was definitely one of the decisions of all time.

[-] biribiri11@lemmy.ml 12 points 2 months ago

In the back of my mind I know this is there, but the cat | grep pattern is just muscle memory at this point

[-] biribiri11@lemmy.ml 14 points 3 months ago* (last edited 3 months ago)

It’s funny, because there was research done by UC Riverside which specifically figured out LTS branches receive patches for CVEs significantly later than vendor specific branches. Specifically:

Interestingly, we note that the picked CVE patches appear in distributions 74.2 days earlier than LTS on average;

They also conveniently left out the part of Greg KH’s opinion stating that he recommends the use of vendor kernels over stable/LTS branches, too.

I found this particularly funny:

It all comes down to a delicate balancing act between security and stability. Some top Linux kernel developers and CIQ are coming down on the side of security.

Now I know CIQ is “supposedly” different from rocky, but what is CIQ going to do, break bug-for-bug compat and use stable kernels in their supported version of Rocky? This entire article feels like it doesn’t fundamentally understand that not all bugs (especially ones that lead to potential low-ranking CVEs) aren’t worth patching.

[-] biribiri11@lemmy.ml 11 points 3 months ago

Hah, those are the load times I used to get on my Xbox One with its dinky HDD. At the very least, The Midnight Ride has been updated to post next-gen, and I now get really small loading times (<5 sec) on my SSD. The game feels less rough around the edges, too. Only took 3 hours to set up :,)

[-] biribiri11@lemmy.ml 12 points 4 months ago

The US’s Department of Defense is one of Red Hat’s biggest customers. Other than that, the US government theoretically uses Linux quite extensively, going as far as making significant contributions such as SELinux. It was mentioned already, but academia uses Linux a lot, too. I saw lots of machines at SLAC running CentOS 7.

[-] biribiri11@lemmy.ml 11 points 4 months ago

It’d be dangerous if an installed app claimed to be something like sudo or bash. Even if a mechanism was created for flatpak apps to claim a single shell command, there is no centralized authority on all flatpak apps to vet them. If there was for flathub, and each uploaded package was checked, that still leaves every other non-flathub flatpak repo which must implement the same vetting. Because there’s no way to guarantee to do it safely, and because flatpak devs are unwilling to compromise, this is just what we get.

https://github.com/flatpak/flatpak/issues/1188

view more: ‹ prev next ›

biribiri11

joined 5 months ago