EthernalExplorer

@EthernalExplorer@reddthat.com

This profile is from a federated server and may be incomplete. Browse more on the original instance.

EthernalExplorer,

You are overthinking this. If you like green tea, but an instance admin prefers coffee, would you stop posting on every community on that instance? Do you only want to post where people 100% align with your views on everything? I guess not, because then you would have to host a private instance where you only talk to yourself. Therefore, stop overthinking this and keep posting there.

If the question whether somebody federates with Threads or not is THAT important to you, then you already have your answer.

Overall, I really hope we do not come to a point where thoughts like “my instance does not federate with $evilinstance, therefore it’s a good instance. But $otherinstance does, therefore $otherinstance sucks and I’ll avoid everything on $otherinstance” become the norm. Because then we get a clusterfuck.

EthernalExplorer,

Why would Threads users join Lemmy if they can just subscribe to instances federating with them. That is why I don’t want to post on instances federating with Threads anymore

I also don’t want Threads to benefit from my posts/comments

I see.

Would you still post to lemmy.world or you would create another community on lemmy.ml where Threads is blocked, if you were in my case?

I understand your problem. It’s an interesting thought-experiment. Though I am not a fan of Meta/Threads either, it probably is not that dear to my heart as it is to you. You’ll have to decide this based upon how important the situation with Threads really is to you. If it’s a matter of principle, you probably would not continue posting to lemmy.world. That said, as it’s niche communities you are talking about, creating new ones on other instances will create a split, which is most likely not helpful for user engagement. Who knows, if Threads will bring many users, it might actually help bring life to niche communities.

Of course, you do have every right to create another community somewhere else, my gut tells me it will not be successful though. I just don’t think many will be like “Oh there is a new community for this hosted on an instance not federating with Threads, let’s move!”. Users, overall, will probably gravitate towards the community with the most activity and it’s not likely that it will be your new one. However, you may have a chance if it there is hardly any activity now.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • 200 @ user_overview
    HTTP status 200 OK
    Route name user_overview
    Has session yes
    Stateless Check no
    Time 281 ms
    Total time 281 ms
    Initialization time 59 ms
    Memory 14.0 MiB
    Peak memory usage 14.0 MiB
    PHP memory limit 128 MiB
    Logger 88
    Errors 0
    Warnings 0
    Deprecations 88
    Cache 31 in 30.67 ms
    Cache Calls 31
    Total time 30.67 ms
    Cache hits 30 / 41 (73.17%)
    Cache writes 6
    3
    Default locale en
    Missing messages 3
    Fallback messages 0
    Defined messages 131
    Security n/a
    Authenticated No
    Firewall name main
    Twig 89 ms
    Render Time 89 ms
    Template Calls 82
    Block Calls 16
    Macro Calls 0
    52 in 40 ms
    settings_row_switch 15
    date 4
    user_settings_row_switch 4
    user_inline 3
    date_edited 3
    vote 3
    boost 3
    entry_comment 2
    user_avatar 2
    settings_row_enum 2
    user_box 1
    user_actions 1
    entry 1
    magazine_inline 1
    related_magazines 1
    active_users 1
    related_categories 1
    related_posts 1
    related_entries 1
    support_us_block 1
    featured_magazines 1
    21 in 74.01 ms
    Database Queries 21
    Different statements 20
    Query time 74.01 ms
    Invalid entities 0
    Cache hits 20
    Cache misses 2
    Cache puts 3
    6.4.0
    Profiler token a9e304
    Environment dev
    Debug enabled
    PHP version 8.2.26   View phpinfo()
    PHP Extensions Xdebug ✗ APCu ✓ OPcache ✓
    PHP SAPI apache2handler