I mentioned not too long ago that Mullvad was handing its resolver users over to Quad9. Sadly, I didn’t realize how accurate my concerns would be. Quad9 is a good operator, they actually fought Sony in a German court instead of quietly complying. Yet, they were still ordered to block the content. That’s the core problem. A blocking order is only as damaging as the resolver it impacts. Every time an operator shuts down and redirects its users to Quad9, it pools more users into one place. This makes the next blocking order even more valuable and effective for whoever files it. And now we're seeing Quad9 backing out of a market.
Mullvad talks a lot about decentralization, then hands its resolver users to one of the biggest resolvers going. Quad9 is a good operator, and they actually fought Sony in German court instead of quietly complying. They still got ordered to block. That's the problem. A blocking order only hurts as much as the resolver it lands on is used, so every operator that shuts down and sends its users to Quad9 makes the next order a better deal for whoever files it.
"What have you done for me lately?" Egypt controls the Suez, which is favorable for China's continuing oil import needs while they continue to accelerate off of oil.
> China has invested more than $10 billion in Egypt, building a business hub east of the capital, Cairo, and an electric rail line for industry in the Nile Delta. Annual trade between the two countries is estimated at $20 billion, according to government figures.
How does the GrapheneOS threat model account for baseband or firmware-level supply chain risks on Lenovo/Motorola hardware, given their historical consumer security incidents like Superfish? Is the open-source attestation sufficient to mitigate hardware-level tampering?
The use case is for tutorials and documentation pages. sandbox.bio embeds that terminal in all its bioinformatics tutorials and people find it useful to have an environment where you don't need to set anything up before you start learning. So I wanted to make it easy for others to embed a similar environment in their training materials.
I don't think there is much use to it other than fun little gimmick.
To that end, I could see it being sort of fun to run like "ls" and see the list of post categories, then do like "ls posts/" to see all the general posts, then "cat posts/i-am-a-post.txt" to read the post.
A few weeks ago, I came across a blog post with 5 git tips. I would have loved having an embedded terminal with some mock repos preloaded with the exact situation. That's the kind of use case I'm aiming at, not just the basic commands!
Well some of their keyboards also hypothetically have open source firmware yet upon introducing a hardware revision they never released the necessary files. I only know this because I actually wanted to purchase one of those keyboards specifically for the open firmware.
They still seem to be the best (approximately only) game in town if you want the ability to flash your own firmware to a standard off the shelf peripheral.
> This repository is currently in its early setup phase.
> At the moment, the repository mainly contains project scaffolding, policy files, and the initial project direction. Firmware sources, board support, build instructions, and flashing guidance are still being prepared.
> That means zgm is early, but it is intentionally early in public. The goal is not to wait until everything is finished before opening the door. The goal is to make the long-term direction visible and let the project grow into a useful open firmware platform in the open.
> That means zgm is early, but it is intentionally early in public.
"Intentionally early" is one of those phrases that means they vibed this README out in an hour with AI, and now hope that they can create firmware for it in the next 6 months.
Call me naive, but why not natively run the Nix package manager side-by-side with pacman. This allows one to safely use tools like Home Manager to manage their user environment and dotfiles declaratively while leaving the core Arch Linux base completely untouched.
That's not the final release, that's an RC and tech blogs should stop reporting this as final. There were instances in the past where the RC had critical bugs.
Yeah but not the Phoronix one ("Firefox 153 Available", "Mozilla has uploaded the Firefox 153.0 release binaries today"). Shame because Phoronix was kinda good in the past.