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.
A single Docker container is not possible because Lemmy requires multiple different images (postgres, pict-rs, lemmy-ui, lemmy). Supporting two different databases would be too much effort. In the end Lemmy is optimized for large instances with hundreds or thousands of users, not for tiny instances. So more difficult installation is not a major concern.
Im glad its finally working, took a long time. Welcome to the federation!
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?
That doesnt change anything because they still need to be stored on the server.
Every instance automatically archives content from other instances that it federates with (though this doesnt include images). An archive sounds like a good idea, but we certainly dont have the capacity to take on another project. It would have to be done by someone from the community.
As an admin you can remove a remote community, then it shouldnt federate anymore. Though admittedly this isnt very intuitive.
So its a bash script which manages the docker-compose install for you? I really wouldnt want to maintain almost 2000 lines of bash. Plus such a script has extra complexity and has a chance to break. I think it makes more sense to rely on standard, widespread tools like docker-compose which you can find documentation for all over the internet. Though if you prefer to use that installation method over the official one, theres nothing wrong with it.
It doesnt really matter what you want. The software is open source so anyone can use the software freely. No way to prevent it.