1. 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
  2. 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.

  3. “So easy is it, though many housekeepers doubt it, to establish new and better customs in the place of the old.”

    Walden, Henry David Thoreau