It can be done, but then whoever forks that will need to stay on top of keeping that fork up to date with other changes in the original chromium, and that gets harder and harder to do as time goes on and more changes are made to the same or related parts of the codebase.

Yup, the arugula/balsamic combo is the same way I’ve enjoyed pear pizza. Delicious.

Pear works well on white pizza

Become a Red Hat employee and you get one for free.

(genuinely, I know this sounds like a joke)

https://en.wikipedia.org/wiki/Peter_principle

This quote sounds a lot more like eugenics than euthanasia.

ctrl-f Kelly on that page

1. Boost has a certain app version. You can install the latest or find some older APK version to install, but older versions will only support a certain range of server versions.
2. The Lemmy instance you register with and use will be running a particular server version. There is nothing you can do about this, it’s up to the instance admins, but most instances are going to stay relatively up to date because lagging too far behind could cause federation/interoperability issues.

So even if making a new account on another instance running an older version works, it will only work for some period of time until that instance updates.

I’m not sure what bug you’re experiencing exactly, but it sounds like it could be either server side or app side. Either way, just sit tight and wait for a fix to be published.

I’m honestly surprised they made 10,000 sales.

When was the last time you saw a corporation making decisions and taking actions of its own accord, without people?

Maybe they will start to, now, as people delegate their responsibilities to “AI”

AI on its own isn’t a threat, but people (mis)using and misrepresenting AI are. That isn’t a problem unique to AI but there sure are a lot of people doing dumb and bad things with AI right now.

You can check the release notes to be sure, but generally you can just perform the update and move on with life. Backing up your data is always a smart precaution.

Generate the binaries during test execution from known (version controlled) inputs, plaintext files and things. Don’t check binaries into source control, especially not intentionally corrupt ones that other maintainers and observers don’t know what they may contain.

That sounds like someone who topped out with highschool level programming tried to implement a hash algorithm.

You can use it for normal applications that aren’t sort of “system components” like a VPN. So if you want to install some office/productivity software, or a web browser, or a music/video player, then a Flatpak would be a reasonable choice. For most of those cases you would probably still choose the RPM if it is available, but Flatpak is also fine if not.

That’s because YAML syntax is a superset of JSON. Any YAML parser should also accept JSON, not just the one k8s uses.

!cars@lemmy.world could be a starting point

I know I’m not the only one but I’ll say it anyway:

Altoids Sours.

Fuel cell EVs can’t be fitted with charging plugs for religious reasons

I really need to hear that story.

iPhone 4 antenna “you’re holding it wrong”

iPhone 6 folding

Wireless mouse charge port on the bottom

Apple pencil charging on the iPad

iPads with display bright spots due to structural adhesives underneath letting go and cables pressing up

MacBook butterfly switches

Garbage cable quality all around