The-Navigators-Blog/source/blog/ssb-BXRqNCJsZutPKV5jzVeFywmpzNIEkeUJ7QfymjdSnhg=.html.markdown

title	date	tags
SSB Log Entry 687	2020-05-22T09:04:58-05:00

Pigeon Protocol Daily Update, May 22nd

Note to folks just tuning in: I do daily updates related to #pigeon-protocol - a project with similar goals to SSB.

DONE

The Ruby implementation now enforces "canonical ordering" rather than flexible ordering of header fields.

TODO

• Change @, %, & to FEED., TEXT., FILE., respectively.
• Go back to writing documentation
• I might actually get rid of multihash along the lines of what Kas suggested. That is, implicitly support ED25519 and SHA256 as defaults. I will call them "the only option" in documentation rather than the defaults. I think that:
  • ed25519 and sha256 have stood the test of time long enough.
  • We can easily add a .whatever suffix later if we need to.
  • It is also possible to configure the "world" that the feed lives to only use a certain signing / hashing algo.
  • I'm pretty OK with a future where a security concern causes feeds to be manually migrated by authors (or left behind for eternity). I don't think this is avoidable, given the eternal nature of a feed- is it?