nutomic

You can already block federation with certain instances. And the only ones who can upload images are users that are locally registered to your instance.

Really?. Does this relate? Not related, not a feature request. I mean there probably wasn’t a specific feature request for the exact specific matter at hand. But plenty of noise and discussion around something needing to help address the problem.

All of these are resolved, what more do you expect?

I personally got kicked out of and banned on everything Lemmy Matrix related for daring to challenge you and and Dessalines. You are petty AF.

I dont remember the exact details but the reason you got banned was because you actively attacked a Lemmy maintainer. Someone who actually works on the project to make it better, as opposed to you who only complains. Such a ban is well deserved.

Anyway Im done talking to you. Please switch Beehaw away from Lemmy and use another platform so you can stop bothering us.

I remember Beehaw wanted to switch away from Lemmy to another platform months ago. I encourage you to do that and point your demands and entitlement at someone else. We have enough users who actually appreciate our work.

No we arent getting paid, there is no employment contract with anyone. We are working on Lemmy in our own time, and receiving donations from some users. It may seem like a minor difference but its important, because donations dont include any obligation to give something specific in return, or prioritize specific tasks.

There is a lot of misleading information in this post.

Something that I notice said consistently by those who have little experience in Lemmy admin spaces is “why not just contribute then?”And the answer people try. And this happens. This unfortunately leads into the next point that is the developer teams behavior.

Dessalines and I had some discussion whether the linked issue should be closed or not. Anyway we decided to leave it open in the end. Then some weeks later a user came along and made a completely offtopic complaint that this decision making process is somehow wrong. I admit that I overreacted by giving a temporary ban for this, but mistakes happen and its completely disingenious to spin this as some sort of general toxic behaviour from our side.

There is a fundamental lack of confidence amongst a majority of Lemmy instance admins towards the lead developers of Lemmy.

This is your opinion and I doubt it is as widespread as you think.

Another aspect of this is that the Lemmy devs run two instances: lemmy.ml & lemmygrad.ml

What makes you believe this? I can only speak for myself, and I am not involved with lemmygrad in any way.

The biggest piece that broke all confidence in the Lemmy developers amongst many admins including myself is that during the CSAM spam attacks there was complete radio silence. The developers made no statement on the matter. And when Github requests were made to try and propose ideas about how to fix what happened, the developers explicitly stated they didn’t have time to focus on that. No dialogue.

Correct the CSAM wave was handled by admins on their own. As far as I remember there were no specific feature requests that would have helped in this regard, and anyway they would have taken too long to implement and publish.

As well, when a post was made about Sublinks (A project I will touch a bit more on, and am involved in due to the reasons I have highlighted above) the comments that were made by Lemmy’s lead developers were extremely petty. This lessens peoples confidence in your project, not improves it.

Why do you consider it petty? Its a fact that jgrim never opened any issue for the features he wanted, not did he attempt to contribute with a pull request. Its also true that it took multiple years of fulltime work to get Lemmy ready for production, and I dont see how Sublinks can be any faster when it has only volunteer contributors. That doesnt mean I wish for Sublinks to fail, in fact I hope it will be successful so that admins and users have more choices available, and to improve resilience through independent codebases and development teams.

Generally you seem to have an extremely entitled attitude. Lemmy is an open source project that is provided for free. I would also love to fix all the problems that users report, and implement all those features. But unlike Reddit we are not a billion dollar company with thousands of employees. We are just two individuals funded by donations and working from our homes. There is only a limited number of hours in each day and only so much work we can finish in that time. If you are unhappy with Lemmy then by all means switch to a different platform, because we dont get any direct benefit from having more users.

It's already largely resolved through the feature to export/import user profile.

No schade-throwing, but I know how much effort it took to get Lemmy ready for production. Namely multiple years of fulltime work. Sublinks seems to have only volunteer contributors, so it will likely take even more time.

Or these people could learn Rust and contribute to the existing project. That would save years of duplicated effort. I personally knew zero Rust before starting to contribute to Lemmy, its really not that hard to learn.

I was a Java developer before starting to contribute to Lemmy. Didnt know anything about Rust, just wrote code and resolved compiler errors until things worked. Rust is definitely not as hard to learn as some people think.

Not true. And if you miss a feature why dont you help implementing it instead of complaining? Thats what open source is all about.

Thanks for the suggestions!

Create an ARCHITECTURE.md document explaining the overall architecture and different components of Lemmy. This would help new contributors quickly familiarize themselves with the codebase.

The documentation has some info about the architecture as well as how to start contributing. Is there anything particular missing, or do people not find these docs?

Publish a public roadmap with milestones and release plans. This gets people excited about the project’s direction and motivates them to contribute.

As mentioned in the other comment, we will have a public roadmap once the NLnet milestones are finalized. Other than that the issues are up for grabs for anyone, so Im not sure what sense it would make to give them priorities.

Nightly builds enable contributors to test upcoming changes, offer feedback, stay actively involved in the project’s progress, iterate quickly on improvements, and foster a culture of continuous improvement.

These are available as :dev Docker images, and deployed to test servers at enterprise.lemmy.ml etc. Maybe this should be documented somewhere to let people know?

Implement a bounty system for critical or challenging issues to incentivize contributions. Some people who don’t want to contribute with a monthly subscription may prefer this kind of contribution.

Bounty systems dont work well in my experience. Usually the reward is too low to pay an actual dev salary, and then its still a hassle to get the money into your bank account. Plus there is no gurantee to get paid for your work, its always possible that someone else submits a solution just before you finish yours.

Create project swag (stickers, t-shirts, etc.) and distribute it to active contributors as a token of appreciation.

Good idea, though we dont really have the funds to pay for that. It was also suggested to sell swag to earn money for Lemmy, but havent gotten around to that yet. Do you by chance any good company to produce and sell this?

Institute a “Lemmy contributor mentorship or apprenticeship” program where experienced developers formally take up 1-2 promising new contributors under their wing.

Well if anyone opens a pull request we give feedback as part of the review process. And if anyone has questions we also answer them in the issue tracker or on Matrix. But in practice there seems to be little demand in this regard.

Live or recorded screencasts solving issues, similar to mentorships but instead of one-on-one it allows more people to feel engaged in the development process, and provide feedback in the case of live streams.

That seems to get more into entertainment, not what we want to do.

Host discussions about issues on Lemmy itself, as suggested in the blog post below. The voting and threads with nested comments make it easier to have productive conversations compared to GitHub. The community is here so you’ll get more contributions right away in the form of ideas and feedback.

We do have biweekly dev updates which are somewhat related. But discussing individual issues here would likely duplicate discussions from Github issues.

Yes Bevy has a big advantage because its a library, so everyone who uses it is a developer and is able to fix minor issues. In case of Lemmy only a small fraction of users are developers, and even less know Rust. I watched the video, but its not easy to take concrete suggestions and apply them to Lemmy. Maybe the community reviews for PRs would be a good idea to get people familiar with the codebase. It also mentions using a project board so we should consider that. Though Im not sure how to select issues for each milestone because again, everything is up for grabs.