#tantekand then once they solved the where are comments stored, how do we notify comments have been made problems - they claim they're done (e.g. pingback)
#aaronpkand that's why I'm not really interested in building any sort of backend comment thing yet until the UX part is figured out
#tantekand then fail to actually solve *the most important problem*
#tantekthe UX of the damn thing in the first place
#tantekwell, by "until the UX part is figured out" - do you mean, until the UX part is figured out by someone else, or until the UX part is figured out by you?
#tantek(I'm trying to do the latter, obviously, figure out the UX of a good commenting system)
#aaronpkyea, it's fascinating how different the engagement is between all the services
#tantekeven between their web / mobile-web / iOS app versions - it's like they have different designers on each that are designing more by taste than by what actually works best (across all three)
#tantekThat is, when people comment, they're @-replying to the POSSEd copy of my note, but without leaving the original post permalink page of my note.
#tantekExcept if *I* reply, then obviously it gets posted on my site first, and POSSE'd to Twitter, with the in-reply-to-status-id set accordingly to whatever I was replying to.
#tantekthat's my thinking in terms of what can I code sooner than a fully federated system, and still have people be at least somewhat interested in using it
#tanteknow what would be *really* interesting is to figure out how make a "Comment" or "Reply" webaction button which e.g. your site or Barnaby's toolbar could take over and then use it to post to your own site, and then notify my site through webmention
#tantekso my first goal is to enable others to @-reply to my notes directly from my notes pages themselves, rather having to go to Twitter to find the POSSE'd copy and reply to that
#aaronpkand people should be able to reply to one of the comments the same way!
#tantekand then of course to allow me to also follow-up reply to those
#tantekbut before I implement any of this UI I want to first be able to reply to tweets from my site the way you and Barnaby (and tommorris too?) do
#aaronpkyes I would change the UI I use for mine if I were to implement comments as you described
#tantekand heck - all you guys display/link to your POSSE'd copies totally differently!
#tantekso there's no indieweb UI pattern yet for displaying links to syndications
#tantekI mean we just came up with rel=syndication for discovery of said links like last week or something
#tantekhas been trying to wrap his brain around the entire set of distributed commenting UI/protocol/implementation challenges.
#tantekand tease out building block solutions one at a time
#tantek.comedited /comment (+207) "/* Examples of Replies */ distinguish best practice of threaded POSSE'd tweets vs. adhoc reply practices" (view diff)
#@efemurlRT @biancawelds: So I went ahead and replaced Google Reader with a self-hosted Tiny Tiny RSS installation. So far, so good. #indieweb
#tantekaaronpk - AFAIK - you have the only example of an indieweb reply to an indieweb post where the POSSE'd copy of your reply properly links back to the POSSE'd copy of the indieweb post you're replying to.
#aaronpknot moving, but our office is now reconfigured and we don't really have space anymore (we're at 14 people now instead of the 6 we were last year)
#aaronpkI have a lead on another space though, not far away
#aaronparecki.comcreated /Category:Events (+114) "Created page with "Below are pages representing IndieWeb events, including each year's conference as well as meetups during the year."" (view diff)
#tantek.comedited /projects (+233) "/* experimental */ and p3k goes to the top of this list, since there's two indiewebcamp community members using it" (view diff)
#barnabywalterstwo users? congrats! that’s an indiewebcamp record, no?
#tantekfor something developed by one of us? yes, it's a milestone :)
#tantekbarnabywalters did you see the comments/replies discussion from yesterday?
#tantekand when you get back - wondering if you've posted any replies on your site to other indieweb posts, and then had your POSSEd tweet link back to their POSSEd tweet
#barnabywaltersRE placement of comments box before/after comments: yeah, I wonder if any research has been done to determine how effective each approach is. I like facebook’s approach of showing your comment inline with the conversation, and truncating it to the last few items
#barnabywaltersfacebook’s overall UI tends towards not being much good, but I think they have lots of little components which are very effective
#barnabywaltersand obviously they have lots of money+people working on getting high engagement
#tantek" lots of little components which are very effective" - totally agreed
#barnabywaltersalthough we’ve already determined that they optimise for regular dopamine triggers and that we should be careful about copying that
#tantekdefinitely some design inspiration we can steal there
#barnabywalterslol — I can’t help but think “I’m discussing the differences between a reply and a comment — where did my life go wrong?” ;)
#tantekI'm fine with just calling them all comments for now
#tantekbarnabywalters - there's a difference between discussing and capturing ;)
#tantekwe capture it on the wiki so we can park the discussion in its current state without feeling a need to discuss it further immediately and come to some grand conclusion :)
#tantek(incidentally, capturing such partial/incremental discussions seems to be both a challenging/useful skill to learn, and particularly good use for wikis)
#barnabywaltersyeah, I have #indiewebcamp to thank for introducing me to wikis as a thought management system
#tantekbarnabywalters - I'm leaning towards thinking that we do really need a separate design for writing indieweb comments than just what indieweb post authoring UIs provide
#tantekthe context is so important when writing a comment
#tantekthat any comment UI must show the context of what you're commenting about
#tantekso e.g. if you have a comment webaction button on your post, and I click it, either I get an in-place UI to write a comment post on my own site, or if in-place is too hard (or no JS etc.), then it should take me to the comment webaction endpoint on my site
#barnabywaltersat which point in-place, probably via webactions + iframes is the path I’d take
#tantekthe latter (webaction endpoint on my site) is also likely easier for me to just go implement
#barnabywalterstantek: we already have #2, and the iframe + postmessage code I was working on earlier is the basis for #1 ;)
#tantekwhereby, e.g. if I click a "Reply" button on Twitter, the browser extension knows to make that take me to the comment UI on my own site, with the original tweet loaded as context above the text input box
#barnabywalterstantek: did you test out the web action toolbelt?
#tantekinstead of just having a dumb text input for the URL of the tweet I'm replying to, I want my UI to show the tweet I'm replying to
#barnabywaltersphp-mf2 has backward support for twitter.com classnames, just so you know
#tantekI'm designing the UI as if everything I have is already fully web-based, and then I'll adapt what I can to what is implemented, and incrementally move forward from there.
#Loqiimplemented is both long and includes forgettable punctuation
#barnabywaltersmight save you some parsing time, if I managed to get the structures all correct
#tantekand on that note, I'm off for a fastwalk where I'll be thinking/visualizing more about indieweb commenting UIs - and maybe sketching afterwards when I get some coffee.
#eschnouaaronpk, got it (twice in fact) : http://eschnou.com/home?tab=1, just seems I have more rendering issues, got stuff to debug now :-) thanks !
#aaronpkI think it sent two because of the in-reply-to link as well as me mentinoing you by URL
#eschnouaaronpk, makes sense, I need to put something in place to detect this and filter duplicates, but at least it works and now I just need some fine tuning.
#aaronpkcool! are you planning on displaying it as a comment?
#eschnouaaronpk, yes, it should actually be displayed already, I need to look for what went wrong with yours.
#aaronpkmaybe my markup is bad and it couldn't find the post content?
scor, singpolyma, friedcell, friedcell1, b0bg0d, josephboyle, josephboyle1, reidab and tantek joined the channel
#tantek!tell eschnou just saw http://eschnou.com/home?tab=1, including syndication of the pingback from aaronpk - well done! that's awesome that you got all that directly from parsing the h-atom on his permalink page.
#aaronpkhmm methinks I should be hosting my own image URLs of people and shrink them down to 32px or something
#aaronpkor ditch the little minicard markup and try to do all the styling in css only
b0bg0d joined the channel
#tantek.comedited /comment-presentation (+205) "add eschnou's post with a comment from the indieweb in the manually section until he says if/how it's automatically generated" (view diff)
#tantekaaronpk - not sure about the whole image URLs of people hosting thing
#tanteksome amount of caching may be good for speed and/or fallback
#tantekbut from a distributed social web perspective, embedding from each person's own site is probably better
#tantekand heck if we *all* do that, then those images are cached in the browser across sites
#aaronpkwell the main problem i'm noticing is that i'm linking to people's pics and they are all different sizes, and anything downstream doesn't know their size or how to render them
#tantekso if you load tantek.com and it shows you my avatar icon
#tantekthen when you go to a comment on aaronparecki.com, the image of me is already cached in the browser
#tantekit's the first indieweb post to display an indieweb to indieweb comment inline right in its entirety? (so much better than pingback double ellipsing crap)
#tantekand since I wrote a "local" comment on that post - it's now showing an example of how you'd display replies from the indieweb and local replies on the same post
#tantekright now it looks like they go in distinct sections