Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)KI
Posts
1
Comments
519
Joined
2 yr. ago

  • If communities want to amalgamate, they can just collectively choose to use a different community. Negotiate mod status for the immigrating mod team, and abandon the old instance. With small communities, this is feasible. With large ones, it's not, as a significant number of members won't want to amalgamate. And they shouldn't have to.

    At the user level, lists and antennae would give users a lot of power to shape their streams.

  • Indeed, there's a viability threshold for a community, and it's probably on the order of 100 active users. Having them spread out isn't doing any of them any favours.

    But that points to the need for and importance of discovery tools. Community tags, better search, better federation tools, better back-linking and cross-posting tools, user-defined lists, etc. The Misskey/Calckey "Antenna" saved-search feature would actually be very powerful in the threadiverse, particularly if coupled with community and post tags, and would really improve the visibility of new or undersized communities to those who are looking for them.

    But forced amalgamation across independent and independently operated websites definitely isn't one of them.

  • The whole point of that server is to allow people to simply login and then participate in other instances from there.

    In order for users on lemmy.one to interact with content on other instances, lemmy.one has to import and host that content. So, it has plenty of content on it, just most of it originated elsewhere. That remote content should be just as indexable as local content.

  • Off the top of my head:

    • API's a big one. Mobile app development for kbin is deeply hampered because of that.
    • The ability to quickly filter your timeline by Local/Global, which is a big deal for regional or themed instances.
    • A (more) easily accessible subscribed community/magazine list (slower/smaller communities are kind of totally smothered in kbin).
    • PeerTube federation.

    Meanwhile, the domain block touted by the OP is buried and kind of a pain to get to, and the search claim is... overstated (kbin search still only reaches other sites that the given kbin instance is subscribed to).

    kbin has a nicer UI, IMO, and it's fine. It's perfectly fine. Lemmy is also perfectly fine. Neither is excellent, and that's ok. Neither has reached version 1.0, either, and both are being developed by small teams (for some flexible definition of "team").

  • Ehhh. kbin's quite feature-incomplete in its own right, it's just a different set of features that are incomplete. I don't think there's anything about kbin that's actually superior to lemmy, just... different. Meanwhile, Betamax had inarguably better video, and inarguably worse capacity.

  • Because having communities with an identical name on different instances will fracture the community.

    They're different communities on different websites, though. Trying to force them all into one space is erasing all communities but one, just for the sake of having to see an @website.com address, or for pretending you're not missing out on something when you ignore 99.9% of posts and comments that end up in the space.

    1 million users discussing a topic spread out across 1000 communities of 1000 active users leads to more vibrant and meaningful discussions on that topic than having 1 million of them all crammed into one place, shouting and competing for slivers of attention. And no one will miss anything of deep value in the 999 other communities, because people will cross-post the good bits anyway.

  • the prevention of multiple separate communities having the exact same name is convenient and simple

    Except for when those communities have names that aren't intuitive in any way, or the intuitively named communities are full of off-topic content.

  • I don’t think it should be done by a specific name, it should be user defined, I should be able to add the communities together which I deem that they do belong together for some reason.

    This.

    People are used to a single handle mapping to a single community, and I get that they want that to still be true, but it isn't here. It just isn't. Having a communities auto-group in any way is asking for a bad time for all involved.

    First of all, people generally are not considering the contexts that those communities are situated in. My go-to example here is politics communities. r/politics is, very frustratingly, about American politics, but that isn't going to be universally true here for communities named politics. You should not assume that an Australian based server, a Canadian based server, a UK based server, an Indian based, etc. will reserve that name to deal with, well, foreign politics. And having them automatically lumped together will functionally destroy the communities on instances focused on smaller countries.

    In top of that, it's wide open door for troll instances.

    If people want lists of communities, that's fine. That's great even. I'd love to lump together some sports communities so that when I'm in the mood for that, I can find them all in one place. It'd be cool to be able to have them optionally not show up in Subscribed, too. But auto-grouping is one of those features that is actively bad for smaller communities, and which people really only think they want. It's more of a sign that people aren't opening their mind to this new space and paradigm they find themselves in than an actually useful feature.

  • In grad school, my friend couldn't print anything on the office printer to save his life. It just hated him, and him in particular.

    I once helped him print a document that wouldn't print by walking over to his desk, hitting the print icon, and then clicking "Print".

    I could tell that the printer really, truly hurt him that day.