1. There is value to seemingly insignificant atoms of personal content (e.g. the stereotypical what I’m eating/doing/feeling right now) — providing context for more significant pieces of content; self reflection and the creation of new content molecules

  2. Aitor García Rey: I should write something about the unintended small interactions emerging in digital platforms eg. star a tweet to acknowledge wo. comment.

    @_aitor looking forward to reading it, I’m working on a comparison of the tangible outcomes of micro-interactions (like, favourite) across various different silos. Lots of work being done on likes.

  3. 2013 in numbers:

    • 2 days, 4 rooms
    • 43 Creators, 3 Apprentices participating in-person
    • > 13 people participating remotely, including 5 by video
    • 16 brainstorming sessions
    • 11 selfdogfooding demos
    • 11 hack demos
    • 38 active IRC participants (people who actually said stuff)
    • ≈60 people in IRC at any given time
    • 2718 total IRC messages
    • 176 wiki edits
    • 35090 net wiki insertions (new chars)

    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.

  4. Zachary Kain ☯: @BarnabyWalters Ah, thanks. I'm not really server-language savvy, so I'm thinking of using RSS + IFTTT for the grunt work

    @zakkain good plan! So are you setting up posting with POSSE on your domain? Also check out the work bret.io is doing getting indieweb comments working using no server side code, and hop on on freenode if you need any help, there’s always some friendly person there :)

  5. In reply to a post on twitter.com

    @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.

  6. I’m beginning to think that I want to store two broad categories of content on my 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:

    • short, tweet-like notes
    • (often) ideas
    • checkins
    • bits of personal data like , , sleep or other quantified self-type things
    • replies
    • photos
    • some longer written pieces
    • assorted other location data e.g. journeys, runs, walks

    Examples of content primarily defined by things other than time:

    • essay-like articles
    • experiments and tools
    • venues
    • profile data
    • contacts/people — although this is a tricky one which requires further experimentation
  7. Sandeep Shetty: # Liking Mutable Things On most silos where people can't edit stuff they've posted, you're liking immutable things. On the #indieweb, however, where content owners have complete control over __their__ content, you're liking things that are potentially mutable. One way to mitigate the problems of liking mutable things (like I do with #converspace) might be to quote the thing you liked along with your like post. #converspace #rssb #thinkingoutloud

    @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.

  8. Ben Werdmuller: Facebook bug leaks 6 million users' details. Somehow now seems like a drop in the ocean. https://www.facebook.com/notes/facebook-security/important-message-from-facebooks-white-hat-program/10151437074840766 5m 2 Another great benefit of the #IndieWeb: being able to edit typos in your status updates. http://werd.io/view/51c4e161bed7de073150079b Ben Werdmuller, Jun 21 2013 @benwerd is that an indieweb comments implementation I see there? Jovian Salak, Jun 21 2013

    @benwerd is that an indieweb comments implementation I see there?

  9. Ben Werdmuller: I don't get why you'd use markdown to blog on your own site. Markdown is useful: an easy-to-use notation system that allows you to mark up your text in a safe, fast way. Because you're never letting your users write raw code, there aren't any worries about them posting malware or exploit attempts, or accidentally writing bad markup. At the same time, simple lines and dashes are converted to valid HTML. Everybody wins. But when you're writing your own site, you don't need to worry about those things. You don't care about you posting malware or exploit attempts. (Either you want to, or you won't.) You also don't need to worry as much about bad markup - and if you're not proficient in HTML, you can install a WYSIWYG editor, like the one in WordPress. Unless you're a Dr Jeckyll who morphs into an id-like alter ego without warning, you don't need to worry about your own trustworthiness as a user of your own system. On a self-hosted #indieweb site, all #markdown does is restrict what you can do. It has a syntax to learn, just like basic HTML does, and because you actually have to keep in mind which HTML tags it uses when you write it, it's actually a little bit more complicated to remember. I like a lot of the goals of new publishing platforms like Ghost (I backed it on Kickstarter) but this feature sticks out like a sore thumb to me. I'm not at all sure this is the best writing experience on the web. And I don't see what's wrong with HTML. Updated to add: I've had lots of feedback by people who point out that they just want to write text, not HTML, which is more than fair enough. But surely this shows demand for a smarter, context-sensitive rich text editor rather than another syntax to learn. Why couldn't an editor know to start creating bullet points when you type an asterisk and a space at the beginning of a new line? 13m

    @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?