Posting the same thing to like 5 different communities at a time

Admiral Patrick@dubvee.org to Mildly Infuriating@lemmy.world – 127 points –

I mean, I get annoyed when I see the same thing posted to two communities back to back, but 5 is ridiculous and extremely poor fediquite.

Edit: Seems the poster is some kind of spam bot. As one commenter pointed out, they seem to have spammed this to any community with "music" in the name. And it's more than shows up in the screenshot. A LOT more.

32

Bonus mildly infurating: How can it be an 90s song and an 80s song?

Released in 89 and stayed on the charts through the 90?

Uuuuughhhhh. Fine. lol. Take my upvote. 😆

They also posted it to 70's music haha.

Not about this specific post (which might be a spam bot), but in general: If a post fits several community, I don't think it's something bad to crosspost it to them.

I'm of the opinion that you should pick one. If there's not enough engagement after a respectable period of time, post to another. I definitely don't think one needs to broadcast their thoughts/opinions out on all frequencies every time.

Then you get, why are you reposting this, you just posted this 3 days ago.

The solution is to cross post, and let the users filter the content they don’t want. Why follow 5x different music communities using your logic?

We out here Top 6 Hours’in’ All.

But the moment Lemmy/the average app supports cross-post consolidation or duplicate filtration, I’ll definitely agree. Even until then, you’re not wrong, but it does complicate recommending a best practice.

They posted it to any community that had "music" in the name regardless of if it fit. Either a spam bot or those annoying people who think more is always better when it comes to getting your name out there.

Yeah, I just noticed that when I went into their profile after posting this. They just earned a spam ban.

It should be combined into one post appearing in all communities it's crossposted to IMO. Maybe also with only one comment section under it, but that would bring some problems.

It's even worse on the NSFW instances.

It'll be 20+ posts in a row by the same person.

As someone who used to post OC, it's why I left. Nothing but OF spam bots and pics of pornstars. Reddit is somehow the better option, unfortunately.

mbin combines crossposts into one thing, so doesn't bother me. but even if I saw it multiple times, so what? scroll past

Lemmy does that in the post view, but not in the feed. The API doesn't provide xpost data, and the UI has to wrangle those which is imperfect and only works if the posts are retrieved in the same fetch.

I do usually scroll past, but when there's half a page of them, I get more than mildly annoyed lol.

Lol I saw it so much I had to click on it and I told myself if it sucked I would come back and block the user.. turns out the song isn't very good so now I don't have to see it ever again

What UI is that?

Tesseract. You can use it for your own instance by logging in to it at https://tesseract.dubvee.org/ (which is a bit counterintuitive, because there's also a local Lemmy server there, but it works). Or self-host it of course (see https://github.com/asimons04/tesseract)

Yep. Though that's my dev version in the screenshot.

Something's not quite working btw. It's tricky to chat about because various front-ends auto-convert absolute links to instance-specific ones, so I'll surround them in code blocks and hopefully they'll leave 'em alone. Anyway: the fedi-link for this post is https://dubvee.org/post/1007192 which is where it is, but if you try to visit that with a browser you're re-directed to https://tesseract.dubvee.org/post/lemmy.world/1007192 which isn't correct - it should either not re-direct you or re-direct you to the correct URL at https://tesseract.dubvee.org/post/lemmy.world/14138451

I don't want to take over the comments with this, lol. I've got a community you can post that in if we want to discuss it further. Community: https://dubvee.org/c/tesseract

I think it's a glitch with the guest instance being set and unable to determine the post ID on the remote instance. When I clicked the first link (https://dubvee.org/post/1007192) in incognito mode, it took me to the expected post (https://tesseract.dubvee.org/post/dubvee.org/1007192) . When I switched guest instance to Lemmy World, and retried the same original link, it did redirect to the wrong link (using the post ID from my instance on LW which doesn't exist).

Yeah, I should not have it redirect when you're browsing as guest since it requires an authenticated call to resolveObject to determine the correct post ID on the remote instance. Should work fine if you're logged in, though. I'll address that in 1.3.0.

Thanks for pointing that out!

Edit/update: I believe I have this fixed in the 1.3.0 latest dev branch.

The point of federation is to connect different servers. Lemmy is not one website. It is many different websites that happen to share data. A link being posted to multiple websites is fine.

Maybe if you're seeing too many duplicate links, you're subscribed to too many duplicate magazines/subs/servers.

Maybe if you're seeing too many duplicate links, you're subscribed to too many duplicate magazines/subs/servers.

That's exactly the point. Most people are, too.

It would be nice if we could specify a priority list for communities (each user creates their own). If a post is crossposted to multiple communities, only the one posted to the community with the highest priority gets shown on the feed.

They posted it to connectasong which is especially annoying. We have VERY specific posting rules over there! It's a game!

There’s nothing wrong with posting the same post to several groups, as long as it’s a text post and not a link. I will also vote down or block people posting just a link