Well, that’s shit news

Looks like you weren’t the only person to believe the 1994 version to be the better one

A good start would be to check the website and go from there. I don’t know of a good, singular guide unfortunately—there are a couple different ways of going about torrenting on I2P.

I can confirm that torrenting on I2P works quite well! You may have to set aside a couple weeks per movie, though. Still, the torrent selection is decent, if not quite as good as what you would get on the clearnet. You’ll want to check the postman tracker (tracker2.postman.i2p) once you have everything set up.

Stormy is an understatement. Last I checked, I was sitting at 4% - though it bears noting that I’m running my I2P router on a Pi, so I2PD is a bit out of date for me

Copious amount of ebooks or web novel downloads, as well as my lofi folder for background music. All preloaded on a boot drive with a Linux distro capable of both running on the hardware and viewing everything I brought, if I can figure out how to do that. Plus however many snacks I can sneak in.

Really cool, particularly the inbuilt sponsorblock and dislikes. Those are something I’ve been missing in my own Invidious. I’ll still stick with the original interface, but keep up the good work!

Going through Anna’s Archive also works, they usually have zlib links

Correct on all counts. I’ll try some other DNS servers later. Right now I’m using the Mullvad DNS servers, any suggestions for ones that support DNS over TLS?

Some further tests make it look like dig is influenced by some caching stuff going on on my PC. I figured that out while playing around with a TXT record for testing purposes, and noticing that host and dig return different results for the same input.

Running the commands again on my phone using Termux reveals that the AAAA record is in place and functioning, but I still can’t reach the website from my browser by using the domain name.

~ $ dig [domain]

; <<>> DiG 9.16.41 <<>> [domain]
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39355
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;[domain].              IN      A

;; AUTHORITY SECTION:
[domain].       1800    IN      SOA     dns1.registrar-servers.com. hostmaster.registrar-servers.com. 1711402015 43200 3600 604800 3601

;; Query time: 30 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Mar 25 22:35:59 CET 2024
;; MSG SIZE  rcvd: 118

~ $ dig [domain] AAAA

; <<>> DiG 9.16.41 <<>> [domain] AAAA
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45166
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;[domain].              IN      AAAA

;; ANSWER SECTION:
[domain].       1799    IN      AAAA    [correct IP!]

;; Query time: 36 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Mar 25 22:36:11 CET 2024
;; MSG SIZE  rcvd: 73

~ $ host -t AAAA [domain]
[domain] has IPv6 address [correct IP!]
~ $

Thanks for the answer! Unfortunately, the response from dig AAAA is rather lackluster:

; <<>> DiG 9.18.24 <<>> AAAA [domain]
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14166
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;[domain].              IN      AAAA

;; Query time: 19 msec
;; SERVER: 192.168.178.1#53(192.168.178.1) (UDP)
;; WHEN: Mon Mar 25 19:22:18 CET 2024
;; MSG SIZE  rcvd: 34

I’m starting to suspect Namecheap just hates IPv6. Their dynamic DNS service only covers v4, too

Correct! Single AAAA record pointing to the IP of my server, which I verified beforehand.

My host records consist of a single AAAA record that points to the IP address of my server, which I verified beforehand. I’ve tried dig, but I’m not sure how to interpret it’s output, which looks as follows:

;; Warning: Client COOKIE mismatch

; <<>> DiG 9.18.24 <<>> [domain]
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35067
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 485ffdde4d749cd80100000066019ef6aba1fc1942596e31 (bad)
;; QUESTION SECTION:
;[domain].              IN      A

;; AUTHORITY SECTION:
[domain].       3113    IN      SOA     dns1.registrar-servers.com. hostmaster.registrar-servers.com. 1711343555 43200 3600 604800 3601

;; Query time: 0 msec
;; SERVER: 192.168.178.1#53(192.168.178.1) (UDP)
;; WHEN: Mon Mar 25 17:05:52 CET 2024
;; MSG SIZE  rcvd: 146

The DNS issue persists. The part that my friend helped me with was determining if I configured my router firewall correctly, which I did. Currently I can reach my server from the internet only directly via its IPv6 address, with no progress on binding it to my domain name.

The firewall port on my router is open, and as far as I can tell, my server isn’t running a firewall at the moment. ICMP might be a problem; ipv6-test tells me that those are filtered out. After checking my router settings, I’ve determined that ICMP is enabled for the device in question.

Tried my mobile connection already, doesn’t have IPv6. Also tried a nearby hotspot, same issue.

More I2P torrenting support

Just as the founding fathers intended.

YouTube is already a sedated, anaemic whale of a website. Adblock probably makes it run faster, given it usually removes stuff rather than add it. If you want speed, I recommend a frontend such as Invidious or Piped, it’s what I use on my weaker laptops where YouTube takes half a minute to load.

RIP Tachiyomi, time to try out Kotatsu

That’s neat, I should adopt that terminology!

What is this, a callout post?