I would love to add metadata to the spec, but someone would have to hack it into twtxt #issue48 @buckket? :)

@buckket I've put a proposal for #pgp verification of #twtxt up

Any particular plans @buckket?

Any particular plans @buckket?

@buckket Do you want to close all issues tagged enhancement and milestone 1.3 before you do another release?

(#v5yaeha) @movq As for developing a Twtxt 2.0 spec/format/protocol, I'm not sure. On one hand @buckket _seems_ to be quite upset that we've used his format/spec and named a "codebase" with a similar/identical name or something, actually I'm not really sure I'm just guessing, but its part of the rebranding issue at place here... So maybe we should? Maybe we should just develop our own protocol entirely? I'm not sure. It really isn't up to me per se now as there **is** a community to think about that spans multiple pods now.

@freemor Somehow I don't see your tweets after 2018-03-16 in the client although i updated your url. @buckket a caching issue maybe?

@buckket 👋 I owe you a **sincere** apology! When I came across your _really_ cool and simple twtxt.txt spec, I fell in love. Then I built what you see here today (_~5wks in the making now..._). Apparently I said "I was the new @bucket"" (_and because I'm actually legally blind I probably even typo'd the handle!_). I should not have done this; and I'm clearly not you, and I'm sorry for making this "joke". After talking to @erlehmann a fair bit tonight I _believe_ we actually have similar ideas and ideals and I'd love to connect with you.