this post was submitted on 08 Apr 2024
317 points (97.9% liked)

Fediverse

28295 readers
726 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
 

I realise this is a known issue and that lemmy.world isn't the only instance that does this. Also, I'm aware that there are other things affecting federation. But I'm seeing some things not federate, and can't help thinking that things would be going smoother if all the output from the biggest lemmy instance wasn't 50% spam.

Hopefully this doesn't seem like I'm shit-stirring, or trying to make the Issue I'm interested in more important than other Issues. It's something I mention occasionally, but it might be a bit abstract if you're not the admin of another instance.

The red terminal is a tail -f of the nginx log on my server. The green terminal is outputting some details from the ActivityPub JSON containing the Announce. You should be able to see the correlation between the lines in the nginx log, and lines from the activity, and that everything is duplicated.

This was generated by me commenting on an old post, using content that spawns an answer from a couple of bots, and then me upvoting the response. (so CREATE, CREATE, LIKE, is being announced as CREATE, CREATE, CREATE, CREATE, LIKE, LIKE). If you scale that up to every activity by every user, you'll appreciate that LW is creating a lot of work for anyone else in the Fediverse, just to filter out the duplicates.

you are viewing a single comment's thread
view the rest of the comments
[–] catloaf@lemm.ee 46 points 7 months ago (2 children)

If it's reproducible, you should file a bug report with Lemmy itself.

[–] freamon@lemmy.world 29 points 7 months ago (1 children)

I can't re-produce anything, because I don't run Lemmy on my server. It's possible to infer that's it's related to the software (because LW didn't do this when it was on 0.18.5). However, it's not something that, for example, lemmy.ml does. An admin on LW matrix chat suggested that it's likely a combination of instance configuration and software changes, but a bug report from me (who has no idea how LW is set up) wouldn't be much use.

I'd gently suggest that, if LW admins think it's a configuration problem, they should talk to other Lemmy admins, and if they think Lemmy itself plays a role, they should talk to the devs. I could be wrong, but this has been happening for a while now, and I don't get the sense that anyone is talking to anyone about it.

[–] Iceblade02@lemmy.world 13 points 7 months ago (1 children)

You can still make a bug report, so that somebody with the actual means can look into it. If every action is duplicated that'd be pretty severe, if not, well it'll be closed.

[–] freamon@lemmy.world 19 points 7 months ago (2 children)

A bug report for software I don't run, and so can't reproduce would be closed anyway. I think 'steps to reproduce' is pretty much the first line in a bug report.

If I ran a server that used someone else's software to allow users to download a file, and someone told me that every 2nd byte needed to be discarded, I like to think I'd investigate and contact the software vendors if required. I wouldn't tell the user that it's something they should be doing. I feel like I'm the user in this scenario.

[–] Iceblade02@lemmy.world 4 points 7 months ago (1 children)

Idk, it's FOSS, so you could always try, but just complaining and hoping somebody picks up on it probably also works. I don't judge :)

[–] freamon@lemmy.world 14 points 7 months ago (1 children)
[–] Alice@hilariouschaos.com -1 points 7 months ago

Oooooo you sassin

[–] SorteKanin@feddit.dk 7 points 7 months ago

It seems its a misconfiguration problem when running multiple server processes, which mostly is only done by larger instances. So it's not a bug in lemmy per se, but perhaps a bug in lemmy.worlds configuration.