#maxwelljoslynAFAIK there aren't wiki pages for individual HWC nights anymore, so I put the West Coast screenshot in a reply to the event page
#maxwelljoslynthe <img> has u-photo, and gets picked up correctly with Monocle's parser preview, but doesn't show up on the events page -- is it b/c my "notes" are actually articles? :*(
#aaronpkmaxwelljoslyn: Strange, I'll have to take a look, I thought that should have worked
seekr, lucasban, jonnybarnes, rEnr3n1, gRegorLove, gxt, nickodd, markopasha, dckc, swentel, loicm, willnorris, voxpelli, genehack, mclemens, bigbluehat, ramsey, rEnr3n, raucao, jeremycherfas, KartikPrabhu, hirusi, anotheryou and [Murray] joined the channel
#[Murray]Wow, on npr declining the GDPR/cookie request serves a page with just text, not even CSS. That's kinda great actually (and loaded _so fast_ compared to what I'm used to 😄 )
#@yuuuanw👋 Design Twitter, recently I started researching and saving design books written by women and people of color. It has grown into a collection that also includes books about research and content strategy. http://yuanwang.design/resources Spread the word if you find it useful. ❤️ (twitter.com/_/status/1295125412461256704)
wolftune, jonnybarnes and kensp joined the channel
#mayakate[m]<[Murray] "Wow, on npr declining the GDPR/c"> https://text.npr.org/ for anyone curious who's given them cookie permission
wolftune, jonnybarnes, KartikPrabhu, [KevinMarks] and maxwelljoslyn joined the channel; nickodd left the channel
#maxwelljoslynaaronpk: thanks for offering to take a look, i was surprised too :)
Nuve joined the channel
#Jeena1I totally forgot about the fact that I have events on my website so I didn't host any event there since 2017 but today I remembered! https://jeena.net/events/26
#[tantek]among other things, while something is a draft it explicitly does not show up in feeds
#[tantek]or streams in general, e.g. on the homepage
#[tantek]it may show up discoverably in *archives*
#[tantek]maybe even called out (with an icon or something) as a draft
#[tantek]so in that way it's different from unlisted posts
#Jeena1it would need to somehow allow comments to be useful wouldn't it? But I guess it wouldn't be a problem with versioning, etc.
#ndegruchyA sort of status field, or just a kind of "rough cuts" idea?
#[tantek]if I do this it'll likely "force" me to make them have a URL date that is based on when I started it (created it?) not "published date", and I think I'm ok with that
#Jeena1I would like them to be able to somehow be connected to the version of the draft they were commenting on
#ndegruchyYeah, giving comments a status requires a bit of engineering, unless you're marking it on your own system and not trying to send it back ala webmention
#[tantek]jeena yeah! we touched on that capability (but for wiki-like "pages") in HWC this past week!
#[tantek]ndegruchy is your post in github and do you do that partly so you can accept pull requests for typos and such?
#ndegruchyComments with a pointer to a git/md5 hash of the draft
#[tantek]or heck even people "helping" with adding links etc
#ndegruchy[tantek]: Eh, more of "versioning", but yeah, those are things that could be useful
#ndegruchyYou could even just send in a mail formatted patch from git and I could apply it
#[tantek]not sure about the strictness / fragility of being bound to a hash (e.g. in Google Docs, changes in other parts of a document don't make comments in one part less true / relevant)
#Jeena1I think UI wise it's ok to show the comments in the latest version but there should be a link to show the post how it looked like when that comment was made.
#ndegruchywell, hence the idea of comment at a diff/hash, but visually linked via fragment
floridafruitgeek joined the channel
#ndegruchyso temporally, the diff/hash point, but fragment bound. Then you can layer the diffs on top, and as the fragment still exists, bring it forward
jonnybarnes joined the channel
#ndegruchyI feel like we're in MediaWiki territory, but with Office style comments
#ndegruchyI wonder if you could bundle up that kind of document into a gzip of git history or similar, and just parse out the latest revision with any comments
#ndegruchyI imagine corruption of said document would be pretty ugly to try and untangle, though depending on how bad, you could parse out commit entries and recover that
#Jeena1I like how Confluence handles inline comments.
#ndegruchymayakate[m]: Quotebacks are really cool. Though I wish they didn't have so much JS
#ndegruchymayakate[m]: Yeah, trying to link to fragments is one of those holy grail kind of things, though. Since content changes so frequently, it's usually not a reliable linking mechanism
#ndegruchyAs you mentioned with Chrome, you can get close, but if any of that text changes, it's broken
#Jeena1you could add nonvisible markers in your text.
#Jeena1The nice thing is that those would just move with the text if you insert something in front of them and they would be removed with the text if you remove the text etc.
#ndegruchyI think I like quotebacks so much because they're a point-in-time copy of the information with a link to the source
#ndegruchyit works with how reality is. in an ideal situation, we'd never have to worry about the information being gone, because there would be some sort of ephemeral copy floating around with our reference point.
#ndegruchyyou could hide the referenced data in with the reference link... though you run into storage and complexity issues, as well as hidden metadata