#tantekkevinmarks, *just* got https support for autolinking youtube (and vimeo) coded but I'm getting kicked out of starbucks and will need to test it at next location.
#tantekended up writing a bunch more cassis common code
caseorganic, kylewm, ozten2, adambrault, michielbdejong, _6a68 and snarfed joined the channel
#kylewmKartikPrabhu, tommorris: I made a couple of very small tweaks to get mf2py working in Python 3.3.4 (but backward compatible with 2). Would that be of general interest?
#barnabywaltersinteresting, Taproot treats any mention as only being of one relation type, i.e. it is either a mention OR a like OR a reply OR an rsvp etc
#acegiakbarnabywalters: I think we were discussing this a while ago but I'm not sure if it made it to the wiki
#acegiakis a h-entry a single verb or a single object with the possibility of multiple verbs attached?
#acegiakthings like tumblr and twitter seem to display an entry as the second
#barnabywaltersacegiak: rather, does it make sense for something to be both a like and a reply? how should that be displayed?
#barnabywalterswhat about between a repost-with-conent and a comment?
#acegiakin mine it's assumed that the h-entry is the CONTENT and the verbs are just attached
#acegiakthe reason I went with that is because if those verbs are separate entities then you need to have at least multiple anchors pointing to the same endpoint one for each verb
#acegiak^ that shows that there is the div which tells you the relationship between the post on my site and the post on yours in two ways: visually by having hte phrase "liked reposted and commented" in text but also because there is the div which has the verbs as mf2 classes like u-like and h-cite and p-in-reply-to
#barnabywaltersacegiak: I disagree that like/repost/comment are just verbs — they’re fundamentally different interactions with different structures and presentations
josephboyle joined the channel
#barnabywaltersI did start to document some of the inconsistencies and similarities between different silo interpretation of these common microinterations
#barnabywaltersI’ll try to dump it into a table on the wiki later on
#acegiakI agree that they have different structures and presentations
#acegiakbut to repost something or to like something or to comment on something are all actions that a person does to a piece of content
#acegiakthey're all content directed transitive verbs
#acegiakthat's the question at hand here: does 1 h-entry = 1 action OR does 1 h-entry = 1 piece of target content
#barnabywaltersacegiak: current implementations and display conventions seem to indicate 1 h-entry = 1 action
#barnabywaltersI’d say that also maps better to action UIs — e.g. there’s usually a button for each different actions which performs that action when pressed
#barnabywaltersrathe than a set of checkboxes and a “Post all” button
ttepasse joined the channel
#acegiakI agree that it makes better sense semantically
#barnabywaltersso 1 button = 1 post (h-entry) = 1 mention = 1 action makes intuitive sense to me
#acegiakI think the confusion for me then comes from the slightly blurry lines between comment post with just hyperlink ~ comment post with full h-cite ~ repost content
#acegiaklike h-cite without a comment kinda just seems like a repost
#barnabywaltersso for me the difference between a reply + reply context and a repost (optionally with comment) is that a reply is explicitly •in reply to• the other content, i.e. makes no sense out of context
#barnabywalterswhereas a repost makes sense on it’s own. it isn’t replying to the original content (i.e. shouldn’t show up in it’s comment thread) but rather is a syndication of the content
#barnabywaltersa reply is a response, a repost is a full-blown post
#barnabywaltersi.e. you might choose not to show replies on your homepage feed (as aaronpk does) whereas reposts would be shown
#barnabywaltersthen a like is the most minimal possible sort of response — no content, just a url which is “liked”
#acegiakto explain where I'm coming from on tumblr the reblog+comment is used both as a way of replying to that content and as a way of providing commentary on it to be displayed to the commenters audience with the content
#acegiakinterestingly I think tumblr is trying to encourage users to post replies as a different kind of data to comments but often tumblr users don't do this because their replies are often open
#acegiakso they technically address the original poster but are intended to be seen publically
#barnabywaltersinteresting, okay — so a tumblr reblog+comment is more closely related to other silos’ comments rather than reposts
#barnabywaltersI didn’t know tumblr did actual comments, I thought tumblr users managed threads themselves within posts
#acegiaktumblr users pretty much manage threads because they don't like the "reply" structure tumblr has? any reblog post in a chain has a "comment" text field which by default has a stack of blockquotes in it which contain the content from all the previous comments entered
#acegiakwhereas the "reply" button creates a new post-ish sort of thing which is kind of awkward
#acegiaka tumblr reblog stack is pretty much analogous to a reply chain in an email
#barnabywaltersacegiak: this sounds a good silo UI mistake to learn from — how are the new post-ish sort of things awkward? do you have an example somewhere?
#acegiakI don't have an example at hand because I don't usually use it and I don't often see it used but I'll try generating some screenshots tomorrow
#acegiakone of the biggest reasons for low adoption is readily obvious: not all posts can be replied but all posts can be reblogged and commented
#barnabywaltersso why can’t all posts be replied to? can replies not be replied to?
#acegiakthe reason for that on tumblrs end is to do with publically directed vs privately directed communication
#acegiaktumblr considers a reblog and comment to be a public broadcast even though often these messages are directed at particular people
#acegiakso a reply can be public or private but they're semantically considered to be targetted at the user they're replying to
#acegiakso therefore some kinds of content are considered to be invitations for privately directed replies eg "does anyone know how to get gum out of shoelaces?" whereas some are not ie photos of a sculpture
#acegiakso there's not just a difference in whether the content is publically or privately visible but also the scope of the targetted audience
#acegiakso that's the reason that they have those structures
#acegiakwhat's interesting is that tumblr's users at least would rather have fewer simpler structures and use those in complex ways than have more complex and semantically meaningful structures that take slightly longer to navigate
#acegiakno where near as pretty as your whole system
#acegiakI'm thinking of makign the citation and comment boxxes toggleable rather than just having it so you clear the boxes out to not do those actions
#barnabywaltersacegiak: well, I don’t have native reposts or likes yet :)
#acegiaktrue bt I guess that's why it's good to have these sorts of discussions early
#barnabywaltersI was thinking of having a cache for each HTML page fetched with a really long TTL, which gets updated by a superfeedr HTML subscription
#julien51barnaby this is a great piece of news! I'm more than excited to help you
#julien51do you currently fetch feeds "as the page" loads?
bnvk joined the channel
#barnabywaltersjulien51: at the moment yes — fetched in parallel with some HTTP caching, but it’s not very effective
#barnabywaltersI think the HTTP caching actually interferes with cURL’s parallel requests too
#julien51not only it is not effective, but it's probably considered harmful for the web :)
#julien51you could of course cache stuff, but I guess the first question os what is "stuff"
#julien51and then, even caching will be frustrating
#julien51the benefit of your approach is they ehtings are up to date no matter what, even when/if they're slow
#julien51if you start caching, things will be faster to load, but they'll also be old
#barnabywalterswell, the reader currently only reads microformats2 content, and the smallest unit of content which is fetched is a feed page, i.e. an HTML page with a bunch of h-entries on
#julien51caching is a good idea as long as your invalidation is smart
#julien51again, if you cache stuff even for 15 minutes and I publish something the second after you cached things, you'll have 14 minutes till you see my content
#tantekbtw barnabywalters - not sure if you saw but my present to all the rest of you - https embedding support added to auto_link in CASSIS (e.g. for youtube and vimeo URLs)
#barnabywaltersit seems a little strange to refer to “status messages” once on the homepage, then “notes” consistently everywhere else. also “articles + status messages” doesn’t really cover the richness of indieweb articles, notes, photos, events, music, etc.
#caseorganicbarnabywalters: You mean multimedia? :)
#tantekcaseorganic, I tweaked the intro/definition of Generations a bit to fit with the page name. still left in a reference to "barriers" so that wouldn't be lost. Please take a look: http://indiewebcamp.com/generations
#snarfedtantek: yes and yes. fully correct (native) posse of twitter replies, RTs, and favs, and FB comments, likes, and event RSVPs
#jonnybarnesok, so if this is possible then I'll have to rethink how I store and process webmentions. Given that a source url should be a unique permalink, could someone write a note 'in-reply-to' two of my notes and send me two webentions, or can I assume a one-to-one mapping of target and source URLs?
#snarfednot tested enough in the wild yet, but i plan to advertise as soon as i've written docs
#tanteksnarfed. wow. that's going to be amazing. even fewer reasons to use silo UIs
#jonnybarnesis confused why aaronpk isn't an op anymore
#snarfedjonnybarnes: not a one to one mapping. afaik an h-entry can have an arbitrary number of in-reply-to, like, repost, etc links (and send webmentions to each one)
#jonnybarnessnarfed: yeah, currently in my code I'm assuming that if I list all the webmentions a particular source will only appear once
#jonnybarnestantek: someone replying to me and someone else in the same note is fine
#jonnybarnesthat wouldnt mess up my assumption that in my list of webmentions a particular source url will only appear once
#tantekthey might be replying to two of your posts too
#jonnybarnesI'm not entirely convinced thats a valid assumption, but I think any exceptions would be rare edge-cases
#snarfedjonnybarnes: i handle these less-common cases by filing issues (or putting them on my todo list) but not doing them until they've actually happened a few times
#tantekKartikPrabhu - yet another article yearning for a mythical "next social network" that doesn't get that the web itself is "a network that is disrupting itself"
#KartikPrabhuon the diagram: as I read it the current triangle seemed to represent number of people involved in a generation. SO most people would be gen4. One could also make a conjugate triangle that shows technical knowledge needed. So Gen1 would be most technical but Gen4 would be common non-tech folks
#caseorganic.comedited /generations (+534) "/* Generation 1 IndieWeb */ Rewrote text to focus on introducing a Gen1 to IndieWeb concepts as an individual" (view diff)
#tantekinteresting, Twitter login just broke for me
#tanteklogin appears to succeed and then I get "Something is technically wrong."
kylewm joined the channel
#caseorganicKartikPrabhu: can you sketch that diagram? happy to make it
#KartikPrabhuthe discussion on the comment section seems to be missing the point entirely (nothing new) with a lot of people proclaiming the superiority of a static html only site
indie-visitor joined the channel
#cweiskethe problem with such attacks is that the pingback receivers try to verify the pingback
#caseorganic.comedited /Main_Page (+107) "/* Homebrew Website Club */ Experimenting with subtle background colors to highlight different sections of the front page for increased readability and focus" (view diff)
#skinnyinstead of the infinite loop, it should time out and give you common causes of a hang and a link to github to file a bug if you can't figure it out
#tantekskinny - there have been outages at major sites today - it's one of those days
#aaronpkit's super awesome. i can't wait to drink another coffee so I can put it in the app!
ozten2 joined the channel
#KevinMarksI have it on my ipod, and I shoulda dd a coffee
#KevinMarksthat last link is one take on a DNS alternative - note how it reinvents XFN halfway through
#KevinMarks(the easiest way for me to send an image link to this channel is to tweet it. I should fix that)
#acegiakok so here's a new problem with silos: apparently my highschool myspace page is back from the grave. it makes me look childish if you find it when you google me and I have no way of getting access to that accound now
#acegiakyo are we documenting the discussion around whether h-entries are actions or objects anywhere on the wiki? cause barnaby and I had a big discussion about it last night
#caseorganic.comedited /Main_Page (+157) "Added background colors to some sections. Consolidated previous indiewebcamps into a row of images to save space and clean up page." (view diff)
#acegiakis 1 h-entry = 1 action (like/repost/comment/reply) or is 1 h-entry = 1 piece of target content (with potentially multiple actions to that piece of content in the one h-entry)
caseorganic joined the channel
#acegiakbarnaby was making the point that logically and semantically it makes sense to have 1 h-entry = 1 action
#acegiakbut we know that many silos don't display like that
#KevinMarksmicroformats do let you mark up multiple overlapping things in one place without duplication
#KevinMarkswhich is an advantage, but does make for possible serialization issues
#acegiakthe reason that its so odd to me is tumblr is my primary silo and the "reblog and comment"(wherein the comment is often an open reply) is so ubiquitous that having multiple entries in the stream for that seems odd