Summary of Discussions (as best I can):

• @lyse@lyse.isobeef.org and @sorenpeter@darch.dk express simplicity. Both Lyse and Sorenpeter support location-based addressing.
  
• @falsifian@www.falsifian.org believes we should continue to develop ideas and extensions progressively over time like we’ve always done.
  
• @david@collantes.us @quark@ferengi.one and @bender would like a better user experience, especially when threads break due to edits, deletions or feed location changes.
  
• @anth@a.9srv.net would like to see utf-8 mandated, and the threading model remain largely the same as it is today, which is primarily based on the convention of a Twt Subject anyway, Twt Hash(es) just make the threading “more precise”. Anth also states that format, client and server specification/recommendations should be kept separate.
  
• @movq@www.uninformativ.de @xuu@txt.sour.is sorry you two haven’t said too much really, so I’m not too sure?
  

Overall, the 22 votes we’ve had on the poll from the community (if you can call it a community?) have clearly shown that:

• We continue to support content-based addressing. (65/35)
  
• We think about formally supporting edits/deletes (60/40)
  
• We do not increase the use of cryptography (thworing things like authenticity and identity out the window) (70/30)
  

And overall the NPS (net promoter score) of “Would I recommend Twtxt to a friend” is a whopping 7/10 (which is crazy! 🤯)

Let’s have our monthly catch up soon™ (1hr) and discuss together. My own take on the direction we should take at this point is as follows:

• We continue to use hashing for the threading model.
  
  • We think about changing this to SHA-256 for simplicity.
    
• We either adopt @anth@a.9srv.net’s UUID approach or @lyse@lyse.isobeef.org Dynamic URL approach.
  
• We continue to incrementally/progressively improve things over time as @falsifian@www.falsifian.org suggested.
  
• We think about mandating utf-8 as @anth@a.9srv.net suggests which makes things so much easier for everyone.
  
• We further discuss the merits/ideas of supporting formal Edit/Delete requests or other ways to better support this in some way.

@doesnm@doesnm.p.psf.lt The useragent tool now natively supports the Caddy (JSON) logfile format. 🥳

This Facebook/Meta story on storing passwords in plain text it just wow 😮 – Like how da fuq does a company, or anyone for that matter in the business of software / technology even do this?! Like at least base64 encode the fuckers right?! (oh wait 🤦‍♂️)

Last chance to have your say before tomorrow’s meetup:

http://polljunkie.com/poll/xdgjib/twtxt-v2