MrKaplan @ MrKaplan @lemmy.world

other accounts:

---

Read more

Posts

2

Comments

364

Joined

1 yr. ago

Moderating

---

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

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,

we're continuously getting timeouts from your instance when trying to submit activities.

It looks like we're being blocked by your server at regular intervals:

https://grafana.lem.rocks/d/bdid38k9p0t1cf/federation-health-single-instance-overview?orgId=1&var-instance=lemmy.world&var-remote_instance=lemmy.horwood.cloud

You're probably using something like fail2ban that keeps banning servers trying to federate to you.

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.

mods can remove other mods if they are below them in the moderator list. for moderators higher up admin intervention is required.

as the default lemmy ui doesn't exactly make it easy to manage moderators in a community if they haven't posted or commented there recently i recommend using tesseract for this, where you can easily do this and much more in the community settings.

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:

check if your piefed account has pms from other instances enabled. afaik piefed.social had this disabled by default for some time during the nicole spamwave.

fyi also @Bonus@lemmy.world

lemmy currently doesn't have granular federation controls. the only option right now is to defederate from mbin instances, but other instances might still announce your users' votes to mbin instances. the more hacky way would be to also block federation related http requests from mbin instances to prevent them from retrieving user profiles, which is probably the most effective method that could be used.

piefeds non-federated votes are a user setting for the default value and users have the option for each vote whether it should be federated. see also https://piefed.social/post/982478

as explained in this post, the original implementation of "private voting" has already been replaced with non-federated voting, which addresses the abuse concerns, as it's then limited to just the instance the votes are cast on.

seems to work for me

it's the software, similar to how you're using lemmy right now

no notification of a moderation event

lemmy.world has notifications for local users or users in local communities for removed content.