26
posted ago by ghost_of_aswartz ago by ghost_of_aswartz +26 / -0

They call this telemetry but really, it's thought-enforcement

They have an initial algorithm that is scanning in realtime your words, and if your words cross a line (by way of technologies such as NSA::XKEYSCORE), then your activity gets escalated to a a more aggressive filter, possibly even a human being, watching what you're writing in realtime.

One would NOT believe that so much money and military and contractors ("signature reduction" corps) would be deployed for watching what we the people are saying on forums; and if you told normal people 5 yrs ago they'd call you a self-deluded, paranoiac fantasist.

Except we have the receipts. We know that 40% of gross internet traffic is bots. We know that Twitter must be at least 1/3 bot software. Chat bots or worse. Politicized talking point bots with some semblance of machine learning (or machine learning 'fairness').

We also know that everything we say in forums is monitored. But they are always on the DEFENSE if you are allowed to write your words and post them.

No, they want to go on the OFFENSE and make sure your words are never seen, and to do that they have to monitor your words in REALTIME and then censor you.

How do they do this? With some javascript that transmits every keypress to a server, and then THAT server will retransmit elsewhere. Or javascript that rewrites URLs to some DDOS protection, loadbalancing, CDN software that will intercept the upstream data from our client browsers in some way. There's multiple ways to do it.

But the website has to be complicit. Their web developers have to put this software on there for that to happen. Unless say cloudflare has gotten really creative and intercepted all the traffic. But still, they'd have to QUANTUMINSERT (a real word, technique by the NSA/CIA) that would have to add in their own javascript by changing the javascript that is intended to be downloaded. Of course, this is not different from an XSS attack, and I'm sure it violates their terms of service, unless their TOS includes a way for CLoudflare to be able to add arbitrary code to files "for telemetry and quality control" then they could use plausible deniability of that insertion.

If I were a web dev and I found out that my patriots.win website were being CUCKED BY CLOUDFLARE in this way, I'd be SO pissed off that I'd stop using them and I'd roll my own DDOS protection using elastic compute eucalyptus grid or squid or one of many other distributed reverse proxy softwares that are open source and ready to go and above all: free.

I'd like to know if someone were intercepting my CLIENTS' data and sending it to the FBI.

I'd really want to know this.

Because


With this information, they can shadowban you

How can Cloudflare shadowban us on this website without the ADMINS or Mods knowing it??

Is that possible?

YES

Here is how

When you request the front page, "HOT" for example, there's a listing of articles

  • Cloudflare delivers this HTML, they rewrite the HTML in realtime to simply remove your article.

They can suppress your article score too.

HOW??

Whenever someone clicks upvote, the javascript shows that they upvoted your article, but they can drop the upvote by not transmitting to patriots.win the callback url that upvotes the article. But they still mark the item as upvoted, so it appears you voted, but you didn't actually upvote, because cloudflare dropped your upvote.

How does it keep track of this? A database. They'd have to have a database to keep track of your attempt to upvote, so that they can remember to mark the items you upvoted as having upvoted; but they actually didn't retransmit the upvote to patriots.win, so patriots.win's database doesn't increment the score.

Thus, your score stays at a low number.

So that they don't get caught, they allow the first RAND(20-50) upvotes then they shadowban by dropping any more than their random max for that post

Patriots.win (winsites) does vote fuzzing just like reddit does. OR that's an unintended side effect of a round robin of different servers (load balancers) having different cached post score values.

Ever notice how some posts get fixed at THIRTY THREE for HOURS?

It's weird, until you know how it works.