Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lemmy stats (users, posts, nodes, comments)

the-federation.info

Post reply on HN
Print view View original

51–60 of 104 posts

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

#51

Post by balder1991 »

distcs wrote: post #39
londons_explore wrote: post #37

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…

Just some more info, they were working on Lemmy full time.

Source: https://join-lemmy.org/news/2023-06-17_-_Update_from_Lemmy_a...

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

#52

Post by camel-cdr »

seanalltogether wrote: post #18

I keep giving lemmy a try and I couldn't figure out what was bugging so much about browsing it. I finally realized I'm only seeing about 7 posts per window on lemmy as opposed to 12 on reddit. And now I'm realizing the content box is only 800px wide so comments feel really constrained. This seems like a weird style choice?

I'm not good enough with css, but I pretty sure if you figure out a more compact design, lemmy-ui will very likely include it.

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

#53

Post by shagie »

ehutch79 wrote: post #48
raybb wrote: post #36

Earlier quoted context omitted.

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.

Shouldn't rest (or graphql) be the default? with realtime updates being a progressive enhancement?

Note that what amounts to a single page app with all the links rendered after fetching some data from a service isn't going to be something that can be indexed by a search engine.

A google search for site:lemmy.ml with it rendered this way will never result in any data.

This may or may not be a good thing since it isn't necessarily assured that the data is stored for extended periods of time (compare: https://masto.host/mastodon-content-retention-settings/ ).

Part of the value that people have ascribed to Reddit is being able to do searches for a product review and limit it to just pages served by reddit. Lemmy appears to be ephemeral and not searchable.

Discussing the current Star Trek SNW episode may be ok, but reading a discussion from a few years ago about Emissary on DS9 ( https://www.google.com/search?q=deep+space+nine+emissary+sit... ) is something that isn't going to be doable.

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

#54

Post by ehutch79 »

rdschouw wrote: post #19
juujian wrote: post #11

Could Lemmy have something akin to r/all? I have always used Reddit more to discover new contents, trends, and communities then to check up on communities i already know (with a few exceptions).

You mean this? https://lemmy.world/home/data_type/Post/listing_type/All/sor...

Very memorable.

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

#55

Post by camel-cdr »

juujian wrote: post #11

Could Lemmy have something akin to r/all? I have always used Reddit more to discover new contents, trends, and communities then to check up on communities i already know (with a few exceptions).

You filter through all, local and subscribed community posts on your statepage. The sorting in general needs a bit of work though.

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

#56

Post by shagie »

londons_explore wrote: post #38
taywrobel wrote: post #32

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 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.

> unpaid developers behind Lemmy

They're paid, though they're having trouble scaling to the support issues.

https://join-lemmy.org/news/2023-06-17_-_Update_from_Lemmy_a...

> ...

> For the past three years dessalines and I have been funded to work on Lemmy full-time by generous support from the NLnet foundation. These donations are paid out when we implement certain new features. But now we are busy answering questions, reviewing pull requests and urgentlyfixing problems. That means we are unable to work on the milestones agreed with NLnet, and won’t receive payments from them. We are increasingly reliant on user donations to pay our bills. These donations currently add up to 1500 Euros per month, which is not even enough to pay minimum wage for the two of us. Hopefully more users can consider donating, so that we can put our full attention to making Lemmy better for everyone, and possibly add more developers to our worker co-op in the future.

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

#57

Post by ehutch79 »

shagie wrote: post #53
ehutch79 wrote: post #48

Earlier quoted context omitted.

Shouldn't rest (or graphql) be the default? with realtime updates being a progressive enhancement?

Note that what amounts to a single page app with all the links rendered after fetching some data from a service isn't going to be something that can be indexed by a search engine. A google search for site:lemmy.ml with it rendered this way will never result in any data. This may or may not be a good thing since it isn't necessarily assured that the data is stored for extended periods of time (compare: https://masto.h…

I'm not sure what any of that has to do with using websockets by default vs traditional rest data fetching?

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

#58

Post by rkangel »

bogwog wrote: post #12
Paul-Craft wrote: post #2

~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.

Yes. I spent last week hoping that everyone from Reddit moves to Lemmy, but I realised that I don't need Reddit to die, I just need Lemmy to be successful enough. There is a critical mass of people needed to sustain a set of useful sublemmys, but that number is a tiny fraction of Reddit.

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

#59

Post by randomdata »

VWWHFSfQ wrote: post #17
stemlord wrote: post #5

Would like to see reddit stats

I'm sure Reddit is prepared for a small contraction in their active userbase while also seeing a significant increase in monetizability of the remaining users.

A small number of users provide what attracts the rest of the userbase. It will be interesting to see which small group leaves.

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

#60

Post by thatwasunusual »

londons_explore wrote: post #37
taywrobel wrote: post #32

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.

> To be fair, load testing is hard to get right.

Load _testing_ is easy.

The problem is to handle load, and cache invalidation is _extremely_ hard.

Post reply on HN