The Dev's stubbornness about captchas is a little baffling. Yes, they're not 100% foolproof but they help.
It's like arguing that we shouldn't have locks on or our doors because a skilled lock picker can get past them.
this post was submitted on 23 Jun 2023
115 points (97.5% liked)
Lemmy.World Announcements
29164 readers
42 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world/
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to info@lemmy.world e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email report@lemmy.world (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 2 years ago
MODERATORS
The devs aren't pushing back against captchas, but they're desperately trying to get 0.18 out to resolve a ton of issues. Captchas need to be redone in the code level and no one has done it yet.
someone has done it, there's a PR here: https://github.com/LemmyNet/lemmy/pull/3289
That looks promising, hopefully weโll have an 0.18.1 release later next week
They agreed to add them back. You can read their comments in OPs link
That only happened recently, though. For weeks they were replying to instance admins requests to reinstate captchas with things like "bots have beaten captchas, so they're useless."
What are you talking about? The issue to bring back captchas was only opened 4 days ago!
Captchas were only removed 2 weeks ago, no one spoke up then: https://github.com/LemmyNet/lemmy/issues/2922
The developers have nothing against captchas. They were the ones who originally built and added the feature: https://github.com/LemmyNet/lemmy/pull/1027
load more comments
(2 replies)
load more comments
(1 replies)
I just updated and it gave me an error on jerboa but it still seems to be working fine
load more comments
(2 replies)
Biggest concern for me is the broken auto scrolling/updating. I can't use this site properly as long as the list of topics doesn't stay in place long enough for me to finish reading the headline.
Hopefully after this is fixed I'll start contributing.
Try changing the 1 at the end of the url to 0 as a workaround.
This will go away with dropping websockets
load more comments
(2 replies)
I know these are early-adopter pain points, but I think if Lemmy is really gonna take off, the devs need to get serious about backward compatibility and ensuring backend upgrades don't completely break major instances/clients. IMO switching from websocket to HTTP should have been treated as a breaking change with a new major version release and a more controlled rollout period for this exact reason.
load more comments
(2 replies)
Here is a link to the current state of captcha re-implementation: https://github.com/LemmyNet/lemmy/pull/3289
This request was reopened after it was merged prematurely. You can read the preceding discussion here: https://github.com/LemmyNet/lemmy/pull/3249
Lemmy Devs have agreed to add it back, so I dont thing it will be long.
Thanks for keeping the bots out! I'm still successfully using Jerboa, btw.
load more comments
(6 replies)
ELI5?
there's a couple of points here
- current website is version 0.17.4 (you can check this at the very bottom)
- version 0.18 is ready, but there's no captcha yet (the thing where you have to identify objects on squares, or click a box that'll turn into checkmark)
- without captcha, bot accounts (not real users) can register to the site too easily
- so we're gonna wait for version 0.18.1, the one with captcha active.
- the Jerboa app, the android app for browsing Lemmy has also recently updated, and will only work for Lemmy version 0.18 up, thus it's advised to use another app or just the web for now
note : the site version 0.18 is already out for the main Lemmy instance, which is lemmy.ml, but lemmy.world (where we are now) is gonna wait for version 0.18.1
I'm using Jerboa and everything seems to be working fine. Edit: Jerboa started playing up mainly crashing on opening it. Binned it off and now using Connect
I first thought my Jerboa was fine (despite the popup warning about version), since I could browse a bit without it obviously exploding. But no, it crashes regularly now (closes, no warning or messages).
I don't understand why a Lemmy update would be considered for release that removes security features like captcha support. (Especially during this time of high rates of signups, and well known bot wave in some instances.)
Combined with Jerboa update that needs the Lemmy update, and popularity of instances that need captcha, it's unfortunately causing a mess for many users.
load more comments
(1 replies)
I'm currently using the app called lemmy connect without issues.
Yeah it's not bad, I prefer jerboa (really I'm waiting for sync) but connect works fine
Lemmy.world is running Lemmy version 0.17.4 right now (check the bottom of any Lemmy instance and it'll tell you what version is running). The new version fixes a lot of things, but lemmy.world can't upgrade to that new version yet because it'll be overrun by bot accounts. We have to wait for the next version and skip this update because that has the protections for bot accounts.
For now i made a shortcut on my phone's home screen to this lemmy instance to act as a quasi lemmy client, works pretty well for the time being.
load more comments
(4 replies)
Alternatively to Jerboa, it's possible to use the web site as a contained web-app, using Firefox on Android.
Thanks for showing me this. It worked on chrome too.
load more comments
(1 replies)
Jerboa asks for 0.18 to be installed, but works with 0.17.4 mostly without issues.
load more comments
(1 replies)
Ok so guys, I appreciate the devs of Jerboa for doing what they do, but I am absolutely switching to another app immediately when something else decent shows up.
load more comments
(10 replies)
Appreciate you waiting for the 18.1 upgrade
@ruud@lemmy.world Dodged bullet anyway, v18 2FA doesn't make people confirm that their app is configured correctly by asking for a code, as is tradition. It just gives them their QR/Key and locks them into 2FA immediately. If they botch adding it to their app they are locked out. And I hear the code currently being generated is silently incompatible with Authy, so those people end up SOL even if they do everything right.
https://github.com/LemmyNet/lemmy/issues/3309 / https://github.com/LemmyNet/lemmy/issues/3325
load more comments
(1 replies)
How about temporarily disabling sign ups until 0.18.1? As more apps update to 0.18 it'll be annoying to juggle versions.
Anything stopping new members from signing up is going to hurt the adoption of the platform as a whole.
load more comments
(1 replies)
The release candidates for 0.18 were published at an almost daily basis. I think it's fair to assume .1 won't take forever.
Thank you for the info and keeping on top of this :) have a nice weekend
I tried that app over a week ago (F-Droid) and it just crashed 5 times just me trying to read the refugee welcome message.
Now that my beehaw account got approved a few days ago, I thought I give it a try again to use it with the app (Play Store), but now it crashes as soon as I start it while it loads its changelog message.
Hopefully one of the other 9 clients is going to have something more stable to offer than this.
If you are logged in you can just update Jerboa to v0.0.35 and you'll get a message saying that the app works better with Lemmy v0.18 but it still works.
If you are not logged in, then use Jerboa v0.0.34 to log in and then update to v0.0.35
load more comments
(1 replies)
view more: next โบ