We're the creators of Lemmy, Ask Us Anything. *Starts Monday, 7 Aug, 1500 CEST*

Dessalines@lemmy.mlmod to Announcements@lemmy.ml – 1373 points –

This is an opportunity for any users, server admins, or interested third parties to ask anything they'd like to @nutomic@lemmy.ml and I about Lemmy. This includes its development and future, as well as wider issues relevant to the social media landscape today.

Note: This will be the thread tmrw, so you can use this thread to ask and vote on questions beforehand.

Original Announcement thread

702

You are viewing a single comment
View all comments

Thanks for both of your work on Lemmy, join-lemmy, lemmy-ui and Jerboa.

  1. Can you tell us about any upcoming major features/issue resolutions in development currently, if there are any?
  2. Will Lemmy have any form of cross-instance community/post grouping, similar to multi-reddits, hashtags, "alliances" or categories? Although some Lemmy apps have implemented something along those lines, it could be more fully-implemented in the official backend/frontend. I've been thinking Lemmy has desparately needed it to help solve some of the fragmentation problems across instances. It would also help avoid one instance necessarily having all the content, ballooning in both running costs and control.
  1. The best way is to look at the open PRs on each repo, to see the things that are being worked on / fixed.
  2. We have an open issue for community collections, but its not being worked on currently. We have cross_posts come back through the GetPost endpoint, to see where else specific posts have been posted to.

The fragmentation issues I've addressed here.

Alright thanks for the answers! I've looked through them, and maybe I was looking for more of what you thought personally of what major features you had in mind. Rather, it sounds like (but don't let me put words in your month) you're more focused on just keeping the overall work together and stable. I can respect that.

As far as some longer-term goals, I posted this elsewhere, but some are:

  • Performance improvements (DB, federation code)
  • Creating a better onboarding site (joinlemmy)
  • Stabilizing the API
  • Becoming fully funded by donations, and growing our dev co-op.
  • Lots of code maintenance
  • Notifications (Unified push)
  • Better sorting to push content from smaller communities (a best sort)
  • A better web UI written in rust (lemmy-ui-leptos)