1. Ben Werdmuller: Government - the last great gatekeeper - is ripe for disruption.

    The first is to publicly declare the jurisdiction in which you live, and in which your data is hosted. That way, people can make an informed decision about how to communicate with you.

    That’s a really brilliant idea. Maybe link the brand names to their tosdr.org pages too.

  2. Every now and again I wonder if the same sort of fandoms which Adventure Time, My Little Pony et al have now would have arisen around things like The Clangers and Captain Scarlet if web culture had been as evolved (or even existed) in the 60-70s as it is now.

    Would people cosplay as Jones the Steam, post videos analysing the character development in The Herbs, communicate using Noggin The Nog reaction faces and write erotic Portland Bill fanfics?

    A bearded viking-esque guy in a pointed hat with safety covers drinks some ale, then spits it out in surprise and look to the right.

    Actually, don’t answer that.


    Spit-takes are better with ale and viking helmets. Wait, no. Everything is better with ale and viking helmets.

  3. I just faked having a task queue for note posting tasks using Symfony HttpKernel::terminate() and it was the easiest thing ever.

    Instances or subclasses of HttpKernel have a terminate($request, $response) method which, if called in the front controller after $response->send(); triggers a kernel.terminate event on the app’s event dispatcher. Listeners attached to this event carry out their work after the content has been sent to the client, making it the perfect place to put time-consuming things like POSSE and webmention sending.

    Once you’ve created your new content and it’s ready to be sent to the client, create a new closure which carries out all the the time consuming stuff and attach it as a listener to your event dispatcher, like this:

    $dispatcher->addListener('kernel.terminate', function() use ($note) {
        $note = sendPosse($note);
        sendWebmentions($note);
        $note->save();
    }
    

    Then, provided you’re calling $kernel->terminate($req, $res); in index.php, your callback will get executed after the response has been sent to the client.

    If you’re not using HttpKernel and HttpFoundation, the exact same behaviour can of course be carried out in pure PHP — just let the client know you’ve finished sending content and execute code after that. Check out these resources to learn more about how to do this:

    Further ideas: if the time consuming tasks alter the content which will be shown in any way, set a header or something to let the client side know that async stuff is happening. It could then re-fetch the content after a few seconds and update it.


    Sure, this isn’t as elegant as a message queue. But as I showed, it’s super easy and portable, requiring the addition of three or four lines of code.

  4. Ben Werdmuller: Indieweb video test

    @benwerd nice one! I’m currently working on video post-by-email. It almost worked here, next time should work flawlessly.

    The nice thing about using email to post videos is that it’s asyncronous — I can send the email and then go do something else, instead of having to either wait for it to upload or do the “if I switch apps now will it stop uploading argh what do I do” dance.

  5. Congratulations to all my friends who got into university, and congratulations too to those who decided to take a different path. You’re all awesome :)

  6. Aral Balkan: Deleted tweets shouldn’t be deleted; they should be shown as deleted. The content is already out there. It is the _intention_ that matters.

    Aral Balkan there’s been a lot of discussion recently about deletion of content — some documented here: indiewebcamp.com/deleted and indiewebcamp.com/POSSE#Delete

    E.G. if I’ve replied to one of your notes/tweets and stored a reply context so even if your copy goes down my content still makes sense, but you delete the original — should I delete it, devaluing my own content? Should I mark it as changed or deleted?

  7. Seb Lee-Delisle: So @StraightPrideUK thinks that publishing answers to interview questions is harassment. I don’t think they understand what harassment is.

    @seb_ly also kinda hilarious that they threaten to “print out” reposts. Tempted to alter my print styles to give them a little surprise…