Lemmy Project Priorities Observations

5 readers

1 users here now

I've raised my voice loudly on meta communities, github, and created new [email protected] and [email protected] communities.

I feel like the performance problems are being ignored for over 30 days when there are a half-dozen solutions that could be coded in 5 to 10 hours of labor by one person.

I've been developing client/server messaging apps professionally since 1984, and I firmly believe that Lemmy is currently suffering from a lack of testing by the developers and lack of concern for data loss. A basic e-mail MTA in 1993 would send a "did not deliver" message back to message sender, but Lemmy just drops delivery and there is no mention of this in the release notes//introduction on GitHub. I also find that the Lemmy developers do not like to "eat their own dog food" and actually use Lemmy's communities to discuss the ongoing development and priorities of Lemmy coding. They are not testing the code and sampling the data very much, and I am posting here, using Lemmy code, as part of my personal testing! I spent over 100 hours in June 2023 testing Lemmy technical problems, especially with performance and lost data delivery.

I'll toss it into this echo chamber.

founded 1 year ago

MODERATORS

[email protected]

A Priority: new sort orders / Multi-community features (bulletintree.com)

submitted 1 year ago by [email protected] to c/[email protected]

8 comments fedilink hide all child comments

Ok, taking a total fresh approach based on all the months I've been reading people's suggestions and [email protected] kind of things....

All / All Remote / Local / Remote Specific-Isntance

I think server operators should at minimum want the ability to view Remote-only, and even per-instance. Further, I think proxy of API to a community should be something to head towards... where a Lemmy API call can be forwarded as an API call on another Lemmy server for a specific community.

Small, Medium, Large, Trending, Featured Community

Some stock multi-community lists, some of which are dynamically generated like Small / Medium / Large based on number of active posts, users, or other tunable parameters. Encourage people to engage in topics that they normally would not see...

Multi-community sharing

I think foundation is that it should use words and not numbers. Right now, the entire Lemmy system is built upon using localized index numbers for community. Even if it just becomes a JSON blob to throw into PostgreSQL and recall by name...

Maybe have them like communities. And people can subscribe/unsubscribe to a specific list. And the list can have moderators who regulate it (editors). And an option to clone a list to new name.

/mc/ multi-community, name. And no ID numbers. A Trigger or something would have to build the ID numbers in the background.

And a browser of these, much like communities are browsed... and maybe even voting on them. Lemmy doesn't have voting on communities - subscribe alone - but sometimes you don't want to subscribe because they have too much content - but you would still vote for it or recommend it.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago

These are the kind of things I think I need to start experimenting with as we nail down performance-concerned compromises.

I really wanted a design of filtering posts with LIMIT 1000 per-community, as in the back of my mind browsing Small or Medium community is really at the heart of Lemmy as opposed to Active / Hot kind of browsing that way favors popularity (memes, etc).