V ‎ ‎

They also claimed to have “quantum” phased radar. Until we see it in Janes or other OSINT it isn’t credible.

It was rhetorical.

Unfortunately the problem lies with the foundation. The one thing they made worth a damn in the past decade was Rust, and they promptly fired the whole Rust team. Servo is maintained by the Linux foundation now ffs. What does the foundation do besides zombie walk and eat Googles money?

Same. Install Firefox on a ChromeBook, which are almost all universally low powered, then watch it chug.

I don’t care how long the former CEO has been involved with the foundation, she has not been good for Mozilla.

I said something similar once before when they first announce me their decision to kneecap themselves, but it’s worth saying again:

They gained nothing from this decision. We used CentOS to trial deployments to prod servers running RHEL. We like how stable RHEL was. We appreciated the service agreements. We especially like how CentOS freed us from worrying about licensing. Their boneheaded decision ruined all of that. Before I left we had plans to migrate off RHEL (I asked an old coworker they actively are) because we can’t trust IBM not to Oracle us with some other world-ending BS in six months. Hundreds of RHEL servers and licenses gone, for what? They lost control of the open-source narrative when they shotgunned CentOS, and now the community initiative is led by people who don’t like them. Do yourself a favor and make it a priority to achieve Linux platform independence before RedHat is further Borgified by Big Blue.

Funny how the EU council considers iOS to be a big problem but not Microsoft’s behavior around Edge. Both need to be corrected, but only one has seen any action - and it ain’t Microsoft.

Over the past five years infosec has turned into a shitshow of showboating. Every exploit has to have a logo and catchy name. Attacks are widely hyped up despite the conditions for usage being extremely difficult or outright stupid. If you are assigning blanket permissions to a group that shouldn’t have it that is your fault. Obstructing stupidity is not in the scope of the container engine.

https://gohugo.io/

Free themes are available on their gohugo repo and there a plenty of paid ones. I enjoy the live reloading and ability to change it all easily with text files.

I used to use Ghost. Mostly on Hugo these days.

Usually trim runs on a cycle, either invoked by the OS or triggered by the drive. The time between trim and you deleting the files may see a performance hit as the firmware has to check if the blocks are in use, rather than knowing beforehand if they are.

Having used both:

Debian is very easy to manage, it has the one of packages and mostly sane defaults. Ubuntu’s user friendliness owes a lot to Debian. I do not like the state of package management however. Dpkg is in need of some upgrades, and the deb package format has some security concerns.

Rocky, being RHEL-derived is, as expected, exceptionally stable. I personally find DNF to be the superior package manager and I have historically run into fewer issues with it. Repos are extensive, especially with copr and fusion, but not as good as Debian.

For a simple home server use Debian. If you want experience with enterprise Linux use Rocky.

To add to the list of resources:

Todaku Books offer leveled difficulty, so even if you are starting out with Japanese there is something for you to read. The books are Creative Commons licensed, so don’t pay for them if you don’t want to.

https://tadoku.org/japanese/en/what-is-tadoku-en/

Incredible how fast we see flatpak improving and spreading throughout the ecosystem.

Their CEO is the biggest symptom of their problem. She demands a sky high compensation despite her poor leadership. The company has been in a spiraling decline for the past decade now. Instead of focusing on bringing a great user experience, they alienated their most staunch users with things like Pocket and allowed PWAs and Electron to eat their lunch.

Hi to run into this problem. I have a Mac mini that I use as a bridge from my home network to my work laptop. Now, most workloads requiring horsepower, I will run in the cloud, but there are some workloads that I want to run locally. I can parsec into the Mac, but I can’t parsec into the Linux server I have. The state of media on Linux is not great, and there are understandable reasons as to why.

People really dislike it when you point this out, But the security model on Linux is lacking. Yes, we have things like apparmor and SELinux, but compare it to sandboxd on macOS. The windows sandbox isn’t perfect, but it’s really user-friendly, and it works in most cases. Linux doesn’t have a direct equivalent. We’ve made great strides with making immutable distros through things like flatpack, and snap, but something that they failed to do is implement a least privilege model that is as robust as sandboxd on macOS.

SUSE is weird but their YaST was compelling enough to make them an option. Cockpit in RHEL doesn’t compare. I think that having admins edit text files is bad. The capability should be there, but it should not be mandatory. Editing files manually instead of a GUI increases the odds of a mistype trashing the system.

Even in the most stable distros I’ve had this issue. We had a RHEL 9 server acting as a graphana kiosk and it failed after an update. Something dbus related. I’d love to know why, as it’s been the only failure we ever had but nonetheless it shakes confidence. Windows 11 updates trashed three servers, one to the point we had a to fly an engineer out. My hope is that immutable distros fix this.

Fam if I walk into a cafe and I’m about to order and there is a bathroom that costs money I am going to leave. I get why they are doing this (hint it isn’t just the money), but I’ll be fucked if I’m going to tip them and pay to take a piss too.

Additionally, the claimed infringement relates to the fact that it’s reflective pulse oximetry using three or more sensors. Your Garmin and old Apple watch aren’t infringing because they use two sensors. I think the patent in its current state should not have been granted. It would be like patenting the placement of three or more CPU sockets on motherboards that fit in a certain rack size.