The Endless Drum Beating

Status
Not open for further replies.
Good luck josh, if we go down, so be it.

I'll just shit post everywhere, teach the world the lesson tumblrs fall should have taught.
 
Hahaahaha no you don't. Your only bastion of free speech is gone forever and all you can do is cope and seethe. Have fun with your imaginary friends while the pendulum swings further left.
You believe the rise of a more corporate and controlled world is great for workers rights & organizations and freedom?
 
You have to take care of you first, Josh. This situation is so frustrating.

For any trannies reading this thread with glee, censorship does not change beliefs. I will never, ever believe that you are a woman - none of us will. We will always make fun of you where you can't hear us, no matter what. Even if there are no more spaces on the Internet where we can speak freely, you can't control everyone.
 
  • Like
Reactions: AccountForLurking
There is one other option that I loathe to bring up. It would be ideologically the same as a modern Molotov-Ribbentrop pact. Fortunately, they cannot kill knowledge, nor can they cannot kill an idea. So long as this site exists, they have have lost.

@Null
I do not know what way you will choose, but sometimes it is better to die a free man than live as a slave.
It should be possible to setup a server in China facing outwards only that would block the mainland + ROC (Taiwan), but you would need to have the acquiescence of the Cyberspace Administration of China (Think Roskomnadzor on steroids). However, our presence there would likely be tolerated only in so far as long as there is not a rapprochement in US-China relationships and contingent on us not talking about China and their ruling party.

Also, is it possible that perhaps we could get an I2P instance set up?


The only "solution" for that would not be legal, don't do it because the government will rape your ass harder than the Branch Davidians. Unfortunately, Kiwifarms is visible in the light, and most of the attackers are hidden in the dark aside from figurehead like Keffals. We do not know who or where they are, but they know where this site is.
 
We will always make fun of you where you can't hear us, no matter what. Even if there are no more spaces on the Internet where we can speak freely, you can't control everyone.
We make superb fake allies by the way. We know all the right stupid words to say and understand all the platitudes. They'll never know when the moment of opportunity comes to drop the facade and stab them in the back (figuratively! not a call to action!). Troons forever doomed to live in fear that they are just being humored.
 
I'm sorry you're dealing with so much shit at once, but glad you have your priorities straight.

Request we play Invincible by Pat Benatar as the Troon menace bears down and tries to shit out a clearly-illegal-yet-somehow-still-legal movement.
 
The joke is that the place is called "Sneed's Feed & Seed" which is clever in itself and quite funny to those with a mature sense of humour but what's really just hilarious about it is that if you look closely at the front of this store, Sneed's Feed & Seed, you can see a line that reads "Formerly Chuck's". Now, this might go over the average viewer's head as this, THIS, is peak comedy. I doubt anything will ever be as funny as the joke about Sneed's Feed & Seed. Are you ready for this one? So, like I said, the place is called "Sneed's Feed & Seed" and this sign says "Formerly Chuck's", which means that when Chuck owned the place, well, I don't have to tell you...
 
It was a good run bros. Not many places left like this.

Transwomen are men and nothing can ever change that, and 95% of people who humor the fetish do so because it's easier than telling the truth. Everyone knows who the groomers and fetishists are.
 
If the site ever goes down for good, I hope something similar will rise in its place. Take care of what you got to Josh, we will be here for you when you return.
 
  • Feels
Reactions: AccountForLurking
The GNU Name System

