I just upvoted a comment in a community hosted on my site, and in the nginx log I can see:
ip.address - - [19/Feb/2024:14:33:31 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://endlesstalk.org"
ip.address - - [19/Feb/2024:14:33:43 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://endlesstalk.org"
Dumping out the activity, I can see:
... (single vote from account on another instance) ...
{
"@context": [
"https://join-lemmy.org/context.json",
"https://www.w3.org/ns/activitystreams"
],
"id": "https://endlesstalk.org/activities/like/f102d062-dfe9-4ece-96e8-310a09b249ba",
"actor": "https://endlesstalk.org/u/freamon",
"object": "https://sh.itjust.works/comment/9061222",
"type": "Like",
"audience": "https://lemmon.website/c/tails"
}
... (single vote from account on another instance) ...
{
"@context": [
"https://join-lemmy.org/context.json",
"https://www.w3.org/ns/activitystreams"
],
"id": "https://endlesstalk.org/activities/like/f102d062-dfe9-4ece-96e8-310a09b249ba",
"actor": "https://endlesstalk.org/u/freamon",
"object": "https://sh.itjust.works/comment/9061222",
"type": "Like",
"audience": "https://lemmon.website/c/tails"
}
... (single vote from account on another instance) ...
It's the same for comments too (if I grep the dump for other people's comments, there's only one, but there's two for comments made by me)
EDIT: can also see dupes from lemmy.ca (they actually sent the same Like 3 times).
Hi Admin,
Turns out this was being worked on by lemmy.ca at the same time I was noticing it - they were sending everything 3 times because they're running 3 containers, so maybe you're running 2?
It's fixed for them now, as discussed here
I restarted the federation containers and my test site now only receives 1 activity, when I upvote something. Before I received 2 activity requests, where nginx returned 400 for the first request and then 200 for the second request.
Is it fixed for now for you as well @[email protected]?
It is, yes. Thank you!
For federation I run 3 containers as lemmy.ca seems to do, however the indexes are set to the correctly value. So that doesn't seem to be the cause, as it has been for lemmy.ca
I run 2 lemmy-ui and backend containers, so maybe that has something do with it? I run a test site, so I will look into it and see if I can figure out the issue.
Thanks for notifying me of the issue :)