Conversation

Notices

1. anonymous (anonymous@freespeechextremist.com)'s status on Thursday, 02-Nov-2023 14:39:27 JST anonymous

   • pistolero :thispersondoesnotexist:

   @p Since you’ve dug into the code for a while now and the pleroma devs are either busy or don’t care I suppose I should ask you.

   Adding relays failed at the AP fetch: [debug] Fetching object https://relay.c.im/actor via AP
   [error] Could not decode user at fetch https://relay.c.im/actor, :checkout_failure

   Where would I go about digging into the ActivityPub code? I am thinking perhaps there is an issue hardcoded in there that’s the issue, since even hosting my own relay didn’t seem to work, with the relay showing no errors or issues that I could see from console.

   • anonymous (anonymous@freespeechextremist.com)'s status on Thursday, 02-Nov-2023 14:39:23 JST anonymous

     in reply to

     • pistolero :thispersondoesnotexist:
     @p Actually, it turns out I am getting federation. Instances that allow onion communication I can talk to. Nothing in the WKN but otherwise it appears federation is operational.
     
     I added a bunch of relays but can't find FSE anywhere. I can't messgae anyone and it shows no errors. Do you not allow onion instances to talk to FSE or is this an issue on my end?
   • anonymous (anonymous@freespeechextremist.com)'s status on Thursday, 02-Nov-2023 14:39:24 JST anonymous

     in reply to

     • pistolero :thispersondoesnotexist:

     @p So it turns out the issue was because akkoma doesn’t accept socks5 proxys. Using a socks5->http proxy did the trick so now I am able to add relays. But still no federation. No idea why, no idea where to even start.

     Machismo repeated this.
   • pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 02-Nov-2023 14:39:25 JST pistolero :thispersondoesnotexist:

     in reply to
     @anonymous The way you usually do it is just have the instance follow the relay.
   • anonymous (anonymous@freespeechextremist.com)'s status on Thursday, 02-Nov-2023 14:39:25 JST anonymous

     in reply to

     • pistolero :thispersondoesnotexist:

     @p I know but I thought maybe I’d get a different error or something other than checkout failure. Nevertheless, I got checkout failure.

   • anonymous (anonymous@freespeechextremist.com)'s status on Thursday, 02-Nov-2023 14:39:26 JST anonymous

     in reply to

     • pistolero :thispersondoesnotexist:

     @p I have tried many different relays, many of which I can’t remember off the top of my head, and even trying to add relays directly. The error is always the same: checkout failure.

   • anonymous (anonymous@freespeechextremist.com)'s status on Thursday, 02-Nov-2023 14:39:26 JST anonymous

     in reply to

     • pistolero :thispersondoesnotexist:

     @p err add instances directly

   • pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 02-Nov-2023 14:39:27 JST pistolero :thispersondoesnotexist:

     in reply to
     @anonymous That's a flaky relay; do the other ones work?
   •  (mint@ryona.agency)'s status on Friday, 03-Nov-2023 04:10:53 JST 

     in reply to

     • pistolero :thispersondoesnotexist:
     @p @anonymous LRDD error is normal, I see it every time I try to fetch a new user.
   • anonymous (anonymous@freespeechextremist.com)'s status on Friday, 03-Nov-2023 04:10:54 JST anonymous

     in reply to

     • pistolero :thispersondoesnotexist:

     @p I am getting no errors as it stands. I am able to talk to others but nothing in the WKN. Akkoma apparently comes with pleroma, at least that’s what I was told. Take that for what you will.

     I am getting an arithmetic error when I try to search though:

     [error] #PID<0.6433.0> running Pleroma.Web.Endpoint (connection #PID<0.6160.0>, stream id 101) terminated Server: 127.0.0.1:4000 (http) Request: GET /api/v2/search?q=a&resolve=true&with_relationships=true ** (exit) an exception was raised: ** (ArithmeticError) bad argument in arithmetic expression (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter/limiter_supervisor.ex:49: Pleroma.Web.Plugs.RateLimiter.LimiterSupervisor.check_interval/1 (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter/limiter_supervisor.ex:28: Pleroma.Web.Plugs.RateLimiter.LimiterSupervisor.add_or_return_limiter/2 (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter.ex:253: Pleroma.Web.Plugs.RateLimiter.initialize_buckets!/1 (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter.ex:170: Pleroma.Web.Plugs.RateLimiter.check_rate/1 (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter.ex:104: Pleroma.Web.Plugs.RateLimiter.handle/2 (pleroma 2.6.0) lib/pleroma/web/mastodon_api/controllers/search_controller.ex:5: Pleroma.Web.MastodonAPI.SearchController.phoenix_controller_pipeline/2 (phoenix 1.6.16) lib/phoenix/router.ex:354: Phoenix.Router.__call__/2 (pleroma 2.6.0) lib/pleroma/web/endpoint.ex:5: Pleroma.Web.Endpoint.plug_builder_call/2

     I also get a strange Can't find LRDD template warning when I attempt to talk to certain instances. I am not sure currently what’s up with that but I believe it’s a configuration issue on my end.

   • pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 03-Nov-2023 04:10:54 JST pistolero :thispersondoesnotexist:

     in reply to
     @anonymous
     
     > Akkoma apparently comes with pleroma, at least that’s what I was told.
     
     Akkoma is a small fork of Pleroma; it's less that it comes with Pleroma as it just is Pleroma with a different name slapped on it and some changes. Some of the changes are just merging in-progress branches, so in general it's a little less stable. Case in point:
     
     > I am getting an arithmetic error when I try to search though:
     
     I've not seen that and I do not know how much I can say about Akkoma. It might be fixed by running a different (newer, probably, but maybe older, who knows?) version of Postgres, or maybe there's a bug in their code that turns the search queries into SQL.
     
     > I also get a strange Can't find LRDD template warning when I attempt to talk to certain instances.
     
     I am not sure what that is, but error messages in this codebase are useful for finding out why some problem is happening; if there isn't a problem to diagnose, then the error isn't a problem.
   • pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 03-Nov-2023 04:10:55 JST pistolero :thispersondoesnotexist:

     in reply to
     @anonymous Oh, hm, Akkoma. Not recommended, but your call.
     
     When you say "no federation", you're getting the checkout error? Some of the things I have said would make less sense if we're talking about Akkoma rather than ActivityRelay. The checkout error makes more sense. Is it able to talk to the DB properly?
   •  (mint@ryona.agency)'s status on Friday, 03-Nov-2023 04:14:48 JST 

     in reply to

     • pistolero :thispersondoesnotexist:
     @anonymous @p They are, or otherwise I won't be hosting Pleroma.
   • anonymous (anonymous@freespeechextremist.com)'s status on Friday, 03-Nov-2023 04:14:49 JST anonymous

     in reply to

     • 
     • pistolero :thispersondoesnotexist:
     @mint @p It's normal? Okay. I thought maybe it was preventing me from fetching a user because I tried to message someone and got that error, and the message was never sent.
     
     Are your fetches often successful?
      likes this.
   • anonymous (anonymous@freespeechextremist.com)'s status on Friday, 03-Nov-2023 04:21:13 JST anonymous

     in reply to

     • 
     • pistolero :thispersondoesnotexist:
     @mint @p I'll have to try a wider variety of websites to test more thoroughly.
      likes this.
   • pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 03-Nov-2023 04:29:47 JST pistolero :thispersondoesnotexist:

     in reply to

     • 
     @mint @anonymous I wonder if it's new; I haven't seen it.
      likes this.
   • pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 29-Dec-2023 06:23:59 JST pistolero :thispersondoesnotexist:

     in reply to
     @anonymous It's probably about 50/50. FSE doesn't talk to Tor, so we can't fetch keys, so incoming activities get rejected (this includes, e.g., follows). I might steal mint's code and get that working, but it's not currently on the list. We don't have signed fetches on, so federation with Akkoma (which enables them by default) is going to be somewhat limited anyway.
     
     On the other hand, we don't block any *incoming* traffic from Tor. (I use Tor to view FSE most of the time.) So you should be able to fetch activities from FSE.
      likes this.