I really appreciate the work that you’re doing but…

Captchas are not available in this version, as they need to be reimplemented in a different way. They will be back in 0.18.1, so wait with upgrading if you rely on them.

What the hell? Another bad default where newbies will continue to launch instances attracting 10k+ bot signups per day and new users will keep getting disgusted by Lemmy if they land on one of those spammy instances. Making captchas a default should have been a priority and I’m sure no one would have complained if the 0.18 release was postponed to make that happen.

permalink
report
reply
0 points

I definitely would’ve… it was basically impossible to subscribe to communities on lemmy.world and lemmy.ml from smaller instances before 0.18.0, and after lemmy.ml updated that’s no longer an issue.

permalink
report
parent
reply
16 points

The feed desperately needed a fix, so I’m glad they pushed it out. But agreed, they should be prioritizing methods to reduce spam and bots in the next release, even if they need to push out a relatively feature-sparse version first

permalink
report
parent
reply
5 points
*

I was tracking the Race for Captchas in 0.18.0 and I’m pretty surprised how it went in the end.

https://lemmy.world/comment/451026

permalink
report
parent
reply
12 points

permalink
report
reply
-1 points

I laughed a lot on it 🤣

permalink
report
parent
reply
0 points
*

I don’t know how this works but I think I read somewhere that this version fixes the new post spam on browser, I checked and it’s still the same, when will that be fixed? Is it an instance thing?

permalink
report
reply
2 points

What does new post spam mean?

permalink
report
parent
reply
1 point

I noticed in the web client used on mobile, there would often be new posts flooding in at the top of the page. Maybe a page’s worth at a time. I’m still using web client on mobile on lemmy.ml and haven’t noticed this since the deployment of 0.18 yesterday.

permalink
report
parent
reply
1 point

Yeah, that’s been addressed.

HTTP API instead of Websocket

Until now Lemmy-UI used websocket for all API requests. This has many disadvantages, like making the code harder to maintain, and causing live updates to the site which many users dislike.

permalink
report
parent
reply
4 points

The instance has to be running the updated version.

permalink
report
parent
reply
5 points
*

All Lemmy instances on v0.18.0 are inaccessible with javascript disabled. The only way to privately browse Lemmy instances now is via kbin. I was hoping that Lemmy was going to focus more on privacy with the coming updates. Maybe this will be fixed in v0.18.1?

#Lemmy

permalink
report
reply
3 points
*

JavaScript itself has nothing to do with privacy. I assume you think so because you are using Tor Browser at the higest security setting that disables JavaScript entirely?

IMHO just stop using that broken-by-design browser and use a browser extension with a JavaScript allow-list.

permalink
report
parent
reply
2 points

It should still be possible to browse the internet with JS disabled. Especially Free Software should set a high standard to that. It’s understandable that Lemmy devs have too much on their heads now, but let’s not pretend that it’s okay to make websites which aren’t viewable without JS.

permalink
report
parent
reply
3 points

That’s a LOT of changes. Kudos to all the people involved.

permalink
report
reply

Lemmy

!lemmy@lemmy.ml

Create post

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

Community stats

  • 207

    Monthly active users

  • 1.1K

    Posts

  • 14K

    Comments

Community moderators