Live data from Hacker News

Lemmy stats (users, posts, nodes, comments)

the-federation.info

31–40 of 104 posts

Re: Lemmy stats (users, posts, nodes, comments)

#31
post #12

~277k users, up from ~51k on June 1 319 nodes, up from 84 on June 1 Sure, this is nothing compared to Reddit's userbase, but we'll see in a couple weeks how big this will get.

It doesn't really matter if lemmy kills reddit. If a new community grows and survives after this whole thing, that's a win for everybody.

Im really suprised nobody has recommended Saiddit... however, reddit admins went and setup accounts there early on...

Re: Lemmy stats (users, posts, nodes, comments)

#32

A bit off topic, but why does it seem like not a single page on this site uses caching of any sort? Every time it’s brought up and I click into it I’m met with minute(s) long loading screens. Surely they aren’t pulling all of these stats from every node every single page load right?

I don’t think this is off topic, because this is a common theme across all of Lemmy. Not necessarily no caching, but abysmal performance across the board.

As much as I want the project to succeed it’s unusable currently, and with more Reddit communities coming back from the blackout, their opportunity to claim the user base in the long run is already passed.

The stats over the last month are impressive (if you can get them to load), but it’s going to be a flash in the pan if they can’t make the website function, and I fear the ship has already left the dock.

Re: Lemmy stats (users, posts, nodes, comments)

#33
post #6

Earlier quoted context omitted.

I'm blanking out my 10 year old account (after requesting my data dump) sometime around the first if they don't do something to reverse course.

I requested GDPR exports for my accounts 8 days ago, nothing turned up yet. I have shreddit lined up to run as soon as I get my zips.

Does one have to be an EU citizen to request via GDRP?

If so - I made the offer to sell my accounts to any GDRP person for $1 such that I can make those requests for data (ill pay more than $1, its just to make it an actual transaction)

I have 17 years of content contributed to reddit... and I'd like to kill it all.

Re: Lemmy stats (users, posts, nodes, comments)

#34
post #22

Well if we hugged the stats page to death, as it appears to me, some of us will need more context. Like what is Lemmy?

Lemmy, like kbin or mastodon, is a frontend to federated social media, ie ActivityPub. Lemmy is made to feel more or less like Reddit, while Mastodon is made to feel more or less like Twitter, and kbin is sort of in the middle and feels oriented to news aggregation, but they all interoperate over ActivityPub.

"Federated" means someone can pop up an instance, and even if the server isn't hosting any content, it can act your "view" into the fediverse.

Re: Lemmy stats (users, posts, nodes, comments)

#35
post #12

~277k users, up from ~51k on June 1 319 nodes, up from 84 on June 1 Sure, this is nothing compared to Reddit's userbase, but we'll see in a couple weeks how big this will get.

It doesn't really matter if lemmy kills reddit. If a new community grows and survives after this whole thing, that's a win for everybody.

Exactly. To me, all this talk of whether Lemmy will replace Reddit is a distraction. 90% of what is on Reddit is (in my opinion) crap, I would be happy if it stayed on Reddit or went somewhere else entirely. All I want to know is whether Lemmy can reach a critical mass where there is enough going on there that it's worth visiting.

Re: Lemmy stats (users, posts, nodes, comments)

#36

A bit off topic, but why does it seem like not a single page on this site uses caching of any sort? Every time it’s brought up and I click into it I’m met with minute(s) long loading screens. Surely they aren’t pulling all of these stats from every node every single page load right?

I don’t think this is off topic, because this is a common theme across all of Lemmy. Not necessarily no caching, but abysmal performance across the board. As much as I want the project to succeed it’s unusable currently, and with more Reddit communities coming back from the blackout, their opportunity to claim the user base in the long run is already passed. The stats over the last month are impressive (if you can ge…

Don't have a link now but as I understand it the main problem is they were using websockets and it didn't scale to so many users. So they're switching to rest api calls and that should fix a lot of the issues. But it's a pretty big switch they've been working hard on.

Re: Lemmy stats (users, posts, nodes, comments)

#37

A bit off topic, but why does it seem like not a single page on this site uses caching of any sort? Every time it’s brought up and I click into it I’m met with minute(s) long loading screens. Surely they aren’t pulling all of these stats from every node every single page load right?

I don’t think this is off topic, because this is a common theme across all of Lemmy. Not necessarily no caching, but abysmal performance across the board. As much as I want the project to succeed it’s unusable currently, and with more Reddit communities coming back from the blackout, their opportunity to claim the user base in the long run is already passed. The stats over the last month are impressive (if you can ge…

To be fair, load testing is hard to get right. Plenty of well resourced and smart teams screw it up, and have outages due to scaling issues.

And the team behind Lemmy didn't exactly get much notice either, so they might not have even tried to get stuff to scale well.

Re: Lemmy stats (users, posts, nodes, comments)

#38

A bit off topic, but why does it seem like not a single page on this site uses caching of any sort? Every time it’s brought up and I click into it I’m met with minute(s) long loading screens. Surely they aren’t pulling all of these stats from every node every single page load right?

I don’t think this is off topic, because this is a common theme across all of Lemmy. Not necessarily no caching, but abysmal performance across the board. As much as I want the project to succeed it’s unusable currently, and with more Reddit communities coming back from the blackout, their opportunity to claim the user base in the long run is already passed. The stats over the last month are impressive (if you can ge…

To be fair, load testing is hard to get right. Plenty of well resourced and smart teams screw it up, and have outages due to scaling issues.

And the handful of unpaid developers behind Lemmy didn't exactly get much notice either, so they might not have even tried to get stuff to scale well.

Re: Lemmy stats (users, posts, nodes, comments)

#39

Earlier quoted context omitted.

I don’t think this is off topic, because this is a common theme across all of Lemmy. Not necessarily no caching, but abysmal performance across the board. As much as I want the project to succeed it’s unusable currently, and with more Reddit communities coming back from the blackout, their opportunity to claim the user base in the long run is already passed. The stats over the last month are impressive (if you can ge…

To be fair, load testing is hard to get right. Plenty of well resourced and smart teams screw it up, and have outages due to scaling issues. And the team behind Lemmy didn't exactly get much notice either, so they might not have even tried to get stuff to scale well.

Exactly! And also keep in mind that all of this is open source created by volunteers like you and me in their free time. Imagine you and me working on a side project like this during weekends. We will probably be focusing on implementing the protocol right, fixing all those rendering and mundane CSS issues, making sure the login and session management does not have security holes. Essentially get all the functional stuff right. And one day Reddit makes some crazy announcement which drives hoardes of people to our little project. Pretty sure we'll not be prepared enough to deal with scaling issues due to the sudden influx of new users.

Re: Lemmy stats (users, posts, nodes, comments)

#40
post #39

Earlier quoted context omitted.

To be fair, load testing is hard to get right. Plenty of well resourced and smart teams screw it up, and have outages due to scaling issues. And the team behind Lemmy didn't exactly get much notice either, so they might not have even tried to get stuff to scale well.

Exactly! And also keep in mind that all of this is open source created by volunteers like you and me in their free time. Imagine you and me working on a side project like this during weekends. We will probably be focusing on implementing the protocol right, fixing all those rendering and mundane CSS issues, making sure the login and session management does not have security holes. Essentially get all the functional s…

All of what you’re saying is correct but so is what the OP said.

It’s very difficult for a volunteer run operation to scale up at short notice. The same time Lemmy has to if it wants to capture disaffected Reddit users.

Post reply on HN