lemmyreader
not much
Was about to post the great blog post from my bookmarks, but another commenter beat me to it (t y !). Here’s comments on that blog post on Lobsters and HN :
Yes and no. Code development for Nitter has officially stopped afaik, but there are still some instances not completely dead.
- https://status.d420.de/ Nitter Instance Uptime & Health
Yes, gdebi :
This article is about Mobifree https://f-droid.org/en/2024/05/24/mobifree.html As far as I can see F-Droid mentions that it will be a contributing partner :
For more than 14 years, F-Droid has been developing solutions which act as pieces of the alternative mobile ecosystem puzzle. So it was a natural fit for F-Droid to become a contributing partner in the broader Mobifree project.
F-Droid playing a role :
F-Droid will play a major role in this project, tasked with creating a decentralized distribution system for developers to deliver apps to Android users.
Help to create the NGI funded project Mobifree :
F-Droid is one participating organization who has joined forces to help create this new mobile ecosystem. However, additional input, expertise, inspiration and work will be needed in order to break the traditional framework established by Big Tech. From community outreach to legal support, from developers, to researchers and end users, we welcome all forms of support.
I don’t read that F-droid will force ads on F-Droid on users any time soon. I can imagine F-Droid will continue to exist as it is but I could be wrong.
Tested playing a video with an Invidious instance right now and it worked. Did you try another instance ?
Windows does have a fallback mode called safe mode and that’s exactly what’s being used to fix this utter mess.
The other fix was reboot your Windows computer at least 15 times.
Package management isn’t going to save you from this as it didn’t save the Linux systems affected last time. It didn’t stop Arch Linux from failing to boot after a Grub update either.
Not everyone was affected though :
How come not everyone was impacted?
Prior to the most recent version, grub only registered the fwsetup if detected support. If your machine detected support, you would have had the fwsetup command registered and the failure wouldn’t occur.
There’s more to it. The mono-culture is one thing, but rolling out the update to millions of computers on the same days sounds like a bad idea.
Fun fact in 2008, with nuclear submarines, the mono-culture was not that bad yet.
It’s interesting to note the UK went with a Windows XP variant and not Windows Vista, which is marketed as the more reliable OS. The USA never made the same calculations: The American Navy runs on Linux.
fans start rotating for a few seconds and then it shuts down.
That could mean the CPU is getting too warm. Does the CPU cooler still work okay ?
