RSSMention

I mentioned before that I have a concept that allows sending comments to RSS posts without the need to authenticate with the host. Instead, you authenticate with the DNS domain and the web server you run on it. It's very similar to webmention, but for RSS instead of the web.

The following (raw) bullet points are from an email I wrote describe the current state:

RSSMention

  • webmention doesn't really work for feeds. It's meant for a link from one webpage to another, not from one feed to another.
  • Having a webpage for each user comment is not practical. There are people writing 1000s or even 10000s of comments every year. Managing them on a static webserver won't work, and I don't want users to need dynamic webpages.
  • Having comments stored in RSS feeds is more doable. You can put 100 or so in a single file, and there are fewer reasons to regenerate the RSS file.
  • The mechanics of webmention are perfect, but feed comments need to be from one permalink to another permalink, not from page to page. The comment's source feed must either be specified separately or included in the permalink (like <feed-url>#<comment-number>). So it probably shouldn't be called webmention. In my notes, I called it RSSMention.

Authenticity

  • Another consideration is authenticity. Basic authentication of a comment can be established by checking whether the comment is also on on the user's comment feed, which should be available to the RSSMention server (either in the permalink, or submitted in a separate field).
  • But a feed could make up a comment that I never wrote, or modify my comment without my permission. I can only prove that the comment is not on my website right now, but I can't prove that I have never written that comment - I could have deleted or modified it.
  • Without establishing authenticity, there are all kinds of legal problems. People could forge comments ("Wow, Elon Musk liked my idea!" and there is no proof that he didn't) and claim that you wrote things that you never wrote.
  • So my idea was that a comment author needs to publish a public key (somthing like /.well-known/public-keys/tim.crt), and a signed hash must be part of the permalink. So more like <feed-url>#<keyname>+<signature>. The signed hash must include all the essential parts of the comment (author name, inReplyTo, title, pubDate, body), e.g., in a JWS format. That way, an owner can legally prove that the comment they republish is legitimate. An extra field in the hash ({canBePublished: true} or {license: 'CC0'}) could also solve potential copyright issues when republishing comments.
  • A key name is required because you can't expect users to manage their keys, especially if they are using multiple clients. It's much easier when a client app creates a new public/private key pair each time it is installed, and then uploads a new public key to the server.
  • My unsolved problem right now is: what happens if someone just deleted their public key and claims they never owned it...? There needs to be some way to either publish the public key itself, or to have it validated...
  • RSS readers should validate the signatures, at least for some comments (like checking every 100th and report the comment if invalid).

Reactions (likes...)

  • I think the simplest solution for likes is to use a single-character comment. To like a post, just send a ❤️ as comment
  • The CMS or RSSmention server can then count reactions.

Policies / Capabilities

  • Realistically, if you use feeds not only for personal blogs, but also for forum-style discussions to replace subreddits or Facebook groups, you need to define policies/capabilities for comments that you accept.
  • A feed that allows RSSmention comments must declare what's allowed in comments. Links/URLs? Images? Tables? Max length? Title allowed/required? Required license? The goal is that the RSS reader (client) only shows options to the user that are allowed in comments for that particular feed. If you don't do that, it's very frustrating for users to see when the comment they wrote is not accepted.
  • A feed that allows reactions must declare which reactions (a string with all possible reactions should be sufficient, like "❤️👍👎")
  • You probably need to link some document with ToS or rules for groups.
  • In other words, this requires an RSS extension that links to the RSSmention URL and describes the capabilities / policies.