• cm0002@suppo.fiOP
    link
    fedilink
    arrow-up
    1
    ·
    5 hours ago

    Keep in mind, I stopped making new accounts a while ago, I have my set of stable, but small instance accounts and I just been cycling through them over and over again, if someone wanted to block them for curation, they should not have had a problem to do so by now. And I do have plenty that I don’t post from for comm making. There are also a few floating around from my imposter problem a bit ago.

    I do not agree that you’re boosting other instances simply by posting from them, and I don’t think the side effect you’re creating is worth the price. Further, I would argue that most users typically do not pay attention to the instance a user is from, especially when simply upvoting a post.

    You’d be surprised, Ive definitely had people ask me about instances that I’ve posted from. Especially funnier named ones like toast.ooo

    Do I have hard analyzed data? No, and it’d be pretty hard to gather such, but I’m already posting a good volume so might as well take advantage to give a boost of recognition to small instances however small it may be

    The cross posts do not show properly in my case, only sometimes do I see them on your posts. Luckily, clients like Boost add a link to their original post when I cross post. It makes the cross post always show.

    What do you mean “better interconnecting smaller instances”? If it’s through cross posting, I doubt it, seeing as you don’t include the cross post link for maximum effect.

    These 2 problems, are kinda related to each other. A big reason a crosspost won’t show, is if the other post is on a comm that isn’t federated with your instance or hasn’t pulled that specific post yet

    So basically by interconnecting instances I mean I’m encountering comms that the instance hasn’t federated with yet because nobody has subscribed from their instance to it. And nobody on that instance can see content from that comm until someone subscribes to it

    The volume with which I post makes it so I’m encountering lots of those comms every day and every time I subscribe to one of them then the instance I’m on starts to get content from it as well. Lemmyverse.net is basically my bff at this point, I’m always on there checking comms and deciding the best ones lol

    There’s a bot that does this automatically, but it’s not part of Lemmy proper, so there’s a myriad of reasons why it’s not as effective on smaller reasons everything from the admin just hasn’t gotten around to it to they don’t even know it exists or is needed

    The only other user that I’ve seen do this type of thing is Monk, and I know your views of him.

    Oh yes. UM, that wonderful user lmao. Yea, but a big difference is, none of my accounts are actually banned from anywhere with the exception of .ml (but I think that’s obvious lmao)

    • AmbiguousProps@lemmy.today
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      4 hours ago

      just been cycling through them over and over again, if someone wanted to block them for curation, they should not have had a problem to do so by now. And I do have plenty that I don’t post from for comm making.

      It’s good that you’ve narrowed it down, but cycling through them will continue to cause people to think you’re somehow a spam network.

      You’d be surprised, Ive definitely had people ask me about instances that I’ve posted from. Especially funnier named ones like toast.ooo

      I’m not asking for hard data, to be clear, but I would still argue that for the amount of people that see your posts (a lot, since you post a lot), the amount of people asking you questions about your instances is tiny. Most users don’t even comment, so the math there doesn’t really add up.

      A big reason a crosspost won’t show, is if the other post is on a comm that isn’t federated with your instance or hasn’t pulled that specific post yet

      But leaving a link to the original post would always show. Just like boost automatically does. You can see an example in this post: https://infosec.pub/post/40397999

      basically by interconnecting instances I mean I’m encountering comms that the instance hasn’t federated with yet because nobody has subscribed from their instance to it. And nobody on that instance can see content from that comm until someone subscribes to it

      I mean, that’s fine, but you don’t need to post from the account do to that. It doesn’t even need to be named with your username since you’d never post with it to begin with. It’s already an invisible action. So again, it’s not necessary to make your username seemingly associated with negative views such as spam networks or ban evasion to help instances with this. The cons still outweigh the pros.

      Yea, but a big difference is, none of my accounts are actually banned from anywhere

      It’s a low bar, to be honest.