Conversation

Notices

1. Embed this notice
   alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 19:41:07 JST alenshore

   • 
   • ✙ dcc :pedomustdie: :phear_slackware:
   • alenshore
   @dcc @mint If you notice anything let me know. I know there are forwarding errors but I have no idea why. My privoxy config is very basic and I only changed what I needed to get relays to be accepted. I am very new to this so I would guess it's something basic I am missing.
   
   I have already contacted the privoxy devs to see if they can find something. No responses so far.
   •  likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 19:41:51 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc Forwarding errors definely come from privoxy, show me its full config.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 19:43:16 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:

     @dcc @mint Actually turns out they did get back to me.

     privoxy config:

     user-manual /usr/share/doc/privoxy/user-manual confdir /etc/privoxy logdir /var/log/privoxy actionsfile match-all.action # Actions that are applied to all sites and maybe overruled later on. actionsfile default.action # Main actions file actionsfile user.action # User customizations filterfile default.filter filterfile user.filter # User customizations logfile logfile listen-address 127.0.0.1:8118 listen-address [::1]:8118 toggle 1 enable-remote-toggle 0 enable-remote-http-toggle 0 enable-edit-actions 0 enforce-blocks 0 buffer-limit 4096 enable-proxy-authentication-forwarding 0 forward 192.168.*.*/ . forward 10.*.*.*/ . forward 127.*.*.*/ . forward-socks5 / 127.0.0.1:9040 . forwarded-connect-retries 0 accept-intercepted-requests 0 allow-cgi-request-crunching 0 split-large-forms 0 keep-alive-timeout 5 tolerate-pipelining 1 socket-timeout 300

     Using port 9040 is the only way to add relays, otherwise I get forwarding errors when attempting to add relays.

      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 19:45:25 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc Port shouldn't affect anything. Check if changing forward-socks5 to forward-socks5t does anything.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 19:46:13 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc Gimme a minute gotta boot everything tf back up :REEEE:
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 19:46:32 JST 

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc If it doesn't, see if there's any difference with minimal config.
     user-manual /usr/share/doc/privoxy/user-manual
     confdir /etc/privoxy
     listen-address 127.0.0.1:8118
     toggle 1
     enable-remote-toggle 0
     enable-edit-actions 0
     enable-remote-http-toggle 0
     max-client-connections 65535
     buffer-limit 4096
     
     logfile /dev/null
     
     forward-socks5t / 127.0.0.1:9050 .
     
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 19:53:54 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc Will do in a moment. Want to make sure I didn't break anything so I am checking to see if old config works. At any rate, on port 9040 I get forwarding error on 9050 I get
     ```
     [error] Follower/Following counter update for https://relay.minecloud.ro/actor failed.
     {:error, "Object has been deleted"}
     ```
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 19:55:09 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc Clearnet relays won't work either way since none of them have Tor connectivity. They are just special instances with a single actor that reposts posts from subscribed instances.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:00:06 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc How do I subscribe to an instance? Also are there Tor relays?
     
     I am also able to add relays (clearnet) with my old config but I get
     ```
     Follower/Following counter update for https://relay.c.im/actor failed.
     {:error, "Object has been deleted"}
     ```
     
     Nothing was deleted though. Odd. I'll try the minimal config.
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 20:00:46 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc >How do I subscribe to an instance? Also are there Tor relays?
     There's none, but many Pleroma instances have their own internal relay at https://instance.tld/relay, so you could subscribe to those that federate with Tor or are entirely in it.
     Screen Shot 2023-11-20 at 14.00…
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 20:01:26 JST 

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc Botched screenshot.
     Screen Shot 2023-11-20 at 14.00…
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Monday, 20-Nov-2023 20:03:40 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to

     • 
     @mint @anonymous6479 I have my relay on
      likes this.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:07:00 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc Okay so nothing in WKN nor can I search anything still (no surprise). When attempting to DM myself I get
     ```
     03:05:37.668 [error] Process #PID<0.2160.0> raised an exception
     ** (KeyError) key :ap_id not found in: nil. If you are using the dot syntax, such as map.field, make sure the left-hand side of the dot is a map
     (pleroma 2.6.0) lib/pleroma/web/mastodon_api/views/conversation_view.ex:27: Pleroma.Web.MastodonAPI.ConversationView.render/2
     (pleroma 2.6.0) lib/pleroma/web/views/streamer_view.ex:140: Pleroma.Web.StreamerView.render/3
     (pleroma 2.6.0) lib/pleroma/web/streamer.ex:315: Pleroma.Web.Streamer.push_to_socket/2
     ```
     
     And it doesn't go through.
      likes this.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:07:02 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:

     @mint @dcc Man I wish that had been more well documented. Could have saved me a boatload of trouble searching for relays.

     At any rate I added ryona.agency. Got this error but it stayed on my relay list:

     request_id=F5lP2TT4qb2MNd0AAB_E [error] Could not decode featured collection at fetch https://ryona.agency/relay/collections/featured, {:error, {:content_type, "text/html; charset=utf-8"}}

     I'll see if anything changed.

      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 20:10:21 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc Is your instance even up? To go through, it needs to be accessible, and I'm getting Host unreachable when connecting to it, both from home and server.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:10:58 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc Odd. It IS up. Let me try to connect with the .onion.
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 20:17:11 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc >Invalid header received from client.
     That's better, but I think you forwarded the wrong port. Check if you're forwarding nginx/pleroma and not something else.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:18:40 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc I had to change the port for the other program and forgot the original. I am going to back to the Tor config pleroma walkthrough I used before. Should have made a copy instead of a direct edit.....
      likes this.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:22:49 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc nvm internet must have pooped it
     it appears to be accessable now.
      and ✙ dcc :pedomustdie: :phear_slackware: like this.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:22:50 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc I am using the port from the walkthrough and it's not working. The privoxy listen port also didn't work. For the life of me I cannot remember what port to use! Arg!
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 20:27:41 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc Yeah, I can curl it, but fetching posts returns {:error, :timeout}.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:27:42 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @dcc @mint Can you reach it?
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:29:09 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @dcc @mint Oh and also please forgive the niggerlicious nature of the site. A lot of it will be changed and/or updated once the site is actually operational.
      likes this.
   • Embed this notice
     alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:30:30 JST alenshore

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc The public timeline should be visible. Is on the browser anyway. You're probably getting a timeout because my internet is dogshit, but that's just a guess. Is there anything I can do to diagnose the error?
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 20-Nov-2023 20:32:54 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @anonymous6479 @dcc Yeah, check if privoxy works (`env all_proxy=http://127.0.0.1:8118 curl http://rawrxd4mden7rmbobaftao3qjyxbrvj4rrooehkqxlqcsdtnnn2hndid.onion`). Something suggests it might be trying and failing to fetch my instance's actor to check the request signature, as after disabling signed fetch for your instance here I've successfully fetched your post.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.