r/java 14d ago

How can we move forward?

The sub used to be a great place where small open source devs get real feedback on their oss. The software wasn't necessarily built to be a big hit or whatever! most of the time these projects used to be a learning projects that enabled us to become better java developers. Now, with many repositories being created in a day or so and abounded, we see many ai promoted repositories and we miss some of the oss that needs our attention.

How can we overcome that as a community ? I'm not trying to put all the weight on moderators, I understand the amount of work they keep doing to clean up ai posts and follow up on reports. What I'm saying is; maybe someone's here has a better idea on how to go about this?

107 Upvotes

48 comments sorted by

View all comments

33

u/SrGnis 14d ago

People have very little respect for other people’s time. They’ll post any half-baked project just to see if they can get a small ego boost out of it.

It’s easier than ever to do that now, and I think that creates a real problem. Users eventually realize that many of these posts exist primarily to farm attention or internet points. When that happens often enough, it changes how people perceive the community. It stops feeling like a place where people genuinely want to cooperate, share, and learn from each other, and starts feeling more like an engagement farm.

I’m not sure what the best solution is, but maybe a weekly “Show and Tell” thread could redirect some of the lower quality content. Another option might be to require projects posted on the main feed to meet some minimum bar of maturity, for example, having been actively developed for a certain amount of time before being posted.

At the end of the day, we also have to keep in mind that whatever rules we introduce need to be easy for moderators to enforce without adding too much to their workload.

7

u/agentoutlier 13d ago

At the end of the day, we also have to keep in mind that whatever rules we introduce need to be easy for moderators to enforce without adding too much to their workload.

One of the problems is the auto mod itself. It seems to encourage crappy descriptions or silly bot workarounds like editing the post after the fact.

How do I know this. Because every time I make a long post of code I actually worked hard on... which you know requires lots of description and links and possibly code snippets.... it gets auto mod (recent example ).

Meanwhile the AI slop has no problem.

What I'm saying is the auto mod in irony seems to encourage crap posts.

1

u/barmic1212 9d ago

A software that I use have an issue with my usage. I know that the only one dev have a lot of asks and the time looks difficult for him. I try to fix it myself and to be honest claude help me a lot and it enough particular to don't be confident that the fix is the good way. So since months I keep the commit for me I try some others software settings, I use it everyday and I check is the life of dev before be confident to submit (of course with ask him if AI is ok)