4 ms·

Although I have never published a blog, I sometimes thought about how I might do it if I did. The "comments" could be treated like "letters" (to the editor).

Although I have never published a blog, I sometimes thought about how I might do it if I did. The "comments" could be treated like "letters" (to the editor). Comments could be treated as submissions, subject to prior approval before publication in the next "issue" of the blog. The author of the blog (editor) would receive a copy of each comment, then decide whether to publish it. Human curation. (Of course the blog author could use automation to assist the review.) In sum, I would treat the blog similar to a pre-internet, printed publication. From what I have seen this is how we achieve some degree of quality control. (Most "content" on today's web is garbage.) However one thing I never liked about "letters to the editor" is that rarely are submissions published in their entirety or original form. Editors like to edit. As such, I would allow the public to publish, without prior approval, an ed25519 hash of their submitted comment on the blog. Then if after review the comment is published, they can claim attribution, and readers can be certain that the blog author did not edit the comment. If spammers or other people want to try to stuff obvious or hidden messages into ed25519 hashes, I think that would entertaining. There should be a bar that those submitting comments have to meet if they want to see their comment published. The blog author sets that bar. This is a service to the readers.

a1369209993 5y ago
> ed25519 hash Ed25519 is a public key (usually signature) system, not a hash function. You're probably thinking of either a ed25519 signature, or a (for example) sha512 hash.
- deleted 5y ago
  [deleted]
- o8r3oFTZPE 5y ago
  s/hash/signature/ Sloppy terminology. Apologies. For example, here's the 64-bit signature for the comment above: e3b2b607891e364b0c80df9fe926a5aed125d8f4a0f2f4c58b58b87b92884e634bb614f13cad372f074158c035eb382535b6d33d9ba10d7d59843a17dee5720e Here's the 32-bit public key: bf9fae774061bb6f5deea9380ccdf11263071bc256c1bd0947572f0a3dcc3806 The blog author could allow commenters to publish their keys and signatures. If the author later publishes their comment, the reader can verify 1. it has not been edited (a hash would also suffice for this) and 2. it was signed with the commenter's published key (presumably by the commenter).
- o8r3oFTZPE 5y ago
  s/hash/signature/ Sloppy terminology. Apologies. For example, here's the 64-bit signature for the comment above: e3b2b607891e364b0c80df9fe926a5aed125d8f4a0f2f4c58b58b87b92884e634bb614f13cad372f074158c035eb382535b6d33d9ba10d7d59843a17dee5720e Here's the 32-bit public key: bf9fae774061bb6f5deea9380ccdf11263071bc256c1bd0947572f0a3dcc3806 The blog author could allow commenters to publish their keys and signatures. If the author later publishes their comment, the reader can verify 1. it has not been edited (a hash would also suffice for this) and 2. it was signed by the commenter's published key.

a1369209993 5y ago

> ed25519 hash Ed25519 is a public key (usually signature) system, not a hash function. You're probably thinking of either a ed25519 signature, or a (for example) sha512 hash.

deleted 5y ago
[deleted]
o8r3oFTZPE 5y ago
s/hash/signature/ Sloppy terminology. Apologies. For example, here's the 64-bit signature for the comment above: e3b2b607891e364b0c80df9fe926a5aed125d8f4a0f2f4c58b58b87b92884e634bb614f13cad372f074158c035eb382535b6d33d9ba10d7d59843a17dee5720e Here's the 32-bit public key: bf9fae774061bb6f5deea9380ccdf11263071bc256c1bd0947572f0a3dcc3806 The blog author could allow commenters to publish their keys and signatures. If the author later publishes their comment, the reader can verify 1. it has not been edited (a hash would also suffice for this) and 2. it was signed with the commenter's published key (presumably by the commenter).
o8r3oFTZPE 5y ago
s/hash/signature/ Sloppy terminology. Apologies. For example, here's the 64-bit signature for the comment above: e3b2b607891e364b0c80df9fe926a5aed125d8f4a0f2f4c58b58b87b92884e634bb614f13cad372f074158c035eb382535b6d33d9ba10d7d59843a17dee5720e Here's the 32-bit public key: bf9fae774061bb6f5deea9380ccdf11263071bc256c1bd0947572f0a3dcc3806 The blog author could allow commenters to publish their keys and signatures. If the author later publishes their comment, the reader can verify 1. it has not been edited (a hash would also suffice for this) and 2. it was signed by the commenter's published key.