Down-voting every youtube link is indeed the only individual action that can be taken in the current system. It could theoretically lead to a YT link being folded or sunk lower. Tricky though because people should know why their YT links get down-voted. Ideally you would be able to tell them in a response. But I think I know how that would go: people with digital inclusion principles have actually become a diluted small minority in the fedi. A flood of lemmy.world folks who would follow the crowd off a cliff would down-vote your reply and up-vote the YT link in solidarity of their favorite walled gardens.

You could DM the reason for down-voting. But then the problem does not get the exposure it needs.

The fedi has evolved like Burning Man. The movement was true to its founding principles early on but as the crowd grew over the years it became enshittified faster than a digital rights subculture could take hold.

BTW, I should mention that sh.itjust.works is also a centralised Cloudflare node.

My point still stands.

Of course it doesn’t. Your point doesn’t even grasp the problem. You think the problem is that fedi users have (or have not) entitlement to content. It’s a red herring. You cannot begin to solve a problem you do not understand. It does not matter who is “entitled” to the content. The content is exclusive; locked inside a walled-garden with a gatekeeper. The problem is that exclusive access content is being linked on an open content platform and shoved in the face of readers who do not have access to the closed content.

The moment you are using someone else’s platform

Again, you still fail to grasp the problem. Using someone else’s platform is not a premise. You can either be on someone else’s node or you can be on your own self-hosted node. Either way, exclusive links are in the reader’s face.

How can you get so many things wrong… then you claim using one platform inherently revokes rights outside that platform – of course not. Irrelevant regardless, but rights granted on one platform do not diminish rights on another.

you loose the rights to the content outside of that platform.

It’s not about “rights”. That’s a legal matter. It’s about digital inclusion (a technical matter). People don’t want to see links that exclude them. It’s just pollution.

better than what? I’m not understanding your comparison here.

You’ve misunderstood the problem. It’s not a fix to access content that’s needed. The question is how to fix the pollution: exclusive walled-garden links appearing outside of the walled garden (where not everyone has access or is part of the special club of Google/Facebook/Cloudflare patrons). How did you misunderstand when I mentioned a toggle? And the title… how could I make the title more clear?

But at some point to interact with any kind of large company … You could also consider not interacting with large companies at all

Actually the large corps are more likely to hold the data in-house. Small companies cling to outsourcing. E.g. credit unions are the worst… outsource every service they offer to the same giant suppliers. Everyone thinks only a small company has the data (and consequently that the small dataset does not appeal to cyber criminals) but it’s actually worse because they outsource jobs even as small as printing bank statements to the same few giants most other credit unions use. Then they do the same for bill pay with another company. It’s getting hard to find a credit union that does not put Cloudflare in the loop. So in the end a dozen or so big corps have your data and it’s not even disclosed in the privacy statement.

Of course it depends on the nature of the business. A large grocery chain is more likely to make sure your offline store purchase history reaches Amazon and Google than a mom & pop grocer who doesn’t even have a loyalty program.

Whether businesses get copies of information is usually included in a site’s privacy policy,

I have never seen a privacy policy that lists partners and recipients apart from Paypal, who lists the 600+ corps they share data with for some reason. Apart from bizarre exceptions privacy policies are always too vague to be useful. Even in the GDPR region. If you read them you can often find text that does not even make sense for their business because they just copied someone else’s sufficiently vague policy to use as a template.

If you really want to limit your information exposure, you either have to audit everyone you do business with this way (because most large companies do this) or hire someone (or a service) to do it.

The breach happened in a country where companies are not required to respond to audits. No company wants any avg joe’s business badly enough to answer questions about data practices. In the EU, sure, data controllers are obligated to disclose the list of parties they share with (on request, not automatically). And even then, some still refuse. Then you file an article 77 complaint with the DPA where it just sits for years with no enforcement action.

My approach is a combination of avoiding business entirely, or supplying fake info, or less sensitive info (mailing address instead of residential, mission-specific email, phone number that just goes to a v/m or fax). This is where the battle needs to be fought – at data collection time. Countless banks needlessly demand residential address. That should be rejected by consumers. Data minimization is key.

In the case at hand, I’m leaning toward opting out of the class action lawsuit and suing them directly in small claims court. I can usually get better compensation that way.

Exit nodes are temporary unless you deliberately pin them for a particular connection, which I have not done for the DNS servers. The problem manifests without exception for weeks now, so it could not be attributed to a bad exit node. The tor microdescriptor db tracks the perms of every node, so I don’t think it would create a circuit for disallowed traffic. There could be an inconsistency between the microdesc and reality, but it would have to be a replicated inconsistency for every connection attempted with torsocks and yet not replicated on any connection made using the torsocks alternative (which works).

Which torsocks version? Yours is probably newer than mine. It seems to be a problem with torsocks 2.3.0 and only with dig. And indeed there is nothing wrong at the network level because I was able to do an MX lookup over tor using a different method than torsocks. I’m also able to use other apps with torsocks, just not dig all of the sudden.

I agree.

One of the reasons no one gives a shit is there is never news about CF making use of that MitM position. But I know they hire data scientists and what corp can resist the urge to monetize data they have access to? So I think it’s just a matter of time before they get caught abusing the vast amount of valuable data they have visibility on.

Sorry I do not know if BBC interviews are transcribed.

But FWIW it will air again on BBC World Service at 02:32 GMT tomorrow and the next day (which could be useful for those on limited internet connections)

Regarding the two suggested search services which are both Microsoft syndicates:

• #DuckDuckGo: hosted by Microsoft and searches are outsourced to Microsoft, so MS gets to see your queries and your IP, among other DDG problems

• #Qwant: tor-hostile (CAPTCHAs), MS profits from your searches.

I can see your point in many situations but when I say I am the one b*tching (myself… in the 1st person), in this context I am not saying I am acting badly myself. So the “women are bad” narrative doesn’t follow. In this case the word merely serves as a more expressive complaint.

If someone were to talk about someone else b*tching, it might well be what you’re saying, as they are complaining about someone else complaining & maybe they oppose that other person complaining or their aggressive style thereof.

Do you know what I should look for? Is it the version number? I recall Lemmy was forked to Lenny, but not sure how to recognize Lenny instances.

(btw, fwiw, I wouldn’t use sh.itjust.works because that’s even more nannied [by Cloudflare]).