Chronotope’s avatarChronotope’s Twitter Archive—№ 87,826

  1. …in reply to @irwin
    irwin I am a big fan of controls, but it is hard to see how a CMS could regulate this without getting into some very slippery slopes. I think WordPress, like other CMSes contains data that users can choose to make transparent that can help with this.
    1. …in reply to @Chronotope
      irwin Things like 'number of users who edited this piece' or 'time spent in article by editors' are all easily recordable using current methods but lack a schema to represent themselves easily. A task for a larger authority like the w3c/schema dot org.
      1. …in reply to @Chronotope
        irwin Having worked with many many CMSes at this point, the reason WordPress is used for fraud is because its prominence. If another CMS had more prominence that is the one that would be used. Nothing in fraud behavior is something only WordPress can do.
        1. …in reply to @Chronotope
          irwin Ironically the most popular tools used by fraudsters who implement WordPress aren't allowed in the theme or plugin directory, they're paid-for-products sold between fraudsters.
          1. …in reply to @Chronotope
            irwin And the WordPress parent company does make tools available to block spammy comments, good ones.
            1. …in reply to @Chronotope
              irwin WordPress's design succeeds in part because it restricts to recommended UX while allowing expansion by to different levels by different types of users. For this reason, I think that most CMSes tend to gravitate to be WordPress-y.
              1. …in reply to @Chronotope
                irwin I think for all its flaws, and there are plenty that a savvy observer or suffering engineer might point out, WordPress is in its position because it has an archetypical CMS UX. Impacting that won't stop fraud, it will just move it.
                1. …in reply to @Chronotope
                  irwin That said, as WordPress moves towards supporting more automated tools we will see an explosion in fraud that is arguably unavoidable. All systems are moving towards API-driven actions, which means big opportunities for fraudsters.
                  1. …in reply to @Chronotope
                    irwin The best way to avoid this is to increase signaling of human actions on a piece and tie that to human identities that are inviolate and capable of being cryptographically signed (this is not a thing blockchain is needed for) but....
                    1. …in reply to @Chronotope
                      irwin Tying reliable human identities to journalistic activity is not always a desired goal. Nor is it really a desired social goal. We live in a difficult middle point where our capability to stop fraud is hindered by our desire to preserve our privacy, which is rock vs hard place.
                      1. …in reply to @Chronotope
                        irwin That said, for those journalists who tie PGP keys to their work it is a crying shame there is no standard to represent that and tie/sign their identity to work across multiple sites.


Search tweets' text