Posts not appearing in communities when other group actors are mentioned.
Tried making a post (link below) to a lemmy community while also mentioning two other groups. My post never appeared in the Lemmy community.
This seems like a bug, when I tried posting to two lemmy communities at once the first went through, the second did not.
Does anyone know what’s up with this?
Link to my post containing multiple group mentions and one Lemmy community:
https://chaos.social/@Draconic_NEO/113406243431431881Link to post containing two Lemmy communities:
https://chaos.social/@Draconic_NEO/113406248999089892FWIW: that post is not for 2 communities - it’s for one community (/c/test at sh.itjust.works) and one user (/u/test at lemmy.ml) - I’m guessing that it’s autocompleted to a thing that was different from your intentions.
(edit: the webfinger response from lemmy.ml for ‘test’ returns both a Person and a Group, which Lemmy can deal with, but Mastodon probably can’t, so it just grabbed the first one it saw)
@andrew_s Ok that makes more sense but I do know I’ve tried it other times when there was no user and it posted to one community but not the other.
@lemmy_support
I’m guessing lemmy is not capable of crossposting the same thing to two different communities in general, the same way it’s not possible via lemmy itself.
I’m not sure how it chooses which community to post to when there’s multiple. I would assume it would pick the first one? If it’s not, that, maybe it’s random?
@db0 Might be, I can’t be sure if it’s just the first one, or random. I don’t really want to try, my instance admin might not be too happy with me posting too many test posts in the name of science.
Though the weird thing is that it just straight up denies it even if the other groups aren’t Lemmy or federate with Lemmy, which Guppe groups don’t.
Ye I really don’t understand how the same post in mastodon is possible to appear in two different groups, but not in lemmy. I am not familiar enough with the internals.
@db0 on Mastodon it just boosts the posts, I assume that’s what Lemmy also does in addition to copying it and formatting the data as a post.
If I oversimplified or got that wrong I’d definitely appreciate if @dessalines or @nutomic could correct me on that. As far as I know there doesn’t seem to be a reason why the same post can’t appear simultaneously in multiple communties, since they’re just boosts and duplicates on the federated instances. @lemmy_support
Always post in this format:
Thread title (Blank line) @Lemmy_community @Friendica_group/Hubzilla_forum/(streams)_group @Guppe_group (optionally more Guppe groups) (Blank line) Post body@JupiterRowland Ok but does this actually solve the issue of not being able to post to multiple Lemmy communties at once? As far as I can tell when you make two mentions to Lemmy communties the first one will go through, second one will fail. If one is a guppe group both will fail since Lemmy only allows one post to go through for some reason.
No. You can’t crosspost to two or more Lemmy communities at once. AFAICS, that’s fully deliberate and intentional by design to keep people from spamming Lemmy with mass-crossposts.
What it fixes is trouble with crossposting to Lemmy, Friendica/Hubzilla/(streams) and Guppe groups. You can’t mention these in any order you like. You always have to begin with one Lemmy community. If a Lemmy community is not mentioned first, it will be ignored, no matter what is mentioned first.
Also, apparently, mentioning Guppe groups before a Friendica group, a Hubzilla forum or a (streams) group doesn’t work either.
Essentially, the title of the post/thread comes first.
Then comes a blank line.
Then come the mentions, all in one line. They must always start with the Lemmy community, and you can only mention one Lemmy community. If you want to crosspost to a Friendica group, a Hubzilla forum or a (streams) group, it comes next, and AFAIK, that can only be one, too. Guppe groups come afterwards, as many as you want.
Then comes another blank line.
And then comes your actual post.
Another blank line.
Lastly, hashtags so that Mastodon has them where it expects them.