Is it feasible to add GNUnet to your stack? If so.. (

Name resolution using GNS on the command line​


The GNU Name Service (GNS) is a fully decentralized alternative to the Domain Name System (DNS). Where GNS does not suffer the same major security flaws as DNS.


In this example, Alice will save the IP address (195.54.164.39) of the Chaos Computer Club e.V. (CCC) homepage into a GNUnet namestore record and then try to resolve it using GNUnet GNS.

First Alice needs to create a GNUnet identity which is the equivalent to a zone in a DNS. We'll call it "myself" and create it using the `gnunet-identity` command line tool. Instead of "myself" you can use your nickname, or any other name.


alice@laptop $ gnunet-identity -C myself


Alice can check to see if it worked using the same tool. The name of her identity and the corresponding public key are displayed.


alice@laptop $ gnunet-identity -d
myself - HWTYD3P5D77JVFNVMZ1M5T10V4SZYNMY3PCGQCSVENKD6ZCRKPMG


Now Alice adds a public `A` record to the zone. We'll call it "ccc" with the value "195.54.164.39" and it expires after one day.


alice@laptop $ gnunet-namestore -z myself -a -e "1 d" -p -t A -n ccc -V 195.54.164.39


Now the GNS can be queried using the command line tool `gnunet-gns`.


alice@laptop $ gnunet-gns -t A -u ccc.myself
ccc.myself:
Got `A' record: 195.54.164.39



So it worked! But only resolving our own records is boring. So we can give our identity (the public key of it to be precise) to someone else so they can try to resolve our records, too. The other person (Bob) has to add it to his namestore like this:

We can all be Bob,
bob@desktop $ gnunet-namestore -z myself -a -e never -p -t PKEY -n alice -V HWTYD3P5D77JVFNVMZ1M5T10V4SZYNMY3PCGQCSVENKD6ZCRKPMG


Alices identity in Bobs namestore is a public record (-p) and never expires (-e never). Now Bob (let's assume he has called his identity myself, too) should be able to resolve Alice's "ccc" record, too!


$ gnunet-gns -t A -u ccc.alice.myself
ccc.alice.myself:
Got `A' record: 195.54.164.39


It can continue like this. A friend of Bob would be able to resolve Alice's records too because Bob published her identity in a public record. Bobs friend would simply use "ccc.alice.bob.myself" to resolve Alice's "ccc" record.


And for the browser...

Name resolution using GNS with a browser​


In the previous use-case "Name resolution using GNS on the command line" we saw how we could retrieve a value (e.g. an IP address) associated with a given named record (e.g. a web address). Now we'll see how GNS can be used with a browser, making it actually useful. Currently Firefox and Chromium are known to work with GNS.


Many websites enforce HTTPS by providing TLS certificates for their hostnames, with the aim of encrypting the web page content between the clients browser and the hostname server, and authenticating the server and client to each other. This is so that a 3rd party cannot see what is being communicated between the client (browser) and server (website host). This is important, for example, if you are using online banking where you don't want anyone seeing your customer ID and password.


Unfortunately, if a browser resolves a hostname through the GNS, the TLS certificates will have the original hostname and the browser will present an error message. In the previous example, we resolved "ccc.myself" to 195.54.164.39 but the hostname's TLS certificate refers to the actual hostname as "https://www.ccc.de/" So GNUnet has to trick the browser by generating it's own certificates for the hostnames GNS resolves. This means we need to create our own certificate authority and tell our browser to use this instead. Luckily there's a script to fix this problem:


$ gnunet-gns-proxy-setup-ca


After executing this script the Browser has to be restarted.


GNUnet provides a proxy service (gnunet-gns-proxy) that the browser can send DNS and HTTP traffic to. It will try to resolve names with GNS first and forward the rest of the DNS traffic to the system's DNS resolver. It will also take care of the HTTP traffic, so the browser gets valid certificates and the web server will not be confused by the hostnames resolved by GNS instead of the DNS. The GNS namestore does not know about any DNS hostnames yet, so we have to store them, too. For our "ccc" A record, we have to store a LEHO (LEgacy HOstname) record, too. It must contain the website's original DNS hostname:


$ gnunet-namestore -z myself -a -e "1 d" -p -t LEHO -n ccc -V www.ccc.de


Now lets start gnunet-gns-proxy.


$ /usr/lib/gnunet/libexec/gnunet-gns-proxy


Our browser has to be configured so it uses our proxy. In Firefox we have to set these options under "about:config":


network.proxy.socks: localhost
network.proxy.socks_port: 7777
network.proxy.socks_remote_dns true
network.proxy.type: 1


To tell Chromium to use the proxy, it has to be started with the "--proxy-server" command line option:


$ chromium --proxy-server="socks5://127.0.0.1:7777"


Now we should be able to resolve our GNS names in the browser! We just have to type "https://ccc.myself" into the address bar. If our friend Bob prepared his system, too, he can resolve our record by typing "ccc.alice.myself".


@Null
 
Status
Not open for further replies.
Back