some of which are likely illegal.

👀

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.

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

Computer upvote this post. I mean comment. No, I meant the comment. Computer remove the upvote from the post. Computer upvote the comment.

Computer compose reply.

Dear Aunt, let’s set so double the killer delete select all

This is a horrible decision.

ATT … penalised smaller publishers in particular since, unlike the main vertically integrated platforms, they depend to a large extent on third-party data collection to finance their business

Cry me a fucking river.

Here is my actual autocomplete (first suggestion for each word):

The diagnosis is that the patient is a member of the family and has been in the hospital for a long time and has been treated for a long period of time and has had a very bad reaction to the medication and has been given a good doctor to treat the patient for a long term condition that is not a good idea to be honest with you.

An SEO ghoul’s wet dream.