I’ll have to thanks Lumen contributors (Google first). I’m not worried about Google de-indexing them, but I’m,more worried about others (I have experienced lacking result on DuckDuckGo (and Bing, that they use) over what I can only assume is wrongfull (and non-transparent) DMCA (first with ListenBrainz).
I’ve switched to Brave. Work better.
Well… That seems uselessly risky and complex when you can just ask them to not do that. The issue tracker said the Youtube folks have been informed. Let’s just see if they fix that rather quickly. (but they are certainly not the only one with that kind of stuff. I’m not a big fan UA discrimination. I mean, this kind of stuff is what webcompat is all about.) (except for some purpose where you truly care about the architecture, like selecting a download link for an installer) (on the other side, I’m totally fine with feature-flags based discrimination, but that need to be done client-side).
To start this project, you 1. Install Nix and 2. Run nix run (god I really love Nix. When it work. And use IFD to not have to manually update a single hash/run a command when you update the lock files.)
Well, I’m not that pessimist, at least not on those 2 points. I hardly see how CSP would prevent addon to do their stuff, as CSP is protection against cross site attacks, and extension aren’t sites (thought I actually remember having an issue like that once making an extension, but correcting the extensio’s permissions solved it).
And DRMs only apply on the video stream. It won’t protect the webpage or the javascript. Plus there are content on youtube that they are contractually required to not put behind DRMs.
What I’m worried youtube will do is simply that their server will refuse to send the video until a certain time after the user load the page, thid time corresponding to a bit less than the time the user would wait by playing ads.
It won’t force the user to watch ads. But it’ll deincensitive it by a certain amount.
This article clearly is just about the public DNS resolver. Using cloudflare to register a domain is well different, in particular cause it’ll play a “significant” role to make it accessible. (as 1. it is not neutral (you need to be a customer) and 2. Removing a registration will block it for everyone).
Next year (1st january 2024), it’ll be in the US (but just the first version from Steamboat Willie and The Gallopin’ Gaucho)
I can confirm I have already some experience with the fact of VPN usage being flagged as a high change of automated traffic (except it was TOR, which is pretty much identical in this context).
Discord put me a wealth of captcha, Wikipedia refused edition of pages (even with my account. Which IMO looks like an oversight). And many pages just had captchas even when not trying to log-in.