• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle




  • Under activitypub, a lemmy community is kind of like a user (actually an activitypub group). When I post here with my lemmy.nz account to this lemmy.world community, lemmy.nz sends my comment to lemmy.world who then sends it to sh.itjust.works for you to see. The community is the controller of all interactions within the community. In this case, lemmy.world is the official source of how many upvotes this post has. And each vote is validated using the user’s public key to ensure it actually came from that specific user - a standard part of ActivityPub.

    So would lemmy.world assign a token for your votes? If your instance assigned the token, Lemmy.world would not be able to validate against your user’s public key. If Lemmy.world assigns the token, it would only be valid in lemmy.world communities, as other instances would have to assign their own token. And both sh.itjust.works and lemmy.world admins could still see the real association.

    Also, changing how votes work would break compatibility with other ActivityPub software (e.g. Mastodon could no longer interpret an upvote as a favourite, Mbin would’t be able to retrieve any data about the votes unless they specifically changed to work in the Lemmy way instead of using standard ActivityPub).




  • Just to be clear, I think registration applications are necessary for anyone without a team of admins across the world.

    I’m not saying these instances requiring applications are doing a bad thing. Just that it’s a barrier to entry and given the non-commercial decentralised nature of Lemmy we will never be able to hire thousands of staff to handle reports like Facebook does.

    It’s a new problem requiring a new solution, and while I think Mastodon hasn’t solved it yet, I think they are ahead of Lemmy.


  • I explained in another comment to someone else, but to recap Lemmy.world has lemmy’s registration applications feature turned on, but behind the scenes they run a bot to approve everyone who types the requested thing in the box. You sign up, type the thing in the box, and you get immediate access.

    Compare this sign up process to the instance that the Lemmy devs run on Lemmy.ml.

    Now to be clear, I’m not saying it’s unjustified. Trolls and spammers are a problem on Lemmy and we need more tools to help. Most instances require registration applications and I think that’s necessary for anyone without a team of admins across the world.

    But that doesn’t change that it’s a big barrier to entry. Facebook has thousands of people able to respond to reports in a short period of time. Decentralised non-commercial Lemmy instances can never meet this, so we have a problem that needs a solution.


  • Yes they are a good candidate I think. Curious about their sign ups though. Lemmy.world asks people to write “I agree to the TOS” in the answer box. If you do, a bot automatically approves you, if you don’t, a bot automatically declines you. There’s no waiting time.

    Lemm.ee states In the “Answer” box below, please state that you agree to follow the lemm.ee instance rules (found in the sidebar of our front page), which has no specific phrase you need to answer, so I’m guessing they manually approve them?

    I honestly think registration applications are a huge barrier to anyone not already on the fediverse.


  • We are fine, but it’s not fixed. I have a second VPS running in Finland, using this queue batcher. The Lemmy.world team kindly set up their server to point to this VPS instead of the actual Lemmy.nz server, then the VPS collects all the events and sends them to the Lemmy.nz server in batches of 100.

    It keeps us up to date, but it’s cheating 😆

    Last I heard Aussie.zone doesn’t have this setup, but they do have a prefetcher (or rather, Nothing4You, who made the queue batcher, is running a prefetcher for them). This basically takes the new comments and posts from Lemmy.world, and sends a request to Aussie.zone to fetch that post. Because this happens outside the normal federation queue it can be done in parallel. It means when Aussie.zone receives the federated activity from Lemmy.world, it already has it, so it can reply quicker and process more events per second. Lemmy clears out activities older than a week in a weekly scheduled job, which is why you will see Aussie.zone’s backlog drop a bit once a week. They won’t get that content from Lemmy.world, it’s just lost. Because of the prefetcher, it’s likely just up/down votes (which can’t be prefetched).


  • Oh definitely some. At the time we were still in the tail of the reddit surge, we were getting plenty of valid registrations and spam was only starting to take off (which was the reason for closing registrations).

    But to my point, I think back to my first Lemmy experience and remember trying to work out which server I should join even though I already had a basic idea about the Fediverse from Mastodon. And I just chose the biggest in the end bpecause how do you choose? Even today I would be wary about joining any server that didn’t have lots of people.

    And later I remember hearing about Beehaw then finding a registration application page and not creating an account.

    These happened well before the reddit exodus, and I never really got into Lemmy until that happened and I joined Beehaw.


  • Doesn’t that say they default new users to a server owned by them? That’s the same kind of thing as defaulting to Lemmy.world for Lemmy apps.

    What I mean is a larger list of trusted instances. Including ones outside the control of one organisation, though I get that this is risky for Mastodon because they don’t want to default people to somewhere that’s going to shut down or have some drama and ruin a hard earned brand.

    We probably have more leeway to do it in Lemmy apps since (with the exception of Jerboa) they aren’t developed by “Lemmy”, and Lemmy.world is also not run by “Lemmy”. But for this same reason, " Lemmy" has no control over what these apps default to.


  • When a user (say, my mother) gets to a page that says pick a server, she would immediately close the page and go do something else. How do you even begin to choose a server? What if you get it wrong? What should you consider when picking a server?

    Its a simple concept that can be explained in a minute. But if you don’t have someone sitting next to you that understands it and can explain it, that user is gone.

    Registration applications are an unrelated barrier but a barrier none the less. You don’t have to apply to Facebook and wait to be approved. People expect to just be able to sign up and immediately go.

    For anyone familiar with the fediverse both of these things seem like non-issues. But for your average Facebook user. Hell, even your average reddit user, they will take one look at either a page telling them to pick a server or a page telling them they have to apply and wait, and unless they are familiar with the Fediverse already then they will back away slowly (or quickly).

    When my instance turned on registration applications, there was a 10x drop in the number of registrations, and I’ve heard similar numbers from others.


  • I think it would definitely be nice to spread users (and communities) across more instances. Doubly so since I’m on an instance that is struggling with the volume of content from Lemmy.world because of what is effectively a limit of how much you can get from one instance at a time.

    But if we want people on Lemmy who don’t know what Linux is, then we need to avoid that massive barrier of asking users to pick an instance. And the second massive barrier of registration applications.

    A good compromise I think would be to have multiple trusted servers with open registrations that the app randomly defaults them to when they go to sign up for an account.