Content jacking and top posting other people's content is really bad for Lemmy. It's also just being a dick to other people making content on the platform.

feed is spammy
divides conversation
chills engagement
makes Lemmy less friendly to posters

This pattern is very common on lemmy, and needs to stop.

This is often used to attack or force migrate conversations from a instance someone doesn't like to another instance they do like. It's offensive by its very nature.

If you want to make a better community, great, do it but not at the expense of other Lemmy posters.

you are viewing a single comment's thread
view the rest of the comments

[–] jet@hackertalks.com 12 points 1 week ago (1 children)

Is your desire to concentrate people's interaction to favored instances greater then the agency of the contents original poster?

I don't think it's good for Lemmy as I outlined above. Give people informed choice, but respect their agency

[–] Blaze@lemmy.dbzer0.com -1 points 1 week ago (1 children)

If you look at that thread, people just don't care about the instance that much

I’ll go wherever the action is, I just want an active community. If people wanna move I’ll be there.

I’ve just joined the community, but I’d be happy to move across wherever.

As long as you do not go to an instance that blacklists lemmy.ml, I’m fine.

Inertia is the main reason the .ml communities are still the most active on their topics.

[–] jet@hackertalks.com 6 points 1 week ago (1 children)

As long as you do not go to an instance that blacklists lemmy.ml, I’m fine.

..... isn't the one of the main rationales for the top posting because ml is blocked on many instances?

[–] Blaze@lemmy.dbzer0.com 1 points 1 week ago

No, the rationale is to allow people to block (more like mute, Lemmy-blocking doesn't really block) lemmy.ml

If !fantasy were to switch to !fantasy@lemmy.zip

lemmy.ml users would still be able to access it
users lemmy-blocking lemmy.ml would still be able to access it, and see comments from .ml users

That's an improvement over it being at .ml, where the second point isn't possible