Doing acceptance #testing in a different language to your application is philosophically a good idea.

When syndicating data, the quality can be used to determine the canonical version even if the separate versions don't link to each other (example: photographer takes RAWs, gives TIFF to client, RAW is proof of provenance) #POSSE

Not drinking tea and not having cream on cream teas reduces the day to day hassle, stress and confusion of living in Devon by approximately 90%.

And the compliment of that #universallaw: the simpler the text-publishing service, the more interesting uses it’s users will put it to, provided it paves their cow paths (e.g. Twitter with RTs, #hashtags and @-replies).

Give users constraints and simplicity, see what they do, then solidify that functionality — or, from an #indieweb point of view, give yourself constraints, then pave your solitary cowpaths.

I really can't stress just how brilliant the identengine.com API is. Solves so many problems, implements so many standards, but more importantly: it is truly, truly webby. Forming a graph of a persons profiles by following rel links, then accumulating all that info is a vital building block. Great work Glenn Jones! #indieweb#web

Twitter’s “you only see replies from people you follow if you also follow the target of the reply” model is quite fascinating because it means that, within a particular community, the number of tweets you see is not directly proportional to the number of people you follow. It’s probably square or cubic, perhaps I’ll model it and see.

I love that #php now has shiny namespacing and a thriving code sharing community, but I think the heavily hierarchical namespacing practises used by some of the community (e.g. symfony components) are unhealthy.

They are difficult to memorise, relying on (often slow) IDE autocomplete, and encourage a use statement for each class. That’s pretty much a scoped equivalent of from x import * in python — not a good practise! It’s still namespace pollution, it just takes longer to write.

I am trying to use a more python–like, package-centred approach with much fewer subnamespaces. The outcome of this should be that you use the package name:

use BarnabyWalters osse;

…and then using all the classes/subnamespaces from that root, e.g: $t = Posse\Helpers::convertHtmlToTwitterFormat($s);

Brennan Novak great to see you auto–POSSEing! And pleased that you found the truncenator useful. Also check out the stuff in BarnabyWaltersPosse, there’s a more up to date version of the truncenator as well as some other syndication helpers.