Day 65 - the lemmy audience, the authors of posts and comments, the voters

RoundSparrow to Lemmy Project Priorities Observations@bulletintree.com · 1 year ago

Hate of Twitter, hate of Reddit seems to have been the primary motivation for many people to join Lemmy.

In the past 2 months, I have seen many people requesting feature in apps to block entire instances of Lemmy or enhance other blocking features.

Bashing on Facebook was often a thing you saw on Reddit, bashing end-users.

Are people largely attracted to this?

I’m mostly just saying it out loud. These trends like what Elon Musk has done to Twitter, or ChatGPT becoming mainstream in 2023 wit all it’s misinformation creation abilities… are happening. Regardless of the anything going on with Lemmy.

ChatGPT is probably the bigger real change. The news/world news on Lemmy isn’t really that different than Reddit from my 60+ days of reading. Same general style of comments, reactions, and flow of postings.

You must log in or # to comment.

Chat

Lemmy Project Priorities Observations@bulletintree.com

lemmy_project_pri@bulletintree.com

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !lemmy_project_pri@bulletintree.com

I’ve raised my voice loudly on meta communities, github, and created new !lemmyperformance@lemmy.ml and !lemmycode@lemmy.ml 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.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

1 user / day
1 user / week
1 user / month
1 user / 6 months
4 local subscribers
98 subscribers
76 Posts
260 Comments
Modlog