sorted by: new top controversial old

Those fucks would unplug the entire damn internet in their crusade if they had the ability to

Postman has a quite active community, you can find a lot of stuff there already. It's not quite on the level of clearnet torrenting yet, of course, but it can very much stand on its own

It functions without port forwarding, but it's much better with. While I can't speak for the Java client, i2pd has support for UPnP, which might make things easier in some environments. You also don't need a VPN for I2P, since the network takes care of the anonymising

[-] Flynn_Mandrake@lemmy.dbzer0.com 158 points 1 month ago

Following Empress' bullshit via Telegram screenshots is a fun experience. I like to think of it as the B-plot of digital piracy.

[-] Flynn_Mandrake@lemmy.dbzer0.com 8 points 2 months ago

Yup. I've resorted to checking for new videos on Invidious and then actually watching them in MPV

[-] Flynn_Mandrake@lemmy.dbzer0.com 26 points 2 months ago

Well, that's shit news

[-] Flynn_Mandrake@lemmy.dbzer0.com 13 points 3 months ago

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

[-] Flynn_Mandrake@lemmy.dbzer0.com 7 points 4 months ago* (last edited 4 months ago)

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.

[-] Flynn_Mandrake@lemmy.dbzer0.com 9 points 5 months ago

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.

[-] Flynn_Mandrake@lemmy.dbzer0.com 13 points 5 months ago

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!

[-] Flynn_Mandrake@lemmy.dbzer0.com 2 points 5 months ago

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

19
submitted 5 months ago* (last edited 4 months ago) by Flynn_Mandrake@lemmy.dbzer0.com to c/selfhost@lemmy.ml

I've been wanting to set up a small game server on my home network for myself and a few friends lately. Nothing I haven't done before - except the part where I open it up to the internet for people outside of my home network to play on.

So I tried setting up a small web server to test out the port forwarding functionality of my router. Darkhttpd, running on a spare Raspberry Pi, works fine on the local network. After digging through the web interface, I find out that using IPv4 isn't an option because of how my ISP tunnels network traffic (sth sth Dual-Stack Lite)—fine by me, in 2024 we should be using IPv6 anyway. So I go and open up port 80 in my router's web interface.

This is where the problem begins. Everything looks fine, but I don't have ready access to a network outside of my own to check if the port is actually accessible from the internet. An online IPv6 open port checker I found tells me the ports are visible and that my ISP isn't blocking anything. Trying to bind a domain that I had lying around to my IP address, however, has resulted in failure.

I have no idea how to debug this. I'm pretty sure there's some issue on the DNS Server end, but I can't even tell if the rest of what I'm trying to do is working. And if it is, I have no idea of how to go about fixing the DNS thing.

Update: I got a friend to test it, and the web page is accessible from the internet. Problem lies with the DNS server

Update 2: After contacting my friend again for a sanity check, it seems that the DNS server works fine and my test website can indeed be reached through my domain—it's just that I can't reach it.

Update 3: After poking at various DNS servers, it appears that the Mullvad DNS servers which I use don't regularly update their records. I've now switched to Cloudflare. My router similarly implements some caching solution that, after much tinkering, I was unable to flush. For the time being I've just decided to fuck doing this properly and directly edit my /etc/resolv.conf with the Cloudflare DNS servers. If I ever manage to get this working properly, I will add a final update, but for the time being, I will consider it solved.

view more: next ›

Flynn_Mandrake

joined 1 year ago