overview for fragmentcity

Admins, we're about to have a really bad SPAM problem when Lemmy removes captcha support in v.0.18 - You ALL have a responsibility to communicate back to lemmy devs to try to stop it. in c/technology@beehaw.org

[–] fragmentcity@lemm.ee 1 points 1 year ago

Right but to your other point, the admins who don't fork will send you spam.

Admins, we're about to have a really bad SPAM problem when Lemmy removes captcha support in v.0.18 - You ALL have a responsibility to communicate back to lemmy devs to try to stop it. in c/technology@beehaw.org

[–] fragmentcity@lemm.ee 7 points 1 year ago (3 children)

Also, even if I don’t upgrade to v0.18, I have to live in a fediverse that have other instances that WILL, and they might pose a problem with increased spam.

A fork avoids this problem how?

I disagree, once your open source project “sprouts wings” you enter an unspoken power battle. If enough of the community disagrees with something the chance of a successful fork grows. Once a project is forked away, you no longer have any control at all.

Who's writing the code for the fork? If you see them, can you ask them to just submit the PR that the devs said they'll approve?

Admins, we're about to have a really bad SPAM problem when Lemmy removes captcha support in v.0.18 - You ALL have a responsibility to communicate back to lemmy devs to try to stop it. in c/technology@beehaw.org

[–] fragmentcity@lemm.ee 21 points 1 year ago (12 children)

Despite what you're implying, the devs have no duty to fix admin-reported problems using admin-dictated solutions.

They have already said they would accept a PR adding support for captchas. Someone will undoubtedly do this before long.

Until then, why the urgency? What is it that's preventing you from keeping your instance on 0.17?

AI models feeding on AI data will lead to 'model collapse', researchers say in c/technology@beehaw.org

[–] fragmentcity@lemm.ee 5 points 1 year ago (2 children)

So basically we are sitting in a room.