Conversation
Notices
-
I am not getting tor instance posts here, I need to set up a tor listening node.
-
@0 There's two ways of handling this I've recommended in the past, either by setting up Privoxy to pass thruogh clearnet directly and Tor via its socks proxy, then setting up Pleroma to use upstream proxy. Or by adding accept-intercepted-requests to Privoxy, binding it to port 80 on random 127.0/8 address, then making the local DNS resolver resolve *.onion to that address.
-
@syzygy @meowski @0 nevermind i'm sorry i wont cheerlead anymore my bad
-
@pernia @meowski @0
Pernia in a skirt.
-
@pernia
That's why I said so, cheerleader.
-
@0 got a problem with male cheerleading, chud?
-
@0 u should luser
-
@pernia @meowski @0
Put the skirt on, bambi.
-
@snacks @0 Fake news.
Screenshot_20240311_214730.png
-
@0 I don't think you can get proper tor federation on a clearnet instance anymore sadly
-
@snacks @0 Privoxy that routes .onion to the Tor daemon's proxy and accesses clearnet directly, but using pure SOCKS proxy should work as well (as long as you don't mind not getting posts from cloudflared instances). I federated with I2P and Lokinet without much issues as well.
-
@mint @0 how?
-
@mint @0 used to have the socks setup, later switched to fediproxy, but it stopped federating with tor instances at some point
-
@snacks @0 Sometimes the Tor daemon takes its sweet time to start resolving onions, yeah. With rawr I got a couple bots on both sides to keep the posts coming in my absence, and subscribed to each other's relays too, seems to be relatively stable.
Screenshot_20240311_220959.png
-
@mint @0 @snacks why isn't there a DNS-like service for onion addresses
-
@0 Oh, and you could also patch Pleroma itself to route .onion through SOCKS proxy directly, like @i did.
https://declin.eu/objects/7d564cb6-cbb0-4801-b052-59975d0cc1fe
-
@not_benis @0 @snacks You can make do by setting up something like said Privoxy with accept-intercepted-requests and resolving all *.onion domains to address it's listening on. But faggots who wrote RFC 7686 don't want you to do that; thankfully Pleroma's HTTP adapters don't care about it, at least yet.