Why not to make assumptions about where your site visitors come from send #js to do a hyperlink’s job:
(That link didn’t work, obv)
Why not to make assumptions about where your site visitors come from send #js to do a hyperlink’s job:
(That link didn’t work, obv)
@anna_debenham I publish microformats2 with classic mf fallback. Also consume lots of microformats data and built some tools to help others do the same:
Lots and lots of chocolate in the office today, courtesy of Brian Suda and borgamynd.com
@w03_ what’s this one about?
@julien51 WATCH OUT! They’re trying to trick you by putting the comma in the wrong place — it’s actually only $93,000,000 :)
Discuss adding #microformats to @duckduckgo special result pages here: duck.co/topic/add-microformats-to-results
Unfortunately page has a JS error on FF Nightly :(
#TIL about Esquivalience, a Fictitious Entry. More proof that #copyright law is bad for consumers, driving organisations to compromise the integrity of their publications.
How to emulate standard #php front-controller behaviour of routing static assets statically, otherwise calling index.php using the PHP 5.4 built-in server:
// file: index.php
// Route static assets from CLI server
if (PHP_SAPI === 'cli-server') {
if (file_exists(__DIR__ . $_SERVER['REQUEST_URI']) and !is_dir(__DIR__ . $_SERVER['REQUEST_URI'])) {
return false;
}
}
// do usual front-controller stuff
Achievement Unlocked: Functional PHP by passing an anonymous function as an argument to itself
This honest and frankly terrifying short film about the side effects of 3D printing has changed the way I think about the future:
#TIL Nicola Pellow (author of the first line mode browser) was from, or at least lived in, Okehampton, Devon (WWW/People -- Pellow)
@github any chance you could add #microformats2 h-entry and #indieweb comment markup to issue pages?
Want to easily send webmentions from the command line, or from bash/python scripts? @vrypan made a neat little package to do just that: github.com/vrypan/webmention-tools
pip install webmentiontools
webmention-tools urlinfo http://waterpigs.co.uk/1000
webmention-tools send source target
Testing POSSE of issue comments to Github
Brennan Novak I generally don’t like paying anything for APIs or apps :) I make exceptions for things like @pagekite which are both extremely useful and also thoroughly good.
@sandeepshetty @pfefferle cweiske Something new to consider: Jeremy Keith added a webmention sending form to his journal entries to help people who’s websites don’t support webmention already. Being able to test and use webmention through a human visible, interactable form is a huge benefit of using HTTP form encoded data.
We can make this an even stronger case by encouraging success and error responses to be full HTML documents with helpful copy.
See also
cweiske @pfefferle demanding strictly ordered + laid out HTML makes things easier for consumers at the expense of publishers, which is a known anti-pattern. We should optimise for ease of publishing.
Also, many implementations are already parsing the target HTML for reply-contexts (e.g. Aaron Parecki (example), @jschweinsberg (example) and myself (example)), demonstrating that parsing HTML is not a significant barrier.
@benhowdle @trailedapp congrats on the launch! Great that you’re encouraging people to own their comments. Have you come across indiewebcamp.com at all, especially the work we’re doing on cross-site replying, webmentions and reply-contexts? E.G. this post is a reply on my own site to one of your tweets :)
Watch out for #python dict-based string interpolation examples which look like this:
'Hello, %(name)s' % {'name': 'Otter'}
That s
after the brackets isn’t pluralising one adorable aquatic mammal into a whole bunch of them, it’s actually part of the interpolation placeholder — the equivalent of
'Hello, %s' % 'Otter'
Note also that for some reason, python lets you put spaces between the closing bracket and the type signifying character. This can cause extremely weird bugs when the string being interpolated is also being translated. For example:
_('%(customer) shared a thing') % {'customer': 'Mr. Bean'}
If not translated, this will produce this confusing but fairly easy to debug output
'Mr. Beanhared a thing'
But if 'shared' is translated into a word beginning with, for example, d
, you’ll just get an exception like TypeError: A float is required