I can replace them if you can suggest better alternatives. Anyway Lemmy users seem to be older than Reddit users, and those who have spare money to donate should know these normal financial terms.

I rewrote the text again, have a look and let me know what you think. Also made some more design changes the donation page.

“Help Design Lemmy” sounds good, thanks for the suggestion. I looked around for some info about A/B testing but it seems relatively complicated to setup. Do you have any tools to suggest for that? And I can see what you mean about the text sounding unsure. What do you think about this one?

We provide Lemmy as free and open source platform without any tracking or advertising, and work every day to improve it. Yet we also need money to pay our bills and provide for our families. Only 2% of Lemmy users donate, so we need your donation to keep this model working. Thank you for helping to create a new form of social media.

AGPL specifies that everything is provided without liability or warranty, so I dont see how anyone could have reason to sue. Besides Lemmy is not a company, if anything a nonprofit would make sense.

Hmm that may be true, but now its already implemented like this, and this would require a breaking change. So better to leave it as is. Anyway the logic should not be changed.

That is true, but not so easy to do. To make donation pages like those in your link would require setting up some kind of nonprofit and directly handling credit card payments with some payment processor, and probably various legal requirements. By relying on existing donation platforms we have much less hassle.

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.