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
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
adamstrawson lookin’ good! How about some rel=me
goodness on those profile links? Helps great tools like identengine.com (⇐ has cool API) exist
aral yep, one for every page view and one each time I leave a page (http://aral.tripod.com/bin/exit/exit_page?q=
). Must of had pop up blocker turned off for some reason.
Doing a mass find-and-replace operation on the Perch Blog app so I can have more than one running at the same time. If you want to do something similar, here are the strings you need to replace:
blog
⇒ yourName
Blog
⇒ YourName
perch_blog
⇒ yourPrefix_yourName
PerchBlog
⇒ YourName
And then obviously rename the .class.php
files and activate as you would any other app.
I finished off the #OSM Nominatim geocoding. Tack .json
onto the end of this URL and have a look in the tags
array for goodies. h-adr and h-geo coming soon.
Also RE twitter syndication UX: with self hosted notes we have the chance to make a really robust threaded/branched conversation model via rel
values, something @twitter lacks /cc Tom Morris #indieweb
Amazed at #HTML+, which had scribble
and audio
form input elements! http://www.w3.org/MarkUp/HTMLPlus/htmlplus_41.html
lkdto how about rel=me
on all your links?
Congratulations on thesession.org’s new release Jeremy Keith! Looking great, and it’s nice to see hentry
on the activity feed :)