Announcements

Its a problem, and at the same time a feature. For example, you can have two communities named !news, that pertain to completely different topics based on their instance:

• https://startrek.website/c/news
• https://starwars.website/c/news

This also isn't unique to lemmy, since reddit too had tons of duplicate communities for the same topics.

Just like on reddit, the network effect will run its course here: unavoidably there will be a lot of cross-posting on duplicated communities, until people center around their favorites, based on quality of content.

There are a few tools out there too, like https://lemmyverse.net/communities , that can help people find communities to subscribe to.

Overall tho, I'm against the concept of "combining / merging communities" that are run on different sites by different people. These should be curated and controlled by the people who created them.

The instance list is fine as is. Think about it like this: do you want racists to join a single instance so they are all in one place? Or do you want them to spread across all different instances, causing moderation problems everywhere?

o7 comrade. I'm glad I can help out in any way.

Lemmy-ui supports SEO, and also has opengraph tags. If there's anything else needs to be added, we're open to PRs.

Side note: For me personally, as @[email protected] suggested, SEO shouldn't be a focus. SEO is such a gamed system, catering to a few giant search companies, and results are increasingly becoming unusable, especially in the past few years. I can barely find the things I want to search for, and almost always have better luck using internal sites search engines. So I'd rather focus on improving lemmy's search capabalities and filtering, than catering to google.

Alright second part:

• The biggest problem is definitely that there are too many things to do, but only the two of us working on it fulltime. The day only has so many hours and its impossible to keep up with everything. Thats why community contributions are really important.
• The amount of contributors is very high compared to a few months ago, its not easy to keep up with all the pull requests. Its going to take some time for processes to adjust to the new scale, and for new contributors to learn how everything works.
• This is a question for @[email protected]
• People work on whatever they are passionate about. Generally that works quite well.
• I am only working on Lemmy and thats already a lot. So another question for @[email protected]

Wow lots of questions here.

• Im doing well, its exciting to know that so many people like the software Ive worked on for the last years. The first month after the migration was really stressful, but by now its calmed down a lot. Plus there are many contributors now which are helping a lot.
• Unfortunately the user donations are just barely enough to pay our salaries, by my calculations the income from Liberapay, Patreon and Open Collective is around 4000 USD per month. Luckily we still have some NLnet funding left, and should be able to work on those milestones now that things have calmed down. I hope the user donations will increase so that they can pay us proper salaries. Maybe even hire additional people, but that seems very optimistic now. It would also be good if we could find other funding sources besides NLnet, as its not clear if they will fund us another year.
• I think the "breaking bugs" were really minor considering how we had to constantly rush out performance and security fixes. This should get better as we dont need to make emergency fixes, and have more time to let the community test release candidates before making the full release.
• Supporting downgrades means that someone has to test them and report/fix problems. We dont have time for that, but feel free to do it.
• Like I said, our recent releases had urgent performance/security fixes so we didnt have enough time for testing. We also didnt find out about these problems until later. Part of the problem is that keeping up with issues is almost a full-time job on its own, so I rarely read them anymore. If you see something important reported, do let me know.
• No concrete plans, but I definitely think that admins are the main actors who should have a voice in development. Its impossible for us to listen to all the individual users, because there are too many and they often dont have the necessary technical knowledge. If you have some ideas how to facilitate communication between devs and admins, let me know.

Are we almost done? Nope, only halfway. Will answer the second half a bit later.

Neither @[email protected] or I are too familiar with the GDPR, so we don't know everything that it requires. Lemmy doesn't do any logging of IPs or other sensitive info, but of course instance runners could be doing their own logging / metrics via their webservers.

We have a Legal section under admin settings, that's an optional markdown field, that can probably be used for it. We'd need someone with GDPR expertise though to help put things together. Lemmy is international software, not european-specific, so we have to keep that in mind when supporting GDPR.

Im not a lawyer so I dont know about GDPR. Do you know how similar platforms such as Mastodon handle it?

If lemmy is working as intended (many small, connected servers), hosting costs should be small: like < $10 USD / month. (images are another issue, but I'll answer that in other comments).

Of course we don't plan on adding any monetization directly into lemmy or its UI, including ads, or required payments. Right now at least the best way is to put donation links in your site sidebar.

I dont follow /c/worldnews so I dont see much of that. Also hexbear is federating now, so it might easily swing back the other way again.

People reporting those instances / users, then admins can add them to the blocklist, or ban them and remove their content.