1. Has anyone ever clicked on one of those whole-page modal ads or CTAs which pop up over articles, other than accidentally? Big sites must have analytics on this stuff. I find it hard to believe that they work well enough to justify keeping them around

  2. Installed Opera for testing and it somehow set itself as my default browser without asking. Anyone know how it manages this somewhat shady settings change? Mac OS 10.9

  3. Just realised that increasing the dimensions of an element onscreen when it is hovered over creates a “natural”, visual schmitt trigger effect.

  4. I love the way browser’s consoles allow us to do maths and simple programming directly alongside mathematical webpages. This can be so much better though — the computation and experimentation should happen interactively in the webpage itself

  5. From Pokemon and Star Wars JSON APIs: “There are hundreds of websites about Pokémon but none of the data they had was consumable through an API.” Problem has never been lack of APIs but discrepancy between human-readable hypertext pages and otherwise hidden machine-readable data. Rethink your assumptions!

  6. This label on @derickr’s site is equally valid advice for both form fields :)

    The text “will not be posted, please leave blank rather than typing garbage in though” is much closer to the “comment” field than the “email” field.

    The gestalt principle of proximity rejects your internet comments! “Please leave blank, your comment will not be posted. Don’t type nonsense in though, that would be a waste of both of our time”

  7. Has anyone published research into the of URLs? Specifically interested in how people understand, relate to and interact with URLs. Hav found some talks and blog posts but not much actual data.

  8. I love @allofbach but the website is not at all optimised for actually listening to/learning about the music. A potential redesign removes extraneous clicks and puts the focus completely on the music and performance:

    Additional possible improvements: link to wikipedia article, IMSLP page (e.g. BWV243)

    Hash: SHA1

    Posting my first note over HTTPS, now at indiewebcamp.com/https level two with a self-signed certificate.

    I’ve also enabled HTTPS for Shrewdness (currently optional, will be required once I have a StartSSL cert) — if you want to add an exception, the signature is:

    Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
    Comment: GPGTools - http://gpgtools.org
    -----END PGP SIGNATURE-----
  10. Attempting to reproduce a weird, That Browser With Flash issue by opening ALL THE TABS:

    It’s like a little mountain range!

    Edit: I made so many tabs they go off the screen, and That Browser With Flash just ignores it, stubbornly insisting that there are only as many tabs as can fit on the screen. Yet another example of Firefox having Superior Prowess (TBWF is seriously fast though)

  11. Musicians+bands: please put a paypal donate button or similar on your site so that when it’s easier for people to torrent your music rather than buying copies (physically or digitally) we can still give you money. We want to give you money!

  12. @kartik_prabhu amazing work overall! This is one of my favourite parts though — the fact that fragmention comments fall back gracefully if they’re not supported on either side, and yet all the data required to present them is preserved, so future updates can retro-actively put old marginalia in the right place!

    I wonder how tricky it would be to implement this on the comment publisher side too — detecting fragmention URLs and tailoring the reply context content…

  13. Working on I’m coming to realise that there are at least two usefully distinct levels of semantic data on the web:

    There’s the basic “object” level at which microformats act, defining simple, basic-level objects like posts and people with properties like name, phone and content.

    Then there’s the level at which HTML works, marking up blocks of text and creating a tree of elements, each of which gives context to the text it contains, for example blockquote elements for containing content from another source, code elements for “computer code” (might be some space to make that more useful — who’s up for adding the type attribute to code?) and so on.

    So what? So these are the two sufficiently standardised levels at which content on the web can be made portable, and mutually understood by many parties. Any additional undefined semantics introduced by author-defined classnames and the meaning communicated by their default styling is unportable, and will be lost when that content is viewed elsewhere (for example shown in a reader or as a cross-site comment.

    So how can you tell if your content is sufficiently portable? For the object-level (microformats) a validator like indiewebify.me can be used. Strangely, there aren’t as many tools for the markup level, but one surefire way to check is to disabled CSS in your browser. Is your content still understandable using only the default styles? If so it’s probably pretty portable.