Kiwifarms Nitter/Bibliogram/Invidious Instances - Better privacy on site. Easier to archive.

The purpose is to protect their users' privacy. The alternative would be to send the IP of the PoP in the EDNS field, but that would violate the specification.
You know very well that that is another fucking lie from lying shyster Matthew Prince.

There is no 'protection of privacy', and if you can't understand that, you should shut your mouth.

If the Russian autist cucked to Shitflare, the 'privacy' that a user would gain is that he wouldn't know the general location of a person going to his site, who wants to go to his site, for however long a gap there is between the user's initial DNS request, and the initiation of the connection over HTTP or HTTPS to his site. If they're on satellite internet or 14.4k dialup, they might get as much of a second of blessed, blessed PRIVACY. After which point the Russian gets the full IP, not just the subnet.

This is just worthless cunt Matthew Prince systematically attacking anyone who doesn't kow tow to his monopoly.
 
You know very well that that is another fucking lie from lying shyster Matthew Prince.

There is no 'protection of privacy', and if you can't understand that, you should shut your mouth.

If the Russian autist cucked to Shitflare, the 'privacy' that a user would gain is that he wouldn't know the general location of a person going to his site, who wants to go to his site, for however long a gap there is between the user's initial DNS request, and the initiation of the connection over HTTP or HTTPS to his site. If they're on satellite internet or 14.4k dialup, they might get as much of a second of blessed, blessed PRIVACY. After which point the Russian gets the full IP, not just the subnet.

This is just worthless cunt Matthew Prince systematically attacking anyone who doesn't kow tow to his monopoly.
I could be using a VPN with a misconfigured DNS that causes DNS leaks. I could be resolving it without visiting. And so on.
How come archive.is is the only site in the entire world which has this problem?
If he's so concerned, why doesn't he set up subdomains like cz.archive.is, us.archive.is, hk.archive.is, etc?
 
I could be using a VPN with a misconfigured DNS that causes DNS leaks. I could be resolving it without visiting. And so on.
How come archive.md is the only site in the entire world which has this problem?
If he's so concerned, why doesn't he set up subdomains like cz.archive.md, us.archive.md, hk.archive.md, etc?
Oh, so what you're saying is that Matthew Prince is such a prince among men that he did this for the 'privacy' of:
  1. The small minority of the small minority of people who are VPN users- who are also so retarded that they have DNS requests going through their bare connection. So, a few thousand retards, people like you
  2. People who are using nslookup to check the current IP of archive.is without going there. So, people DDOSing the site?
You are too stupid to live, and I congratulate the Russian for standing up to Cloudflare. More people should engage in actions that hurt cocksucking faggot monopolist Matthew Prince.
 
Oh, so what you're saying is that Matthew Prince is such a prince among men that he did this for the 'privacy' of:
  1. The small minority of the small minority of people who are VPN users- who are also so retarded that they have DNS requests going through their bare connection. So, a few thousand retards, people like you
  2. People who are using nslookup to check the current IP of archive.is without going there. So, people DDOSing the site?
You are too stupid to live, and I congratulate the Russian for standing up to Cloudflare. More people should engage in actions that hurt cocksucking faggot monopolist Matthew Prince.
I can definitely get behind outright blocking 1.1.1.1 with some bullshit pretext, but there's plenty of legitimate reasons for CloudFlare to do what they're doing now with the DNS too.
 
I can definitely get behind outright blocking 1.1.1.1 with some bullshit pretext, but there's plenty of legitimate reasons for CloudFlare to do what they're doing now with the DNS too.
No. There are not.

Your 'privacy' faggotry is Cloudflare corporate propaganda.
 
Whatever happened to the invidious instance?

A good solution for DoS problems is to limit the archival to users of the Farms. That way you could even archive YouTube and stuff, as long as it's tied to someone's account and used in a legitimate thread.
 
Yeah the nitter one never loads right for me. It's always a completely broken page that isn't readable. Should just get rid of it, it's trash.


Yep, that's how the word filter works.
Filtering on /(?i)url=((http|https)://)?(www\.)?twitter\.com/ should do the trick.

I do think nitter is very valuable because Twitter doesn't work in Tor, though.
 
I see Nitter is built using Nim lang. Seems like a very useful programming language been meaning to learn it. I do see it is also using Jester which is very Sinatra like which I am familiar with on Ruby.
sorry for programming talk 100% support FOSS alternatives to these social media monopoly fucks
 
This is how nitter loads a Tweet for me when linked from KF.
screencapture-tw-tinf-io-lrvick-status-1320246266270519297-2020-10-29-18_24_10.png

Edit - Suddenly, they are all loading correct now.
 
Last edited:
  • Agree
Reactions: hundredpercent
I think the CSS doesn't load properly, under certain circumstances.

What's with the downtime?
 
It doesn't look like the wordfilter is handling instagram user profile links very well. Looking at the bottom of my Beauty Parlor OP here, I have two instagram profile links:

ig.tinf.io is successfully swapped in but it needs "u/" to be inserted in front of the username to work:

You can easily differentiate the two because instagram has two url formats, one for user profiles (see above) and one for direct links to posts that uses "p/":
The filter is excessive. It even gets links like https://web.archive.org/DATE/tw.tinf.io/asd
Not sure if you saw these two posts @Null.
 
If these instances aren't going to work any better than they are now, can we turn off the URL rewriting? Or maybe just show both the original and the rewritten ones if there's still some hope for this? Right now this is effectively making every Twitter and IG URL that has ever been posted to the site effectively unusable.
 
ya I don't have the finite tools required for the kind of URL rewriting needed and unfortunate the most used one (Twitter) is written by a tranny and breaks constantly.
Would it potentially be possible to look at catching connections to https://mobile.tw.tinf.io and redirecting them to https://tw.tinf.io on the Cloudflare side (I notice that http://tw.tinf.io is also not hooked up in Cloudflare for what it's worth)?

That should catch most of these issues. Or maybe phoneposters could be banned?
 
  • Feels
Reactions: Magnum Tenebrosum
Back