I expect an upcoming patch will check during boot whether the fix is needed and only apply it for those old systems

Garage leverages the theory of distributed systems, and in particular Conflict-free Replicated Data Types (CRDTs in short), a set of mathematical tools that help us write distributed software that runs faster, by avoiding some kinds of unnecessary chit-chat between servers.

Huh, “avoiding some kinds of unnecessary chit-chat” is the weirdest benefit of CRDTs to mention here (and I’m not sure it actually is a benefit)

I would have pointed out that they help multiple devices safely synchronise copies of data, or something 🤷

The word “efficient” doesn’t even appear in the main part of the Wikipedia page (just once in the footnotes): https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type

If the USA and it’s allies were truly enthusiastic about human rights and democracy, then they should find out how much a company saves by having supply chains with worse human rights protections, and tax them some portion (I’d say at least half) of that saving

To encourage them to employ more expensive staff in countries with decent democracy and human rights laws

(And encourage other countries to transition to better human rights frameworks)

I wonder if the monitor for an output/sink is enabled as an input/source? Using a pulseaudio control panel like pavucontrol might show you more information? Most distributions provide pulseaudio/pipewire as a useful layer on top of ALSA, so pure-ALSA tools like alsamixer might not be showing you the whole picture

Might be worth trying a bunch of different live USBs to find a distribution with a working sound setup, and then seeing what it’s doing differently compared to Zorin

never attribute to malice that which is adequately explained by stupidity.

https://en.wikipedia.org/wiki/Hanlon's_razor

Anyone who thinks it’s actually because of silly things like “not wanting to be associated with such a disgusting, festering cesspool of a site” is naïve.

Not sure where you got this from, this didn’t seem to be in the CloudFlare blog post anywhere

In theory, a government is democratically-elected, and courts are democratically-controlled, so isn’t a corporation obeying laws and courts exactly what we want here?

I’m not sure we can expect them to go above and beyond what is legal, no matter how much we might wish them to do so, they simply wouldn’t exist for very long otherwise

We hated them (and they hated it, too) when they extra-judiciously blocked traffic they didn’t agree with in the past, so surely requiring laws/courts to do so in future is better?

Seems like Cloudflare have come up with other ways to avoid blocking content they disagree with:

For instance, when a site that opposed LGBTQ+ rights signed up for a paid version of DDoS mitigation service we worked with our Proudflare employee resource group to identify an organization that supported LGBTQ+ rights and donate 100 percent of the fees for our services to them. We don’t and won’t talk about these efforts publicly because we don’t do them for marketing purposes; we do them because they are aligned with what we believe is morally correct.

Perhaps what we could do is have a preference that is like Firefox’s privacy settings (standard versus strict), as a way for the user to tell NetworkManager their risk-appetite and which set of default behaviours is more appropriate?

It would be even better if this was a system-wide

Look, everything here is a good suggestion for someone who knows what they are doing, but all of them have the potential to have some impact on the user experience in a variety of negative ways

MAC addresses should be randomised by default, but only when scanning and when connecting to untrusted networks, but how do we know that a network is untrusted? Many newer open networks (e.g. at restaurants, resorts, hotels, parks, etc) use a WPA2-PSK instead of an unencrypted captive portal, so it’s not true that a WPA2-PSK means a network is trustworthy

So, we’d have to prompt the user to ask them, but now we need to explain the risks and why they should care, and we now also need to help inform the user and offer to reverse this choice if it’s not compatible with the network they really want to join

The UX for dealing with all of these suggestions becomes complicated pretty quickly

A privacy-minded person will appreciate the extra knowledge of what their system is doing, but someone trying to switch from Windows or macOS is probably going to be confused unless developers spend a huge amount of time considering every possibility (spoiler: many won’t)

Alternative title: please make it impossible to get normal people to like Linux

I dearly wish Google would switch back to contextual advertising, and then add proper tracking protection to Android and Chrome out-of-the-box

It’s frustrating knowing there are talented security-minded and privacy-minded folks at Google who aren’t allowed to ship any code that would jeopardise the money tree

Not a mesh yet, hence the hypothetical :)

Not a mesh yet, hence the hypothetical :)

https://twitter.com/gitlab/status/1555325376687226883

We discussed internally what to do with inactive repositories. We reached a decision to move unused repos to object storage. Once implemented, they will still be accessible but take a bit longer to access after a long period of inactivity.

Yeah, I think there are some cases where it’s a performance thing, sure: e.g. a list that displays a few hard-coded common options, and is repopulated with personalised options once they’ve been fetched from a back-end

I discussed this over here, too: https://aus.social/@jokeyrhyme/108700536951949858

I’m still a subscriber, and I greatly prefer the user experience of Netflix (as imperfect as it is) compared to Disney Plus or Amazon Prime Video, or even YouTube

It’s almost as though nobody at these companies even tries to use their own apps

Yeah, we need the different architectures to be roughly equal in market share, so architecture-specific problems like this don’t hit everyone

I’m wondering if we’ll see designs shift away from speculative execution in general, in order to avoid this entire class of attack?