tantekwhat do people here think of the UI practice on various social networks of posting "previews" of linked content? e.g. FB, Twitter, G+ all seem to retrieve and show title/summary/photo for links that you post in your content.
tantekTwitter inexplicably chose to call theirs "Twitter Cards" instead which have nothing to do with the previously Twitter launched (but now defunct) "Hovercards"
tantekc) exercise for each indieweb implementer: code to store/cache that embeddable markup in your personal post data store so that you can redisplay it without having to rerequest the external URL (has the advantage aaronpk mentioned of snapshotting the preview as of the time you posted the note)
tantekaaronpk - so the library in b) returns you the markup snippet with preview name/summary/photo - you just need to store that however you store information in your posts, so you can retrieve it from your store rather than the external URL
tantekof course the beauty of the markup snippet returned is that it would support the same format as in a) so it is completely re-usable without loss of fidelity
tantekso I'm thinking of building c) into my posting UI on my site, that is, when I'm previewing a post before PuSHing and syndicating it out, the post preview UI retrieves the link preview(s) on the server, and then shows them to me as part of the overall post preview before I hit the "Publish" button
tantekand when I hit the "Publish" button, the same logic which makes a syndicated copy to Twitter (by calling the Twitter API), and then saves the Twitter copy permalink in my data store, can also save the link preview(s) in the same data store accordingly. just piggybacking the same data store write to file call.
tantekok so I just researched what Facebook/OGP, Google/G+, IE10, and Twitter Cards do for link previews and h-entry handily covers the 80/20, *except* for rich media related properties.
tantekwith the addition of u-photo we get most of that. with (new properties) u-video and u-audio we would get all but the live streaming properties for rich media (the streaming stuff is twitter only anyway).
tantekI suppose this starts to overlap a bit with #microformats for discussion, but I wanted to discuss first within the real world use cases that the indieweb has for this stuff
tantekI'm finding that real world indieweb use cases (i.e. stuff any of us wants to implement and ship on our own sites) are a good litmus test for prioritizing/filtering such innovations
tantekI think "just use h-entry on the <body> element with a few additions like u-photo" gets us close enough to what all these sites use that we can get started with building on that and see how it works.
aaronpk!tell tantek you should follow the ##hackernews channel. turns out there are actually a lot of people blogging on their own domains still. in no small part thanks to static site generators like Jekyll
Loqitantek: aaronpk left you a message 5 minutes ago: you should follow the ##hackernews channel. turns out there are actually a lot of people blogging on their own domains still. in no small part thanks to static site generators like Jekyll
aaronpkwe should find some way to get these people more involved in the indieweb community since they are already totally eligible to come to indiewebcamp
tantekone variant of that would be a social indieweb search engine - where it only searched indieweb sites of folks you had XFN links to (or perhaps 2nd degree as well)
jedahan, eschnou, barnabywalters, scor and friedcell joined the channel