3 ms·

Also seems to tie together with the last bullets on these minutes: https://meta.miraheze.org/wiki/Board/Policies/20230607-Minutes https://meta.miraheze.org/wiki

• joecool1029 3y ago
  I had figured it was not exactly technical burnout in running Mediawiki installs but regulatory burnout in following Euro GDPR/cookie banner/bullshit-of-the-now requirements. Some of them are easy but the rest phase in once you reach a certain scale of users (which it sounds like they probably have).
  • LordShredda 3y ago
    It clearly says technical burnout. Why do you have to blame GDPR? If anything it was the best thing to happen to the open internet
    • aerio 3y ago
      Yeah, speaking as a European tech lead; GDPR was a pain in the butt a few years ago when it was introduced - and all client websites had to be retroactively fitted with cookie systems, routines had to be implemented, stuff had to be learned, etc. Once sites are planned with it in mind from the get go it's really no big deal, and huge for the end user.
      • duskwuff 3y ago
        For a wiki farm like Miraheze, GDPR/CCPA/etc compliance is fairly easy. MediaWiki collects fairly little personal data about users, and there are well-defined methods for the site operator to export or delete that data if a user requests that they do so. Besides, that all kicked in years ago. It's not a new concern.
      • Nemo_bis 3y ago
        Cookies were regulated by the ePrivacy directive back in 2009. The case raised above is about someone who had access to see the users' IP address. Handling training and authorisations for people with access to personal data is an ongoing job, not something you do once and forget.