sorted by: new top controversial old
New User Monitoring in c/meta@programming.dev
[–] [S] 1 point 1 day ago

This stuff hasn't been the cause of the recent outages. The admin did a Debian update a few days ago, and somehow the server is very unstable ATM. The entire server has been dying on us, so we can't even put up a static maintenance screen.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Was there an outage today? in c/meta@programming.dev
    [–] 2 points 3 weeks ago

    There is discord and matrix if you need to get in touch, linked in the sidebar. Unfortunately, as we are a very small team, we can't guarantee that notifications will be sent for unplanned outages, but we do try to send them for planned outages.

    There is also a status page, but given it appears to be broken I won't link it :D

    If you have any other solutions we'll be happy to consider them.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Wid: My package manager project in c/rust@programming.dev
    Add gg to any GitHub URL — ranked forks + open comments on the repo in c/programming@programming.dev
    Add gg to any GitHub URL — ranked forks + open comments on the repo in c/programming@programming.dev
    Stack Overflow drops to 1,442 questions in July, down 99% from 2014 peak in c/programming@programming.dev
    New User Monitoring in c/meta@programming.dev
    New User Monitoring in c/meta@programming.dev
    80
    New User Monitoring (programming.dev)
     

    Hi All,

    Tldr:

    • We are monitoring publically available information (posts, comments and DMs).
    • Monitoring is turned off as soon as the admin team are satisfied the user is legitimate.
    • will only temporary remove, no bans or deletion without a human being involved in the decision.
    • No user data is sent off to 3rd party tools, all processing is done on the instance server. No LLMs are involved.

    Due to some ongoing issues with harassment campaigns, we've had to setup a rudimentary monitoring system for all new users.

    • When a user's signup is accepted, they will be automatically enrolled into the monitoring system. The admins team may also add accounts manually if they have been given a strike.
    • The system will monitor all posts, comments and DMs sent by new users, and bring them to the attention of the admin team if it appears suspicious. In egregious cases, it will auto-remove posts and comments if required, but a human admin will always review and reverse any false positives as soon as required.
    • Once we have validated that the user is not a harasser, they will be removed from the system.

    We don’t want to go into too much detail on how it all works to prevent bad actors from bypassing it, but we can say that all the processing is being done locally on the instance server. For most of you, this wont have any impact, but some of you have been impacted by the systems false positives. It is also a good time to point out that DM messages are not private, and should not be used for anything that requires strong privacy.

    There will likely be teething problems, but we are actively working on improving the bot to minimize impact and we are always open to feedback.

    How to Hate AI in c/Aii@programming.dev
    Why I Built JADEx Instead of Switching to Kotlin in c/programming@programming.dev
    Fell for it again award in c/actualcommunism@lemmy.dbzer0.com
    [–] 1 point 7 months ago (1 child)

    If you join another instance, you wont be subject to our filter. It is meant to prevent abuse, we have issues with new accounts abusing other users, and this is our only way to prevent it.

    I have been manually undeleting the messages as I get to them, but it is a human process, so it takes time.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Fell for it again award in c/actualcommunism@lemmy.dbzer0.com
    view more: next ›