People on the Turkey subreddit were running a campaign to move from X to Bluesky

I see so much astroturfing for Bluesky. They have good PR people who know what buttons to push, clearly.

RepRap is the OG of hobbyist FDM printing.

Reportedly, an updated 12V-2×6 power cable is implicated, as opposed to the older but closely related 12VHPWR cable, which is a worry.

For the record, the card in question was a Zotac RTX 5070 model paired with a Seasonic Focus GX-750 power supply. It’s worth noting that it was the cable that suffered unambiguous damage here, not the graphics card or even, seemingly, the power connector or socket.

What’s the TLDW?

Google 🤮

Both comments are correct.

I haven’t used any of them, but in addition to the suggestions here, there is also Infomaniak which is a Swiss provider. They seem to have better reviews on trustpilot.

Can you stop posting Torygraph right wing propaganda?

Link to the patch?

prove that we’re using copilot to generate code

How do they expect you to do that? And are they capable of telling the difference if you lie about it?

It sucks for FOSS projects, but you have to imagine their rules from the perspective of someone who is actively trying to bend the rules to avoid giving Valve their cut. If they make an exception for FOSS projects, then every indie developer will claim to be “Shareware” and solicit donations off-platform.

Even Epic Games tried this and ended up in a lawsuit with Apple.

That’s great, but was it a smart idea to register a domain name in a TLD whose root nameserver is Verisign (an American company)?

some of which are likely illegal.

👀

Which one?

Passing power through doesn’t have to put noticeable load on the GPU.

I specifically said thermal load. Power delivery always causes heat dissipation due to I²R losses.

This must be for commercial displays where it is beneficial for installation to have power and data over a single cable.

I can’t think why I would want power delivery to my PC monitor over the display cable. It would just put extra thermal load on the GPU.

We will have to watch closely how Mozilla implements these standardized consent dialogs, because this could be a devious way of obfuscating from the user whether the app uses their data in acceptable or unacceptable ways. I wouldn’t put anything past the new surveillance capitalism friendly Mozilla Corp.

The article doesn’t link to the source, which is this post:

https://blog.mozilla.org/addons/2025/04/03/rethinking-extension-data-consent-clarity-consistency-and-control/

Today, our Add-on policies dictate that any extension that collects or transmits user data must create and display a data consent dialog. This consent dialog must clearly state what type of data is being collected and inform the user about the impact of accepting or declining the data collection.

Whilst the policy is a great example of Firefox’s commitment to transparency and protecting user data, it can add significant overhead for developers who want to build on our platform, and it creates a confusing experience for end users who often encounter many different data consent experiences for every extension they install. These custom data consent experiences also increase the time it takes for add-on reviewers to process a new extension version, as they need to verify this custom code is compliant with our policies. We’re simplifying how extensions gets consent to collect data

In 2025 we will launch a new data consent experience for extensions, built into the Firefox add-on installation flow itself. This will dramatically reduce the:

• development effort required to be compliant with Firefox data policies
• confusion users faces when installing extensions by providing a more consistent experience, giving them more confidence and control around the data collected or transmitted
• effort it takes AMO reviewers to evaluate an extension version to ensure it’s compliant with our data collection policies

Developers won’t need to bother with creating their own custom data consent experiences. Soon, developers will simply be able to specify in the manifest what types of data the extension collects/transmits and this will automatically be reflected in a unified consent experience across all Firefox extensions.

The DHT exists and is already a fully distributed system.

Even without the DHT, there is no centralization in Bittorrent that would lend itself to federation. Anyone with a complete copy of the data can already start their own tracker.

Do you perhaps mean a federated content index that links to torrents or magnet URIs?

Try it again without Ventoy

Yeah, because they’ve been doing this to us plebs for years now.