#indiewebcamp 2013 in numbers:
Most counts either manually from the wiki or scraped from the IRC logs, which are surprisingly nicely marked up.
I received over 20 mentions via both pingback and webmention — I’d love to hear how many others received. Likewise, if anyone has personal stats like LOC or commit counts, please leave them in the comments!
Does anyone who was there IRL have any other stats e.g. amount of food/drink consumed? Total bandwidth/electricity usage would also be awesome to know.
@zakkain at the moment everything I post is a note or an article, both of which get POSSEd to twitter automatically by my server and then to Facebook manually if I want. Delegating to an external service, even if it’s one I manage, is probably a good long term solution, but I always want to get the syndicated URL back on my site which complicates things a little more.
I know others are having success using IFTTT for POSSE.
I’m beginning to think that I want to store two broad categories of content on my #indieweb site, content which is defined by the time it occurred/is published and content which is primarily defined by some other attribute.
Examples of content defined by time, which at the moment I’m using notes for:
Examples of content primarily defined by things other than time:
@sandeepshetty that’s the reason for reply contexts — dealing with content which changes or goes away. If you store the reply/like context then your copy of the data is always the most valuable, most complete. Otherwise it’s the copy shown on the remote site.
@benwerd is that an indieweb comments implementation I see there?
@benwerd I use markdown for initial authoring purely for speed, esp. when typing on mobile devices. After that I just edit the HTML. I’ve yet to come across a WYSIWIM editor which satisfied my semantic, well-structured HTML needs, any suggestions?
Battle for the planet of the APIs by Jeremy Keith — nice piece of writing, it’s worth pointing out that Twitter still includes rel=me links back to homepages, but is increasingly wrapping them with t.co, making them fairly useless.
Whilst I admire RSS as a rallying cry for the openness of data on the web, I don’t like it much, mainly due to it’s DRY violation. microformats2 is the better solution.
.h-entryis better off where you’ve got
.idno-entryso then the author
.h-cardcan be scoped into the entry
.h-entryto explicitly declare authorship
.h-as-*on the same element as
.u-urlwhere you currently have