From 2,997 active users across all lemmy instances at the beginning of June, the number increased to 52,797 by June 30th. Source.

An active user on Lemmy is "someone who has posted or commented on our instance or community within the last given time frame.” Source. That means lurkers are not counted as active users. There are currently almost 200k total users spread across the top 10 non-bot lemmy instances.

We’re really building something here!


EDIT: Looking for a lemmy app? Here’s a whole list: https://lemmy.world/post/465785

    • @Treebeard189
      link
      English
      41 year ago

      Awesome thanks I’ll give it a try. Using Connect right now and love it so far. Also got Jerboa and will be trying it as well.

      • @ShlorpianMafia
        link
        English
        31 year ago

        Jerboa is nice but it’s having some widespread bugs right now. Hopefully things get ironed out with the next update, but for now the instance lemmy.world is having trouble communicating with the rest of the Fediverse. I had weird issues with Connect too where it wouldn’t let me post because it didn’t recognize community names, despite being on the community before hitting the “post” button.

        I’m browsing in Firefox at the moment, it seems stable at least.

        • @randomwither
          link
          English
          21 year ago

          Feeling the hit with Jerboa as well, but Firefox is running nice and smooth with Lemmy right now. Going to definitely work with more apps to see which work best.

    • @BackStabbath
      link
      English
      21 year ago

      I can’t even sign in. It basically says that my account doesn’t exist.

      • @Nies221
        link
        English
        11 year ago

        Check that your instance is correct (lemmy.world) and try again when the server works better. Right now the server seems to be having a lot of trouble loading pages, etc, and maybe that’s why it’s not working for you.

        • @BackStabbath
          link
          English
          21 year ago

          Yeah, seems it was a server issue. I had used the correct instance last time as well, but it worked now. Thanks!