Skip Navigation

Posts
0
Comments
138
Joined
2 yr. ago

  • the issue lies with cloudflare and not lemmy. wold, correct?

    the issue seems to stem from a change done by Cloudflare not too long ago, but that doesn't mean that we're unable to work around it. i'm currently implementing some changes that should help with this.

    any info or links about this cloudfare issue known atm?

    the link was included in my previous comment

    please translate this into user experience

    for the most part, any "read" operations (looking at a post, comment, user, etc) should not be affected by this. for any "write" operations (login, posting, commenting, editing posts/comments, etc.) there seems to be a higher error rate currently related to this. in those cases the action would simply not be completed, and depending on the client (app, default web interface, alt ui) this could range from and endless loading indicator to an error being displayed to nothing being displayed.

    if this has resulted into more strict automod functions

    no, and this was not an automod removal. you can see the reason why it was removed in the modlog: https://lemmy.world/modlog?postId=36129581

    you should also have received a message from our automod informing you about the removal, but automod is only informing you about what happened, not the one taking action in this case.

  • seems like we're not the only ones trouble by some changes clouflare did to their OWASP ruleset: https://community.cloudflare.com/t/owasp-ruleset-unexpectedly-has-a-high-false-positive-rate/814544/19

    this is a change cloudflare did to the detections they have for http requests to our server. this could affect any API calls from any clients towards our API backend, including automod actions. at most however this would prevent some automod actions from being executed, it couldn't cause e.g. false positives.

  • thanks for sharing this.

    it seems that cloudflare's managed rules for the OWASP are hitting a bit much lately. this request has been blocked as "Inbound Anomaly Score Exceeded" with an "OWASP score" of 49, hitting a bunch of rules in the managed OWASP ruleset, many of them relating to SQL injections. i'm gonna have a look at what we can do to tune this down.

  • Deleted

    Permanently Deleted

    Jump
  • the only reason comments would disappear without modlog entry would be a community or instance ban with the remove content checkbox selected. the only other option would be purging content, which is only available to people with the admin tag and we don't use this anyway. it would also leave purge modlog entries. the lack of modlog entries not existing for community bans is a lemmy issue, not specific to LW.

    you can find your community bans here: https://lemmy.world/modlog?page=1&actionType=ModBanFromCommunity&userId=239118

  • Deleted

    Permanently Deleted

    Jump
  • it's not as much about the removal of those comments being the issue in and of itself for us currently, but that this is being done by a person in his position. we haven't really been enforcing any special rules for moderator behavior on LW in the past (hence also currently considering a mod CoC), but having a member of our team incorrectly accusing people of lying and spreading misinformation on their own, even after seeing arguments for why he's in the wrong is very much a step too far. i wasn't directly involved in the discussion back then, so i don't know the entire message history, but it was my understanding that he would at least stop with those claims, if he wasn't able to apologize for it.

  • Deleted

    Permanently Deleted

    Jump
  • there were several recent reports, including private ones. also, just because you may not see something, it doesn't mean that nothing is happening. we have already discussed topics like the Canadian politics one with him in the past, as we also don't consider it acceptable what he did back then.

  • Deleted

    Permanently Deleted

    Jump
  • we have started looking into reports about jordan a few days ago, and we have already identified several occasions where he has been acting in ways that we don't consider to be acceptable for a member of our community team. it may still take us a few more days to come to final conclusions for how we will proceed with this, as this is something that needs time for a proper review and discussions within the team. we all have lives outside of lemmy, where we need and want to spend our time, and something like this takes hours to properly review.

    one of the things we have already discussed will be establishing an internal CoC for community team members and people higher up in the team, which includes ensuring that we keep a certain level of professionalism in our interactions, even if another party doesn't. we're obviously all humans, but that doesn't mean we don't have responsibility for our actions, especially if it's not a one-off thing. we will also consider if this may be something to establish for community moderators in general, but for now our primary focus is on people in positions above a regular user or moderator.

  • as @Blaze@lemmy.zip mentioned, we don't care about usage of multiple accounts generally.

    we do prohibit the same person voting on content (their own or others') with multiple accounts, and obviously using multiple accounts for ban evasion is not allowed. spamming a community with multiple accounts pretending to be different persons should also be avoided unless the community explicitly allows it, which seems to how you want to do it based on your description.

  • you could save some storage with this, but i don't think it's a good idea. a lot of people expect the threadiverse to have a lot more permanence than e.g. mastodon, similar to reddit. being able to find old posts/comments about a certain topic is one of the things that made reddit as useful as it used to be, especially when searching for tech related issues in my experience. old doesn't necessarily mean obsolete, and whether this would be suitable would be highly dependent on the community. most communities are not intended to be for ephemeral content only.

  • what would that have to do with this?

  • we do have some limits in place, but lemmy only allows rate limits per ip, and those are counted in each backend process independently. I'm currently working on implementing better rate limits in our load balancer.

    due to rate limits historically not working at all or not working properly, there are still various instances without decent limits. additionally, these rare limits only apply to local users. federated activities are not limited within lemmy. we recent added some fairly high limits to our automod to catch some of these cases and it's been working alright so far.

  • Can you guys remove @irelephant@lemm.ee as a mod from !guineapigs?

    Jump
  • removed from all 3

  • we don't ban individual IP addresses, but we restrict posting/commenting/media uploads from some VPN/data center IPs.

  • afaik the decrease in users has mostly been on mastodon.world, where the suspected reason is to a large degree requiring registration applications to prevent spam bots. this seems to scare off a lot of users unfortunately. i'm not involved in the mastodon stuff, but afaik there is currently no system similar to what we have on lemmy or piefed to automatically accept applications after certain checks were successful.

  • they're referring to Lemmy developers, not someone using/running .world

  • I'm assuming that you're referring to the Lemmy developers. FHF supports Lemmy development with a monthly donation of €50, same as we do for Mastodon development.

    If it makes you feel better, there are enough other people donating who don't mind some or all of their donation amount going towards Lemmy development to offset your donation not being used for Lemmy development contributions.

    It's not worth the effort to set up independent purpose-bound donation pools to separate donations from people unwilling to support certain people/organizations, as the end result would be the same, except a lot more maintenance/accounting overhead. Calculating with the current expenses of €1,700/month, this is less than 3% of the total donations we'd need to cover our bills.