tantek_I've gone from describing reply-context brainstorming e.g. for in reply to github URLs to thinking of that as just auto url summary, and now thinking how to document it - because while useful for reply-contexts it's not only for reply-contexts
tantek_curious if anyone else has written any similar code (in functionality) and if so, what names / terms they came up with (even just for function names)
KartikPrabhu, gRegorLove, eli_oat, renem and [quinnvinlove] joined the channel
schmartyi have confirmed that my new setup of selfauth + mintoken + skippy's micropub server (w/ some tweaks) now works with Teacup (my fork which uses JSON because Teacup's nested form-encoded data is no longer compliant w/ Micropub spec)!
schmartyi can now do a lot more experimenting with micropub and my personal notes site, which is very exciting for tracking things that i don't want to publish but do want to manage in a webby way.
schmartyGWG: sort of! old accounts on Teacup had a flag which meant they received form-encoded values of p3k-food and p3k-type. that setting could be changed to get an "ate" or "drank" with nested h-food data. still form-encoded though.
schmartyGWG: i keep myself organized with what amounts to a private website powered by Hugo. i take daily notes, track weekly and ongoing TODOs, and more.
schmartywhen skippy added post type discovery support to his micropub server (which targets saving files for hugo), i realized this would be a pretty good combo.
schmartyso with teacup set up to post to my private site, and the micropub server set to handle posts with ate / drank properties as a new "type" of post, i hope to start doing more small-q quantified self.
schmartyi think eventually i'll set up my public website as a syndication target for certain things, but meanwhile i'll be capturing the stuff in a way i feel safe about and can start experimenting with how to display, etc.