Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-At this time we permit content that is infuriating until an infuriating community is made available.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
There were also 2 more below that.
And this must be a bot, endless posts by this user, every time the same content on multiple communities.
Daily Reminder, Discussion is okay. Name caling, vitriol and toxic behaviour is against our community rules. Nothing is worth an argument. Discuss away but leave the aggression at the door.
It goes without saying, but any user included in the post should not be harassed. Those found to be following this person will be banned from the community.
Here's my idea:
It's a middle ground between completely hiding the duplicates, and letting them as is. Once you click that plus button, it shows the duplicates as full posts, otherwise it leaves them as just one-liners.
There is discussion on going at [email protected] currently about new rules. Users posting the same story from the same source will be blocked by an automod. I asked about users posting the same story from different sources, and apparently that's absolutely fine. So expect this problem to get a lot worse before steps have to be taken to make it better :/
The issue is that this sort of rule only works against duplicates inside a community; it does nothing against duplicates across communities, that users may or may not be subscribed to. As such I think that the solution should be on the interface level.
On another, related matter: you replied twice. I think that the server itself should prevent it, as 99% of the time it's by accident.
Can you put this suggestion on their Github issues tracker? It's brilliant.
I like this one. It conveys all of the pertinent cross posting info in a succinct manner.
This also happened on reddit
It did, but it wasn't as bad as this. My hope is that as Lemmy matures, this will happen less.
It got lost on the noise of reddit. There’s no way lemmy has more bots, let alone a higher ratio to users.
And it’s entirely up to your instance, the instance I am in has strict bot rules that other instances bots must follow.
wtf do the bots have to do with this? the issue is that multiple communities are all talking about the same article in many different places when they should be all talking about it in 1.
Absolutely not, the benefit of each community having its own vibe is exactly that.
Think of it it like this, one community is for Germans and one is for the French. They can talk about the same thing, but they will Absolutely go about it differently, and that’s fine. Pick which one you want to help/join, or hit up both.
The only way it happens less is if lemmy actually does something to merge communities or treat cross posts as a single post.
unless communities and users become agnostic to instances, this problem will never be solvable. also defederation makes this virtually impossible.
There is a cross post feature, and the resuting post appears to be aware it was cross posted - it would be nice if Lemmy would consolidate those to one post that appears in multiple communities, or at least show you only one of them.
Lemmy needs cross communities that exist across instances otherwise it's going to get more and more fragmented
Why do people insist that there needs to be (for example) /c/politics on every instance? Really, there are only 3 or 4 with any substantial traffic, and there are good reasons to pick one over the others, and they are the same good reasons for them to be separate.
Why do people insist that there needs to be (for example) /c/politics on every instance?
This is a fundamental issue with the way that lemmy is organized that was identified early. Its a design consideration thats pretty much baked into the cake that each lemmy instance effectively tries to be an entire reddit.
Its a bit of an issue, because this will necessarily dilute the kind of network effect that is what allows social media to be as engaging as it can be. Interesting articles don't get as much momentum. The interaction is more diffuse. Conversations are more spread out and fragmented.
Its beyond the scope of the current design, and I really do commend the developers for what they've built (lemmy as is a great experience); however, a more 'instance' based approach may have made more sense based on how we've seen things scale. Instead of every lemmy instance trying to be 'all of reddit' each lemmy instance would focus on a set of niches (for example, a fashion focused instance would have c/fashion, c/mens_fashion_advice, c/streetware,... whatever); then they would federate to propage these niche across the fediverse.
The Star Trek lemmy instance is an example of this. Its a home for all things star trek. I also tried to start something like that focused around WallStreetBets, but afaik, WSB had almost no exodus.
More importantly, the critical mass to get enough users for the content to be interesting didn't happen. There were too many competing /c's across the lemmyverse. So articles get posted, but none get more than 1-3 upvotes because the userbase that would get it to say 5-15 upvotes simply isn't there.
I really do love lemmy for what it is, but this design consideration is absolutely what is preventing Lemmy from being a true Reddit killer. The structure of federation sets lemmy(s) up in a way that there is an inherent blocking factor to super-connectivity.
However, I can imagine a couple solutions to this that dont necessarily require a full burn down and rethinking of lemmy.
One would be to allow for the merging of communities. Users set up C's, but if there was some way to do a kind of merge (as like on github), where the two RSS feeds could be merged (as in github). Likewise, it would make sense if there were a way to 'split' or fork communties, as in, say you've got c/fashion, and some one wants to fork off and have it become c/mens_fashion. This would allow communities to consolidate around critical mass (there are enough posts, comments, etc to represent meaningful engagement), and then also to diffuse that issue latter when it makes sense to maybe split off political memes from say, political discussion.
A second solution would be to allow communities to be 'transferred' across the federation. This makes sense in that your 'local' community should be comprised of the things you care about the most (fashion, mens fashion, streetware, etc..). This feature would allow niche communities to consolidate into single instances, which will also serve to drive engagement (a user of mens fashion is far more likely to post into streetware and vice versus).
A third option would be to build a super structure to lemmy that allows for the consolidation of multiple lemmy RSS feeds into one. Effectively, user would be able to identify various lemmy communities into 'supper communities' that consolidate them under a single heading (a tool to grab up all the 'mens fashion advice /c's across the fediverse) and deliver it in a single RSS feed.
Of the three of these the third option makes the most sense to me. It requires the least rework of the underlying data structures, and seems like a bolt on solution. However, it also might be the least effective of the three. I've no intuition about what that would do the structure of the network or if it would aid in overcoming critical thresholds of engagement.
This icon 
makes a cross-post, it shoud be used, because it combines them in the feed if both are in the same view (often in New), but it probably should be automated, at least if the link and the title are the same, so it also works if someone doesn't use the button to cross post.
Example:
This way you still are only one click away from each communities comments.
Yes when I see this I downvote all duplicates.
Lemmy should, however, find all federated duplicates and offer you to cross post an existing one when such a case arises. It would fix many of these cases.
Not all clients support this (yet). I only found out about this recently and have to go to the browser to use the crosspost feature.
It's the same motherfucker just karma farming
Farming what? There is no karma on lemmy
There is karma on lemmy, available through api
okay but literally no one cares about that
Maybe he just hates Zuckerberg that much haha
Just block the user?
Yep, it's one thing if someone is posting a lot to a sub they want to grow. But if someone is posting the same article to like 10 different subs in 2 minutes...
Just block em
I feel like the best way to handle the situation with similar/same communities on different instances is to allow communities to automatically federated with other communities. That way subscribing to one community will show you its posts and all the posts to its linked communities.
It would be especially helpful for these general purpose communities like Technology or News since I would imagine most communities are going to have one.
If that happens then we wouldn't need to hunt down and follow every single instance of the same community. Let the mods handle it on their end to save the rest of us the effort.
not a necessarily a bot, but also there need to be a feature where duplicate posts need to be hidden. inoreader (rss reader) has this is a premium feature. lemmy apps need to draw inspiration from the rss readers, since content is similar. in fact i used to browse inoreader before using a lemmy client app.
What about the comments though? I don't think hiding duplicates or merging comments will be easy
I think bots are too agressive posting everywhere. example linkbot, it has posted over 20000 posts and its only one month old account.
I think "World News" and "Technology" are not quite similar communities. It's up to the mods of each community to decide whether the content posted is appropriate to that community. One could argue, that an article about Threads is not exactly "World News" though. Also I think that the different variants of e.g. Technology will have a "flavor" of the instance that it's hosted on. You then get the option to subscribe only to the flavors you like, or if you subscribe to all, then there's bound to be some duplicates. Maybe some future feature could combine them - it would need to be clear which comment threads are from which instance though.
personally I'm more annoyed that there are several "Technology" communities and several "World News" communities, rather than World News and Technology sharing a similar topic.
w o r l d n e w s
Eh, it's a benefit and a drawback. For those of us that don't use browsers to access lemmy, crossposting is much harder for one thing. Then you've got bots and people that don't even know that crossposting exists at all.
But, the ability to choose which communities you block and thus streamline your feed is too big a benefit to really be infuriating in natural general. Once there's a built in way to migrate block lists, it'll be even less infuriating.
But yeah, you gotta block the bots that don't crosspost correctly, or they're utter spam machines. If users behave as bots, gotta block them too. It sucks, but it's miles better than trying to artificially limit communities.
Each instance can have their own rules and mods, I have already encountered power tripping mods on lemmy.world, I can choose other instances with the same threads with different mods.
Its not really surprising to see duplicate from what are basically all 'general-purpose' instances. Merging duplicate posts into one would be a great solution.
It's a UI issue and not really an issue with how Fediverse communities work, if the same link is posted in multiple communities it should ideally show you only one of them in your feed. The user would be able to specify how he wants to discriminate between the same links: most recent one, most active one etc... It shouldn't be difficult to do at the UI level.
If these are serial reporting, Threads is down by a factor of 8. Could be more. Antelope FWY 1/128 mile.
It seems useful to have bots serial posting for a while, within some limits.
These forums have a chicken and egg problem - need posts to get commentors, need the commentors to incintivise posters. Also just need content in general to get any readers.
But I'm in general agreement that recently the feeds haven't been too smooth on Lemmy and that take a lot away from the browsing experience.
You probably have to stick to one of the communities. That's what I do to avoid this kind of issues.