Here's an idea I think could be fun and/or interesting: adopt the /.well-known/ (RFC 5785) convention for public and private keybase directories. Files stored within this standard, probably hidden, top-level directory (inside a kbfs folder) would have certain standard formats and provide additional functionality for users, effectively overlaying social networking capabilities on top of kbfs.
blog
This could be as simple as a directory containing a collection of Jekyll-style Markdown files with YAML front matter containing metadata, or just an Atom XML file. E.g.
Keybase already naturally provides the "follow" mechanism present in sites like Twitter, Tumblr, etc. to construct a social graph, but with the added goodness of signing and (if-desired) privacy-via-encryption.
Here's an idea I think could be fun and/or interesting: adopt the
/.well-known/
(RFC 5785) convention for public and private keybase directories. Files stored within this standard, probably hidden, top-level directory (inside a kbfs folder) would have certain standard formats and provide additional functionality for users, effectively overlaying social networking capabilities on top of kbfs.blog
This could be as simple as a directory containing a collection of Jekyll-style Markdown files with YAML front matter containing metadata, or just an Atom XML file. E.g.
microblog
Something similar to the above but with additional constraints on content length, etc. trsst is interesting here.
cv
A JSON-based format for describing CVs could do the trick here. Other XML-based formats like XMLRésumé are also of interest.
vlog
An Atom feed coupled with video files, perhaps?
With these kinds of documents stored in a kbfs folder, it would then be interesting to enable their display as part of the keybase user profile, e.g.
Keybase already naturally provides the "follow" mechanism present in sites like Twitter, Tumblr, etc. to construct a social graph, but with the added goodness of signing and (if-desired) privacy-via-encryption.