#KartikPrabhukylewm: nice sharing of multiple posts with context!
#aaronpkooh I wonder how that woudl look as one of my "collections"
#kylewmKartikPrabhu: thanks! I'd like to implement some nice way to stick a citation in a regular post, so I could quote arbitrary excerpts (I think we've discussed that before). but for now it's nice the logs have a permalink for each line :P
#aaronpkI need to move the photo property inside the h-card for the IRC lines :)
#KartikPrabhucan someone please make fragmentioned reply-contexts to show that this ^ is not needed at all!?
KevinMarks_, ShaneHudson, eschnou, crossdiver, acegiak and KevinMarks joined the channel
#colintedford.comedited /WordPress (+9) "/* People using WordPress */ Much as I look forward to leaving Wordpress, I haven't yet & won't for some time." (view diff)
#tantek_!tell KartikPrabhu <p> is the wrong element for transclusion of someone else's text anyway. We already have <blockquote> for that. And it already has a "cite" attribute for referencing the source.
#tantek_AND most importantly, it already has a way of statically including the text *you saw* at the point in time of when you quoted it. So you can dynamically enhance it with some sort of JS-dynamic stuff and the cite attribute if you want. No new markup needed.
#barnabywalterseliemichel: from http://webmention.io/ “Webmention.io is a hosted service created to easily handle webmentions (and legacy pingbacks) on any web page.” — does that answer your question?
#barnabywaltersearly indieweb creators typically tried to use existing OStatus (or similar era e.g. openID, pingback) standards on their personal sites before getting fed up and simplifying them
#eliemichelbut why is h-card in front of ActivityStreams and not WebFinger?
#eliemichelI was trying to gather info about OStatus to try and implement it
#barnabywalterse.g. I tried to implement salmon integration with statusnet but never got it working, with zero help forthcoming from the statusnet/ostatus community or codebase
#barnabywalterseliemichel: h-card is a vocabulary (like activitystreams) whereas webfinger is a discovery mechanism (like rel-me)
#eliemichelI droped Salmon from my todo-list before trying to implement it ^^
#barnabywalterseliemichel: sounds like a productive decision, especially now status.net runs on pump.io
#eliemichelyep but I though WebFinger is, in its foundments, a way to give back info about ourself
#eliemichelactually they don't say they use OStatus
#eliemichelalthough their protocol is near from it
#barnabywaltersit did integrate with friendica for some time, but I think that was a project-specific collaboration rather than both impementing a documented standard
#barnabywaltersyeah, Diaspora really tried hard to use existing standards, to their credit
#eliemichel«”¯WebFinger is about making email addresses more valuable, by letting people attach public metadata to them.”¯Â»
#eliemichelSo WebFinger fundamentally is a way to give back info
#barnabywaltersthe indieweb rejects email addresses as a person’s primary identifier on the web, making webfinger not very much use
#eliemicheland it is used to give some endpoints now
#barnabywalterseliemichel: webfinger, via XRD (or some such XML format for linking to things)
#eliemichelI don't say IW should use WebFinger. I just say that WebFinger is not exactly a mecanism
#ben_thatmustbememy attempt at mobile worked for about 2 seconds before I lost signal
#ben_thatmustbemewhile i don't disagree with the idea that personal domain is better than personal domain e-mail the 3 examples for section one are pretty much the same thing said 3 times
#ben_thatmustbemeits not really much different plus you get the ability to host far more information at a web address, plus you get control over contact or not
#ben_thatmustbememy domain may not publish my contact info if I don't want it to
#ben_thatmustbemeeveryone tries to hide their e-mail address for that very reason
#ben_thatmustbeme!tell aaronpk re google domains. Know that if you register there you cannot transfer out for 60 days after you purchase.
#eliemichelmy approach was more: Everything starts with the RSS feed. Then my blog is just a feed reader configured to read that feed
#eliemichelit allow readers to load only the info that interest them
#ben_thatmustbemetake a look at http://indiewebcamp.com/Principles It may help explain some of it. The second item in there is kind of this very point. Its about humans first, machines second. not the other way around
yakker, lttlman, snarfed and joshwnj joined the channel
#ben_thatmustbemeeliemichel, its really no different than if someone makes an RSS fee that doesn't have any more than the titles and links to the articles. That sample site isn't very user centric (imo) putting just links on the main page seems silly.
#eliemichelyep but putting a list off all full articles is not really more readable
#bretcomputes just do the transform, even if you manage everything behind the scenes with machine first data serialization formats, ultimately its turning into light on a screen (or sound etc)
#eliemichelyes but doing a transform for undoing it directly is a watse of computation
#Loqiaaronpk: ben_thatmustbeme left you a message 1 hour, 53 minutes ago: re google domains. Know that if you register there you cannot transfer out for 60 days after you purchase.
#aaronpkben_thatmustbeme: I think that is true for any registrar, it's an ICANN rule IIRC
#eliemichelokey, I start to see how webmention + h-entry drive to awesome results =)
#bretthere is always going to be html for a website. how you generate that is up to you. this just takes the approach of making the html trivialy consumable by a parser
#eliemichelbut do we agree that h-entry can't be a good way to syndicate full article lists as atom does
#breteliemichel it depends on the publisher just as it does with atom/rss. xml feeds have the same issues where publihers truncate full text to get more page views
#eliemichelbut what if I just want to follow someone's posts?
#breteliemichel re following someones posts: for now just do as you always do: use your favorite reader or social network. i think the goals of indieweb style readers that barnaby and ben are developing is that you follow people by adding that persons domain name, with the added benefit that all of their social networks are identified on the site and can be used as auxiliary data sources. You follow people by their domain, not xml feeds. No more hunting
#bretaround for rss buttons or unlisted feeds. Just point to a personal domain or social network profile url.
#bretsince its actually supposed to be useful, i'm sure atom/rss feeds will be supported
#bretthe goal is to follow people, not feeds. thats what made facebook and twitter so popular
snarfed joined the channel
#ben_thatmustbemeI think elimichel is pointing out the bit about not really getting a full history if you just follow their hfeed. It doesn't go all the way back, whereas rss/atom tend to go back much farther since you aren't concerned about display
#eliemichelmmh yes but I still want to be able to read Foo's articles in my feed reader
#tantek_not any more. RSS/Atom tend to be bulkier so I for one have fewer items there than on my home page.
#eliemichel"following Foo's domain name" is too abstract for that purpose
#bretben_thatmustbeme in my experience, that is never guaranteed with a feed
#aaronpkin my experience atom feeds tend to be much shorter, like 5 or 10 items
#tantek_in general the data quality in feeds is crappier. fewer items, less accurate, truncated, all kinds of garbage.
#aaronpkat least with an h-feed you can look for a rel=prev link and follow that for past items
#LoqiKartikPrabhu: tantek_ left you a message 4 hours, 36 minutes ago: <p> is the wrong element for transclusion of someone else's text anyway. We already have <blockquote> for that. And it already has a "cite" attribute for referencing the source.
#ben_thatmustbemei think h-feed just makes more sense. in the "follow ben.thatmustbe.me" it already knows what page to load, no need to go there and then try to find the atom/rss feen
#KartikPrabhuthe nav links at the bottom have rel-feed links to h-feed pages. In fact Bridgy already consumes this to find original posts from POSSE post copies
#KartikPrabhutantek: about the fragmention quote post. I agree, it is grossly over-thinking quotations and fragmentions too. In fact it would be much easier if your post publishing software saw a fragmention in the post and just fetched and inserted a <blockquote>
#eliemichelbut I'd like to "say" that I mention sites
#LoqiKevinMarks: tantek left you a message 12 hours, 21 minutes ago: I encourage you to add a subsection for kevinmarks.com here and add your use-cases: http://indiewebcamp.com/template#Use_Cases
#tantekKartikPrabhu: typically it's a result of ignorance/naïveté. Those who do not know about existing standards are doomed to reinvent them.
#eliemichelsometimes they know about it but it seems overcomplicated to them
#KartikPrabhutantek in this case pf fragmention+quotes, those who knew the standards are doomed to reinvent them
#tanteke.g. that "hacking paragraph" post - clearly the author was so completely ignorant of <blockquote> that they didn't even mention it in their post!
#eliemichelbut finally they end up with a more complicated solution…
#KartikPrabhueliemichel: I don't think it is "over complicated" but "unfamiliar"
#tantekeliemichel: the "end up with a more complicated solution" is usually an indicator of lack of expertise/skill/practice at designing standards. AKA newbie outcome.
#KartikPrabhutantek: hmm you really think the author did not know about blockquote?
#tantekKartikPrabhu: occam's razor, ignorance rather than ignoring
#eliemicheltantek: that's exactly what I intented to mean ;)
#tantekto put it another way, designing *simple* standards is *very hard*
#tantekand typically requires failure and iteration :/
#KartikPrabhutantek: you mean Hanlon's Razor: "Never attribute to malice that which is adequately explained by stupidity."
#tantekgRegor`, KartikPrabhu what's even funnier about that p[href] proposal is that "href on every element" was one of the "features" of XHTML2. And I doubt the author even knew that either.
#tantekdate on the wiki is correct - 2014-10-11..12
#tantekrather than what I wrote above. 2014-10-10 is CyborgCamp (also at MIT, but at Media Lab)
#tantek.comedited /2014/Cambridge/Guest_List (-64) "/* Official Guest List */ move venue capacity to Participants section to bring count closer to where people add themselves, update capacity to 48 per sandro confirmation of venue, and recount signed-up and remaining numbers" (view diff)
#sandroI thought the camp was Friday + Saturday (Oct 10, 11). Am I confused or has that changed? No one else has reserved any rooms in the building Sat or Sun; Friday is the only contended day.
#snarfed(aaronpk: summary: the only explicit way we have to differentiate posse tweets from mention tweets is u-syndication, or *maybe* permashortcitation etc (debatable), both of which have extremely low adoption among bridgy users)
#snarfedaaronpk: exactly! and those both have low adoption among bridgy users
#snarfedto be clear, this is entirely a bridgy product/policy choice. technically, we can implement anything we want. it's just where on the tradeoff i've come down so far. definitely open to changing it in the future.
#tantekaaronpk, snarfed, no you can tell the difference because POSSE tweets come from a Twitter profile that the original site has rel=me linked to!
#snarfedtantek:true! good point. it's only a partial solution - KevinMarks has complained about bridgy interpreting non-posse tweets of his as posse - but still, it would definitely help. it's a good feature request.
#snarfedtantek: i'm not sure it is. like i said before, it's a faq i need to write up, but i've procrastinated because the tradeoff and decision is a bit complex
#snarfedagain, you're right that rel=me helps distinguish between different people, but that's actually the minority case. the common case is a tweet from the same author that *mentions* the post, but isn't a posse of it.
#snarfedhence using u-syndication/PSC to identify posse tweets, which i'm reluctant to do since adoption rates are low, so it would muzzle responses for lots of users
#KevinMarks_I don't mind you replicating my non-posse tweets back as comments BTW, it's just weird when the responses are replicated and the tweet isn't
#tantekKevinMarks - how about a 24hr threshold - would that work for you?
#tanteki.e. any tweeting you do of your own posts more than 24hrs after you published your posts would be treated as *comments* on your own post rather than POSSE copies
#KevinMarks_I think so. May miss some potential comments
#KevinMarks_Also, it would be nice if bridgy embedded the tweet the first time it was faved/liked
#tantekwhat do you mean by "bridgy embedded the tweet"?
#KevinMarks_See that post, where it shows the fav/likes but not the tweet that got them
#tantekwhich should be also published on <a href="http://techcrunch.com/2013/06/09/how-apples-ios-fragmentation-problems-distort-design-thinking/" rel="syndication">TechCrunch</a>