• There’s also the fact that a bunch of instances immediately closed registration as soon as the Reddit refugees started arriving. They couldn’t handle the sudden extra load, so they all closed their registrations. Which is their right as owners, but it also meant that virtually all the new users were funneled to the instances that were willing to expand, with Lemmy.World being one of the only ones.

      Hell, I still haven’t received registration emails for most of the “we’re filtering our registrations. Click the link in your email to verify you aren’t a bot” instances I tried to register with.

    • Urgh, yeah.

      I use the ‘official’ Jerboa app and the web interface and duuude is it a Hassle to add a sole unknown community!

      I’m doing them all for what I know ; pasting different link types into jerboa search, pasting the instance, !first, /c/ … Going to web UI, doing the same, doing the lemmy.mysite.com/c/other@thatinstance.com or what the correct thing is (I have it somewhere) and obviously it still doesn’t work.

      For like 30 minutes.

      Then it “just works” 😅

      It would be great if admins at least (I can see the possible abuse if anyone can force-feed communities to the instance, but well they can today so… ) can add communities to their instances by some “add-list” the server grabs quickly (I know we can by subbing to them but see above, it sure is not easy). Could be cool to be able to grab a bunch of fun communities, or art communities, or sport communities or whatever someone shares, and just force feed them to your instance.

      I thought whitelisting was something along those lines, I sure was surprised 🙂.

      Great job though Lemmy Developers, I’m quite sure Lemmy will roam the internet for ever!

  • Yes please! Lemmy.world and lemmy.ml shouldn’t make up the majority of my feed.

    I think best case scenario, you have themed instances based around art, tech, politics, news, gaming, food, etc, and the largest communities are hosted there. Then you have “catch all” instances like lemm.ee which federate with everything, there can be as many of these instances as needed as the user base grows. These types of instances should be where the bulk of the new user accounts go, assuming just an average user looking for a /all replacement. Curated instances like beehaw allow for a more fine-tuned experience, but should still function basically as a catch all and not as “hosting the content” instance.

    However I understand that building up to that is damn near impossible with the current infrastructure. We would basically need a means to migrate an entire community to a new instance, while simultaneously updating everybody’s subscriptions to reflect the new home of the community.

  • Think we need universal/transferrable accounts to make this happen. People, myself included will be concerned that if they sign up to a tiny instance someone’s hosting on a raspberry pi or something that it’ll just disappear without a trace one day and their account along with it

    If accounts were made portable I think a lot more people would disperse

    •  xavier666   ( @xavier666@lemm.ee ) 
      link
      fedilink
      English
      1611 months ago

      The amount of data that needs to be exchanged because of this approach is not scalable. Assume that there are 3 instances with 100 users each. Even if lots of users upvote/post/comment, the traffic is exchanged only between 3 servers. But if there are 300 single user instances, the amount of traffic/storage will be duplicated which can cause a huge load for everyone which might not be viable in the long run, for both the sender and receiver. PS: I am assuming that the instances periodically update content by fetching the deltas.

      • Just go to your average big popular subreddit, check out all the text of all posts and comments they week. That’s still a minuscule amount of data. A few megabytes when uncompressed.

        And Lemmy won’t get to that point of popularity and traffic for a very long time.

        And even then, it’s an easy problem to solve. Each instance creates a chunk of a day’s data, sign it and share it on a bittorrent like protocol. Even nntp massively archaic infrastructure can manage this, it is a piece of cake for Lemmy to do.

      • I am assuming that the instances periodically update content by fetching the deltas.

        That’s incorrect, so far no batching is set up for sending multiple posts at once and the exchange is initiated by the sending server, not the receiving server.

    • 🤔 We need an ActivityPub app that is basically just a user account holder that is tied to their IP or MAC address so individuals can carry the same info throughout the fediverse, block instances they personally don’t like, and so bans from instances are actually permanent and enforceable.

    • The key based (and content addressing based) thing is what bluesky is building. They’re starting of with Twitterish microblogging, but there’s people building forums on top the protocol too. Federated, of course.

    • I think instead instances should have every community. There isn’t one /c/books, every server has a /c/books. Your feed pages just pulls from the entire fediverse. No concept of “creating” /c/books, it just is.

      Likewise, there isn’t “a” moderator. Every user is a moderator. Whether you vote, or delete the post out ban the user (from your view), your moderation opinions are published publicly. Your local feed algorithm sees everyone’s “moderation opinions”, if the consensus of the community is delete, then it just doesn’t show up in your thread

      For each “moderation opinions” by a user, your client investigates their historical record to address credibility and likelyness of being a bot, a user’s history is his credibility

      • I’ve got similar ideas, but not entirely the same.

        What you call communities would be closer to what I would call content sources / repositories (host servers) plus topic tags. Then instead of consensus (because that’s too hard to automate with decent quality results) you’d have communities formed by subscribing to “curation feeds” which pull submissions and comment from all over the network in a similar style.

        This would let you easily crosspost and comment to multiple related communities in a network, as well as to yeet bad mods/curators without losing any content or splitting the community (just create a new curation feed and get people to switch). You could similarly choose to have your client mix comment from multiple curation feeds (similar to “multireddits” on reddit).

          • As a midpoint there’s things you can do like “2/3 consensus of X, Y and Z’s submission selections on topics ABC”, then defining that as it’s own feed people can subscribe to.

            But it gets complicated to mix and match when different subcommunities have very different local cultures.

  • Every country should have their own instance and people should sign up to the server that’s closest to them or that best fits their privacy concerns.

    I would love to see more federated social media servers in Switzerland for example.

  • If everyone was spread out onto different instances

    Each instance with an owner/operator making rules… that the average social media user walks in, orders a drink, and starts smoking without any concern that neither one may be allowed. People can be loyal to their media outlets even when it is beyond obvious they are bad. People raised on storybooks that endorse bad behaviors and values, HDTV networks, and social media too. Audience desire to “react comment” to images and not actually read what others have commented - nor learn about the venue operators and reasons for rules is pretty much the baseline experience in 2023.

  • I do still see value in a general landing page for new lemmy users, but this whole thing has really shown me that it should not be anything like this. .ml and .world have done a lot of work becoming the “big” instances and now they have a taste for censorship (and have most the users) I doubt it will get better.

    •  wewbull   ( @wewbull@feddit.uk ) 
      link
      fedilink
      English
      111 months ago

      I don’t know how federation works in detail, but I really hope it’s like torrenting where peers introduce each other. That way if one person decides to defederate with an instance it’s a decision that only applies to him. If anybody else is federated then the connection information is available to all. i.e. the network heals around damage.

      I have no problem with someone constructing a bubble for themselves, but they don’t get to say what’s in my bubble.

  • Correct me if this is already a thing, but it would be nice if you could post to multiple communities at once and have users see comments across all communities and instances. So a user posts “A” on instances X, Y and Z all under communities run on those instances at the same time. When making the post, you select ehich communities the post goes to instead of just one. Users on instances X, Y and Z see it as a single post it appears in all of the communities the user specifies. A limit might be useful here to prevent trial spam. A user commenting on the post in instance X will be seen on the other instances and communities where that post was made.That way, you could remove the centralisation on instances and communities (one community or instance might remove the thread, but everybody else still sees it and each others comments in the remaining communities/instances.) This has a few advantages:

    • People are incentivised to post to smaller communities knowing that larger ones will also get the same post and everybody can see each others comments.
    • If a moderator of a community removes the post, it still disappears in their community, but not the whole instance. If the thread still exists in other communities in the same instance, users of that instance can still participate in the post on those communities.
    • If the post is banned instance-wide, it is banned across all communities in the instance at once. This could include non-local communities.
    • Users in other instances will still be able to see the post and continue contributing to it. You can only remove the post from your own instance.