Lemmy Project Priorities Observations
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.
view the rest of the comments
Pros and cons
Community
con, does not have a community subscribe and block list
pro, has moderators list that spans instances
Person
con, you can't login to a person account on a remote instance. So that's less like a community
con, no moderator list for a person
pro, has all the ability to build list of communities to whitelist or blacklist
pro, can also blacklist persons (which I guess a community can too, ban list)
More observations
A Person who can login is a local user, and there is an alternate table for that.
A community does have a home instance as does a Person. So it does matter where created. [email protected]
non-Lemmy federated things get confused by communities name clashing with persons. Which even email systems I have used with public folders assigning an email address, it's basically treated like a person. Lemmy allows a@person and a@community, do we follow that convention, a@multipass ?