tantek.com

t

  1. Happy first day of spring!

    Time for some spring cleaning.
    * Delete apps you’re not using
    * Delete accounts you don’t need

    E.g.:
    * https://boffosocko.com/2018/03/19/facebook-app-purge/
    * https://indieweb.org/delete_your_account

    See and use:
    * https://indieweb.org/appaccess

    Add yourself to:
    * https://indieweb.org/app-quits
    * https://indieweb.org/silo-quits

    on

  2. There’s no such thing as free private #socialmedia.

    Either
    you pay for hosting your private data
    or someone else pays to access it
    or someone buys whole site, changes ToS (as you agreed to let them), does with your private data as they wish

    #indieweb

    on

  3. Privacy Theater: Why Social Networks Only Pretend To Protect You:
    https://techcrunch.com/2009/12/27/privacy-theater/
    by @rohitkhare

    From *2009*.

    #ownyourdata on the #indieweb before #Facebook or #DeleteFacebook

    on

  4. @overcaffeinated @RodBegbie @waferbaby #indieweb folks choose that which meets needs eg:
    https://eli.li/entry.php?id=20180314144847
    #IndieAuth
    #Micropub
    #Webmention
    #RSS
    #Microformats
    and https://twitter.com/ChrisAldrich/status/961794239163068416.
    My site #hfeed #Atom. Simple building blocks enable evolving a plurality of approaches, features, tools: https://indieweb.org/plurality

    Drop by and chat some time! https://chat.indieweb.org/

    on

  5. It makes sense to special case the [a-z] microformats2 class name segment requirement to allow numbers in vendor prefixes, since there are existing vendor/product names with numbers, e.g. (made up examples with actual (past) vendor/product names)

    h-6prime-rev
    p-p3k-special
    u-revision3-source

    on

  6. As I wrote in http://tantek.com/2018/079/t2 (https://github.com/microformats/microformats2-parsing/issues/30#issuecomment-374784404), the 'type' array must not convey any ordering semantics from the source (thus it must enforce an artificial order that does not convey anything, in addition to uniqueness per set requirements). All other uses of arrays in the parsed JSON output (children, property values, rel subarrays) already convey appropriate document order semantics.

    on

  7. Since HTML 'class' and 'rel' attributes are defined as unordered sets, we must preserve that semantic across any parsing transformations, in order to avoid introducing meaningless noise like artificial ordering which could accidentally cause a consuming application to erroneously infer and depend on such.

    The parsing spec must require uniqueness in the 'type' array accordingly, and since JSON arrays do have a defined ordering (whether you want it or not), the best we can do is to define a canonical ordering that does not imply anything about the unordered source, such as alphabetical ordering of unique h-* classnames.

    For 'rel' attributes, the spec http://microformats.org/wiki/microformats2-parsing#parse_a_hyperlink_element_for_rel_microformats already says the right things for treating them as sets, and notably does preserve source order in the URL sub-arrays for each rel key, which is intentional.

    on

  8. Consecutive dashes were never intended in microformats2 class names, only as separators between [a-z] segments per original microformats naming principles: http://microformats.org/wiki/naming#Some_Details

    I’ll make edits to capture this succinctly along with issues #27-30 (comments forthcoming), assuming no objections.

    on