<2021-09-08T10:18:11.000Z> silverpill: Hello! I'm developing an activitypub server with ethereum integration. I heard that you wanted to do something similar with Soapbox, so perhaps you'll find it interesting.Currently the development is at proof-of-concept stage. You can tokenize a post, that means putting its metadata on IPFS and minting an NFT. Federation basics are also working.The source code is not published yet, but I'm planning to release everything under AGPL soon.I would be grateful for any feedback.test.mitra.pmInvite code: c0ba8bc56bda4bf183a7a2d6f6f5cd7f
<2021-09-09T01:58:11.000Z> alex@gleasonator.com: Very cool
<2021-09-09T02:00:56.000Z> alex@gleasonator.com: What language is it in?
<2021-09-09T08:58:08.000Z> silverpill: Backend is in Rust, frontend is Typescript+Vue
<2021-12-23T01:00:33.000Z> silverpill: Hi Alex, could you help me with debugging a federation issue?Some activities from my instance are rejected by Pleroma (?) instances. Specifically, I get 500 error from your instance in response to Like and Undo(Like) activities. But I can't reproduce this on my own Pleroma instance. poa.st also accepts it.
<2021-12-23T01:03:43.000Z> silverpill: I see this happening to spinster.xyz, leafposter.club and gleasonator.com
<2021-12-23T01:05:37.000Z> silverpill: This activity triggered error on gleasonator.com:{"@context":"https://www.w3.org/ns/activitystreams","id":"https://mitra.social/objects/017de4bd-b352-f6fc-a638-39aa44888a2f","type":"Like","actor":"https://mitra.social/users/silverpill","object":"https://gleasonator.com/objects/ac603fee-ff4e-45c2-b024-09ce79e1bc15","to":["https://www.w3.org/ns/activitystreams#Public"]}
<2021-12-23T02:07:25.000Z> alex@gleasonator.com: I would have to check my logs, but I'm AFK. Do you have a timestamp?
<2021-12-23T15:09:51.000Z> silverpill: 2021-12-22T19:42:58 EST
<2021-12-23T15:21:47.000Z> silverpill: 00:42:58 UTC
<2021-12-23T19:01:56.000Z> alex@gleasonator.com: My logs get pruned too fast to see anything from yesterday, trying to see if I have any other erros
<2021-12-23T19:04:58.000Z> alex@gleasonator.com: The only errors I see are DB Connection errors, eg Postgres timing out.
<2021-12-23T19:19:30.000Z> silverpill: I'll try again now
<2021-12-23T19:20:38.000Z> silverpill: Just sent Like to your server, it returns http500 
<2021-12-23T19:23:22.000Z> silverpill: With "error" in response body
<2021-12-23T19:25:36.000Z> silverpill: I'm sending to a personal inbox gleasonator.com/users/alex/inbox
<2021-12-23T19:28:12.000Z> alex@gleasonator.com: This is the only thing I see that looks out of the ordinary:
<2021-12-23T19:28:14.000Z> alex@gleasonator.com: Dec 23 19:19:43 gleasonator mix[638338]: 19:19:43.856 [info] POST /inboxDec 23 19:19:43 gleasonator mix[638338]: 19:19:43.880 request_id=FsN4gMvJVahHfDsAzOyC [info] Sent 200 in 23msDec 23 19:19:43 gleasonator mix[638338]: 19:19:43.914 [info] TLS :client: In state :hello received SERVER ALERT: Fatal - Protocol Version
<2021-12-23T19:30:07.000Z> alex@gleasonator.com: Usually a 500 means some kind of crash which it would log, but that's not happening for some reason
<2021-12-23T19:32:05.000Z> silverpill: My request was sent at 19:53But maybe the clock if a bit off
<2021-12-23T19:32:42.000Z> silverpill: btw do you have nginx or some other web server acting as a reverse proxy for pleroma?
<2021-12-23T19:33:38.000Z> silverpill: I would check its log as well
<2021-12-23T19:39:12.000Z> silverpill: I sent a Note in reply to this post gleasonator.com/objects/ac603fee-ff4e-45c2-b024-09ce79e1bc15It went through
<2021-12-23T19:39:40.000Z> silverpill: If the problem was with my http client, it should not have worked right? :
<2021-12-23T20:47:19.000Z> silverpill: Not sure if this is applies here but there are cases when Pleroma doesn't show errors because they are logged at debug level.For example, if value of "to" field of the incoming Note doesn't match the "to" of Create activity the pleroma drops it. The error message is only visible when you set log level to "debug":git.pleroma.social/pleroma/pleroma/-/blob/develop/lib/pleroma/web/federator.ex#L106
<2021-12-24T22:40:14.000Z> silverpill: There was a clock synchronization issue on my side and it has been fixed. However, activities are still being rejected.
<2021-12-24T22:42:18.000Z> silverpill: I checked software version on problematic instances via nodeinfo and they all running different pleroma versions: from 2.2.2 to 2.4.1-dev
<2021-12-25T00:17:34.000Z> silverpill: So pleroma rejects Like and Announce activities if recipient doesn't follow the sender and recipient is not present in "to" field.The error doesn't appear in the log even in debug mode. Only response with status 500 is logged:23:32:17.714 request_id=FsPU3aMK08mwLKoAAnmR [debug] Sent 500 in 33ms
<2021-12-25T00:17:42.000Z> silverpill: I suppose it's happening here git.pleroma.social/pleroma/pleroma/-/blob/develop/lib/pleroma/web/activity_pub/object_validators/common_fixes.ex#L40 but I'm not sure where exactly.