Thinking of making a #taproot listener which detects slashtag use and puts everything after the slash into a small element in a new paragraph. #todo

Really Google? em to embolden search terms in results listings? #html

pcntl_wait($status); //Protect against Zombie children

Every now and again the otherwise banal PHP docs make me laugh.

Cross-browser selection UI injection flow:

1. Listen for mouseup on body
2. When triggered, let s be window.getSelection()
3. If s.isCollapsed === false, return
4. Else, let r be s.getRangeAt(0)
5. Create a new element e
6. Call r.surroundContents(e)
7. e.innerHTML and e.textContent now return useful values, and e’s coordinates can be used to inject UI into the page

To resolve: what element should e be? Or more accurately, what display property should it have? Possibly inline-block (inline mucks up if selection is across block elements, block mucks up selections within text nodes)

New stuff: Web Action Hero Toolbelt and <action> markup on individual note pages. #webactions

We have a #webactions Hero Toolbelt config UI!

Now onto the actual meat. Most of this was already implemented in my fork of #indieweb reply, I just have to tidy it up and add in the <action> shim.

I was going to spend this evening working on #webactions browser extension, but I think it would be better spent providing a #backup/data export utility for fellow ex #diaspora users.

From my initial researches, it looks like /u/username.json is the best bet, as it gives a JSON array of all posts written by username, along with like and comment data. It accepts a max_time=timestamp query param, and a _ query param, the function of which I am not sure of.

To iterate through all the pages of posts from a certain user, start with their profile URL w/ .json tacked on the end, fetch all the items, get the datetime of the last item, convert that to a timestamp, fetch the same URL with ?max_time=timestamp, repeat until an empty array is returned.

Can any other #diaspora users (or fellow former users) verify that, on exporting your content (Settings -> Download XML) posts are NOT included.

I have User, Aspects, Contacts and People, but the Posts element is empty (<posts />). #indieweb #ownyourcontent

I wonder how common it is for HTTP APIs actually support PUT to a collection to replace it? Combined with the Robustness Principle it seems like a powerful tool for data migration #ownYourData #indieweb

Wow, exporting my DB of tunes (for migration into the shiny new system) as #YAML almost results in valid #ABC!

-
  TUNE_ID: 1
  T: Bourree De Brand
  M: 2/4
  L: 1/8
  C: Trad. French
  N: Bourree from France
  K: G
  ABC: |-
    d>B GB|c3g|f>d ef|ga bg|d>B GB|c3g|f>d ef|g4:|
    |:c2e2|g=fd2|e=fe2|ded2|cB AG|c2e2|g=fd2|e=f/2e/2 dB|c4:|
  words: 
  genre: folk

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);

Question: What #HTTP Status code should I use for “You haven’t provided enough/correct information to carry out that method”? Currently I’m thinking 422 Unprocessable Entity.

Context: POST request to a list resource for the creation of a new sub-resource.

Learning new trompette patterns with Gregory Jolivet, and decided to try to evolve a micro syntax for representing them in notes, so I can add some SVG or Audio-API magic afterwards.

1 4 1 3 1 4 1 3 1234 1234 1234 1 3

And a variation: 12 4 1 3 12 4 1 3 1234 1234 1234 1

Rolled out usage of the menu element on #taproot. I’m looking forward to more browser support for HTML context menus, that will really open up the possibilities for cross-browser extensions

sigh another piece of content ruined by over zealous XML parsing and misguided overuse of rel=nofollow

Just pushed a load of #taproot changes to auto-tagging which should make structured, tag–based querying of notes way easier.

This note should be tagged with mention, reply, quote and location as it contains all of that data.

Some Test Quote with a mention in

New on #taproot: Notes tagged with review get h-review added to their container class string. Not yet sure how to optimise e-description and p-name yet. #microformats