1. fraying just to the first episode of fertile medium and really enjoying it!

    Question: what is the context if you reply to something someone’s said on your own site, as a self–hosted reply (e.g. this one of mine, cross-posted here)?

    In an environment where everyone hosts their own comments, what happens to the their turf/own turf thing? Or is it more of a question of how the user agent in use displays interlinking content (and what blocking tools it offers)?

  2. Aral Balkan: Sexist? Want to learn PHP? We’ve got just the book for you: SexyPHP: A Fun Way to Learn Object Oriented PHP http://t.co/nz1650vr

    aral hideous. That makes me more embarrassed to be a PHP dev than all the bad rep it has as a language. And they're teaching SVN! It gets worse :(

  3. superfeedr: @BarnabyWalters Ha! I tried to log in with the hopes of maybe being able to leave a comment :) You should put a #subToMe button too!

    superfeedr self-hosted comments accepted via Pingback :)

    I tend to prefer to let users inject buttons/UI for the services they use rather than force buttons upon them (e.g. using Indieweb Reply as per Web Actions), but looks like already does a good job of that so I might add one

  4. superfeedr: @BarnabyWalters Thanks Barnaby :) [Also, I could not log into your site with indieAuth :/]

    superfeedr yeah, there’s a weird bug where logging in only works the second time round — I haven’t fixed it yet as I rarely have to log in! At the mo there is little benefit to others logging in but I may add private content/collaborative features in the future. Crowd-sourced typo fixing FTW ;)

  5. Christopher Aliotta: SOCML: A standardized social media data standard Christopher Aliotta Posted on February 11, 2013 I recently posted a proposal for a “Federated Social Network Data Standard” on the groups Wiki. I admit, that I have not searched the web thoroughly with respect to other initiatives like this; however, given the superficial research I have done, I have come to the conclusion that there are no open dialogs currently on this topic. Over the next couple of days I will begin posting proposed technical specifications for the standard. I would like for everyone to contribute feedback and make suggestions/modifications. The solution I am proposing is simple: we need to standardize social media content such that independent developers can create their own services that can share and aggregate data under a common standard. Much like the RSS format, this data standard should be open and free, not encumbered by patents, and be easy to implement. I have posted more here: http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SOCML_Proposal http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SOCML_Standard http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SOCML_Technical 3 Comments | Leave a Comment | Category Uncategorized

    Hey Christopher,

    I have some questions.

    Firstly, who are you? Have you worked on any social-web related projects before? Do you own your identity on the web (i.e. have a personal URL)? Do you post content under your own domain? Do you actively encrypt many of your communications?

    If not, with what authority/experience/motive are you proposing a “standardized standard” for social data? If you have not put effort into building and using your identity on the web, why should any of us who have care about your proposal, as it is unlikely to be relevant to the actual problems faced by people trying to implement this stuff?

    Secondly, why is your wiki username socml? Making your username the name of the thing you’re proposing strikes me as odd, if not slightly arrogant.

    Thirdly, have you heard of activitystrea.ms? Judging by your admission that you “have not searched the web

  6. Emil Björklund: Take a look at the diagram I just retweeted. Ambiguous date formats annoy me... Just use ISO, please. It's easy: falling granularity, Y-m-d.

    @thatemil RRRR yes, ambiguous date formats are so stupid, especially when they’re on tickets (british rail, I’m looking at you)

  7. Pushed lots of note UI updates to today, including porting almost all the to Backbone. Still :

    • Improving location UI: improve cancelled state text, fix located state
    • Make a view for note lists, inc. event handling like add new note to the list when it’s posted from the dialog. This will also minimise the number of requests.
    • Make the backend auto-add hashtags to the note tags property. It should have been this way all along.