I opened an issue about it: https://github.com/LemmyNet/lemmy-ui/issues/2264

The change to cursor is intentional, it improves server performance: https://github.com/LemmyNet/lemmy/pull/3872

3 and 4 are most likely caused by problems with server-side rendering.

Images were temporarily broken due to authentication problems, but thats fixed now. If you encounter problems in apps, please them to the developers so they can fix them.

Please report such problems to the developers so they can fix them.

What a shame. Luckily the numbers are very small, I hope it doesn’t increase in the future.

You can use the lemmy-stats-crawler (or part of the code) to get a list of instances. Then use endpoints /api/v3/post/list and /api/v3/comment/list to retrieve the content.

You can run git submodule update, then it will pull the same translations as specified in the lemmy repo. Or run git submodule update --remote, then it will pull the latest commit from lemmy-translations.

Its not intentionally hard. If you see a way to simplify it, pull requests are always welcome. But running multiple services in a single docker container is generally a bad idea.

And then we should block lemmygrad, lemmy.world, hexbear and hundreds of other instances? Thats not gonna happen. If you want to block instances, do that on the beehaw side.

Federation, because now there is no going back now. Just kidding

You can make an issue or pull request.

I had zero experience with Rust before. Writing code for Lemmy was how I learned it. Didnt read any docs or books, just writing code and searching around how to solve my concrete problems. That approach works very well for me. Before that I was working on Android with Java, Kotlin and some Scala. Also used all kinds of different languages before that, PHP, C++, Delphi, Python, C and assembly in university (ugh)…

Thats good to hear, Im glad you like it!

There are plenty of other instance lists across the internet. So its not even a real solution for your theoretical problem.

Thats fine, they can provide their own list of instances where users can choose from.

It doesnt really matter what you want. The software is open source so anyone can use the software freely. No way to prevent it.

Im from Germany and studied computer science. Was always very interested in open source and decentralized software. Worked in a couple different companies, but was never happy making profit for someone else. Luckily I found Lemmy shortly after Dessalines started the project, and put a lot of work into it. Then we found the NLnet funding which allowed us to work fulltime on the project.

• Private communities would be good to have, problem is that they will require changes to all parts of the code which makes it very complex to implement.
• I certainly wouldnt have to rewrite the federation code so often if I already knew how to do it.

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 @dessalines@lemmy.ml
• 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 @dessalines@lemmy.ml

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.