this is a bug in lemmy-ui. it works in alternative interfaces, e.g. at https://t.lemmy.world/c/%D8%A5%D8%B3%D9%84%D8%A7%D9%85.
the bug report about this was just recently closed due to a lack of external contributions to address the issue: https://github.com/LemmyNet/lemmy-ui/issues/2207
hello,
based on your other post, which has since been removed by moderators of that community, it seems that you are looking for the !perchance@lemmy.world community instead of this one.
you're not going to have much luck here, as here people won't even understand what you're talking about.
that's because SJW is still on 0.19.11. 0.19.12 fixes this by forcing new posts in NSFW communities to be NSFW. see #5649. the UI change made it in 0.19.11 already but the backend change was broken and not backported.
that's answered in the comment i linked
please remove the phishing link from this post immediately. you can defuse it e.g. by putting it in a code snippet and replacing the dots with [.], e.g. netprocesse[.]com.
https://lemmy.world/comment/16818450
if you're talking about the image issue from this post, I have no plans to work on that as we don't use the image proxy but if anyone wants to PR that they're more than welcome to do so.
we're currently looking into some performance issues, we're looking into updating to the latest version this weekend, which fixes a few potential deadlocks. lately we've been getting DB deadlocks rather frequently, which results in significantly worse performance until we restart one of the services.
i see. for PWAs that's expected, for the native app i would've expected a consistent UA for all requests.
our current blocks/challenges are explicitly targeting things that pretend to be browsers while not actually being browsers. we try to exclude requests that are expected to be accessed by browser based clients that aren't directly on the main site. appending to browser user agents still matches our browser user agent detection.
i'm not sure why this was causing issues here though, especially with the login, as that should just be 100% api stuff and therefore use VoyagerApp/1.0 from the native app?
Hi,
this was possibly an unintended side-effect of our increasingly aggressive AI crawler DDoS blocking. When increasing the scope of issuing Cloudflare challenges we missed excluding API endpoints from the rule, that should be fixed now.
This should only have affected clients with browser user agents though, and I see requests with user agent VoyagerApp/1.0. @aeharding@vger.social do you know if Voyager can send browser-like user agents when installed from App Store?
it's in the main settings area:
took a bit while reviewing this but the user is banned now.
unfortunately this is probably only the tip of the iceberg, and most of these accounts we never even see reports about. it's also pretty hard to follow/authenticate accusations once they move the conversation off the platform. while lemmy is obviously not a good place to have private conversations, it does make reviewing such cases so much more difficult, which is most certainly also the reason they push for another platform quickly.
fyi @chosensilence@pawb.social @SendMePhotos@lemmy.world