#barnabywalterstantek: I followed some links and ended up at some of your old log pages — they’re quite fascinating (layout, content, etc). Were the comments done automatically or manually or a mixture?
#barnabywaltersI particularly like the comment layout — names, a flag for language, and sometimes a small annotation
#tantekI'd typically find the links as they showed up via Technorati
#tantekand then create new hyperlinks by hand, using known names for each blog, and lang / hreflang attributes as needed. the flags are all automatic via the CSS.
#barnabywaltersso by the first one you literally mean recreate twitter actions for doing stuff on twitter, as per twitters “requirements”?
#tanteknot per twitter's pub guidelines, but just to give people a familiar experience. so when they click a permalink on my tweets back to the original (perhaps to read more or view better embedded images / video), they can still favorite/reply/retweet/tweet etc.
#barnabywaltersthat would have the further benefit of providing entry points for UI hijacking
#barnabywaltersinstead of trying to inject UI elements, or having them out of context in some browser menu
#tantekright, it's a serverside way of doing that.
#barnabywaltersserver side? I’m talking about the publisher providing UI for taking actions (reply, fave, etc) which default to working with twitter, but which can be hijacked by browser extensions to work however the user wants
#barnabywaltersyeah — it’s the *actions* which are the important thing — that they work with twitter (or fb or whatever) by default is like POSSE — providing hooks back to silos
#barnabywalterswhilst fellow indiewebcampers can hijack them for their own purposes
#barnabywaltersso the challenge I have noticed building and using the fairly configurable Indieweb Reply is matching verbs up with the various bits of data you can expand into the URL
#barnabywaltersthe thing I am wondering is: just how much data should the WA provider (extension) give the consumer (e.g. indie site) — as much as it can find, or just a URL and leave the rest to the consumer server
#barnabywaltersand leave the rest to the consumer server. agreed, that’s the best place to start
#tantekand since HTML5 parsers/browsers will see and parse the <action> tag into the DOM, browser extensions can detect it and customize it ("hijack" as you say) to do whatever the user/reader wants the button to do
#barnabywaltershow acceptable is it to throw custom attributes into HTML? I know data-* is for nonpublic stuff
#tantekI myself will probably start with <action do=verb with=permalink><a href=twitter>..</a></action> patterns for the web action buttons on my site - that is, only providing the twitter fallback/default
#tantekwell if you use a custom tag, all the attributes are up to you
#tantek.comedited /webactions (+1146) "/* Brainstorming */ add a few sample verbs for Twitter equivalents and a bit more of the thinking behind them" (view diff)
#tantekbarnabywalters - there I just braindumped some more of the thinking that's been stuck in my head on this topic for a year or more. hopefully it makes some sense and you find it useful.
#aaronpkthere will be a front-page article that gets a ton of comments, and then the next day there will be a follow-up post from someone else that hits the front page again
#aaronpkso that gives me hope for the indie web still
bnvk joined the channel
#tantekI think if we figure out and build UIs that make it easy for us to blog upon each others blog posts (and have the pingbacks show up with decent presentation - note - current pingpack displays pretty much all suck), then we can create a critical mass ourselves.
#tantekany particular blog post that you liked in terms of the layout, content, comments presentation?
#tantekwould be good to get your perspective on which ones you thought were worthy of re-exploring in terms of UI etc. (I tended to change my blog presentation a lot more back then)
#tantek(and the presentation is baked in for the archives)
#tantekjust some example old /log blog post urls is what I'm looking for here
#barnabywalterswell, it was one announcing XFN where I saw the most interesting comment UI (names, annotations, flags)