• 32 Posts
  • 6 Comments
Joined 2 months ago
cake
Cake day: November 6th, 2025

help-circle




















  • I specified already, people see the instances you post from and builds recognition for that due to the volume with which i post. So I rotate around which ones I post from

    when you use these accounts to post to huge instances like lemmy.world (which you do frequently)

    I haven’t posted to a .world comm (with the exception of linux_gaming) since the JL fallout and have moved quite a few of the comms I created there off it and am planning to move some of the larger ones I mod off there

    although I’m not convinced it’s really a problem.

    It actually did happen to me, and they were spouting right-winger Nazi bullshit sooo yea. Turned out it was UM (unsurprisingly) lmao

    And btw some of those accounts in your screenshot are the imposter accounts like Lonestar, az.social and pawn

    But some of the others I don’t post from much if at all and just make comms with them


  • Oh I don’t do that for that, there’s multiple reasons, but one of the bigger ones is to promote smaller instances because of the volume of posting it makes smaller instances more recognizable.

    Other reasons for the multitude of accounts include making comms on fitting smaller instances (I make programming related comms on programming.dev or retro related on retrolemmy for example), protecting against the imposter problem and better interconnecting wayward smaller instances (you’d be surprised at the number of, even common comms, that smaller instances are missing out on that I discover just through my posting)


  • I do crosspost all .ml content and tag the user if it’s OC, as part of boycotting efforts against .ml. It shows in the crosspost section of your client

    Not that it’s relevant in this particular case, this is my own sourced article not posted before to the Threadiverse

    Why am I cross-posting .ml content?

    I cross-post from .ml to the nearest relevant non-.ml comm to reduce the influence of .ml comms and indirectly, the instance as a whole, to make it an easier decision for other instance admins to defederate because one key reason I identified that admins don’t want to defederate is because .ml still has some very large comms and some niche comms.

    Megathread on the issue

    Some highlights from the link:

    "Don’t worry guys, the Uyghur Genocide was REALLY just birth control! ~dessalines, .ml admin, dev https://lemmy.world/post/30580167

    “See! nobody died IN Tiananmen Square, just AROUND it, so it doesn’t count!!” ~ Davel, .ml admin https://lemmy.world/post/30673342

    .ml admin, Nutomics continued transphobia https://lemmy.world/post/29222558 The original transphobic Comment from Nutomic: https://lemmy.world/post/18236068

    “NK is actually good and anything counter to that is Western propaganda!” ~dessalines, .ml admin, dev https://lemmy.world/post/31595035

    General negative sentiment to other instances who haven’t “seen the way” yet ~davel, .ml admin https://lemmy.world/post/27426510

    “If you don’t support Russia then you just don’t understand geopolitics” ~dessalines, .ml admin, dev https://lemmy.world/post/27352415

    And so so much documentation on clear heavy handed censorship and bias also on the link. So much I can’t even put them all here because this comment would be really long.

    I believe the behavior of its admins (the main admins are Lemmy devs) does harm to the overall growth of the Lemmy-verse and maybe even the Thrediverse (since Lemmy kinda kicked off the Thrediverse) because of its association with the devs of Lemmy and their insistence to use .ml as their personal political platform to spread harmful propaganda

    On the outside, bringing up Lemmy frequently leads to comments like “Lemmy? Isn’t that the place with a bunch of tankies?” Or “Tried Lemmy, but found it full of pro Russia crap so I left”. The best way forward from that I see is to either widely defederate from .ml like the rest of the Triad, or pressure them to put a fair and unbiased as possible admin team.