1. Tags and categories have different connotations. To me, tags are community, collaboration, flexibility, fuzziness, visibile metadata. Categories are authority, rigidity, structure, taxonomy. Tags can be found inside content (), categories are separate, controlling entities. Content owns tags. People own tags. Categories own content. Authority owns categories.

    Beware of vague naming — some software mistakes one for the other (e.g. Mediawiki categories are in fact many-to-many).

    The organisational technique used doesn’t only have technical and usability implications, but social and philosophical (or pseudo-philosophical?) ones.

  2. Erin Jo Richey: @BarnabyWalters Tags provide bottom-up structure and information architecture, categories provide top-down structure and IA.

    .Erin Richey my reasoning is that tags are something you add to content, whereas categories are something you put content into. Tags -> content -> categories — so categories are higher up in the pecking order.

  3. (Thoughts directed @boagworld)

    A hyperlink that uses just a URI as the link text implies linking to that URI, e.g. boagworld.com implies a href of http://boagworld.com

    So when referring to a resource contained on a domain, it’s misleading to use just the domain as the link text, and much clearer to include some extra words to define what the link is linking to, e.g. some post on boagworld.com

    It’d be really interesting to do some testing to see if this is just a problem with people who understand URIs or if it applies to everyone.

  4. Decided to go completely plaintext for personal document storage.

    • Documents: HTML5/Markdown
    • Unstructured Data: JSON
    • Structured Data: CSV/JSON

    So I’m looking for QuickLook plugins to make dealing with them easier. [QuickJSON](https://github.com/joh