@voxpelli thanks for the links, auphonic looks like a great service! Certainly going to look into using that for automating stuff like audio encoding.
Soundcloud down or broken too often now. Time to implement #indieweb audio posting UI in #taproot.
@aaronpk and accepting a reply from the same UI :) This calls for cake — going to have a go at those cookie recipes you posted!
Reflecting on 2013 with my #family. Biggest things personally have been making my second #gurdy, moving to Iceland and meeting+working with all the great people over here. Lots of #indieweb and #taproot progress, including a great indiewebcamp in September.
Looking forward to 2014: more cooking, more indieweb progress, seeing more of Iceland, going to some gurdy festivals, improving hardware hacking abilities, connecting my gurdy and other devices to the web and each other.
The other detail added to #taproot: #indieweb phoning via SIP and a “Call Me” button. On desktop devices you’ll see it on my homepage in the Elsewhere section. Clicking it on a WebRTC-enabled browser will start an audio call with me if I’m logged into a SIP client.
Next: using a Tropo app as a middleman for providing voicemail transcription and local numbers, improving/providing mobile UI.
New in #taproot: latest 3 articles and location of last checkin/location post on the homepage — hopefully some useful/interesting context.
Next: mobile-focused homepage design.
New in this version of #taproot:
The local maximum has been overcome, for now. There is still much to do.
It’s already possible to use web action toolbelt to add indieweb reply/bookmark buttons to twitter.com and weave to expand POSSEd copies into full posts, but I think that’s as far as the “progressively enhance the twitter UI for indieweb support” train goes. Remaining pain points:
Pieces in place allowing a seamless transition from using twitter.com:
Pain points still to be resolved:
A bottom-up, building blocks approach to interoperability makes the barrier to entry small and the value large, as opposed to a monolithic all-or-nothing protocol approach, which demands compliance due to its implementation’s incapability of gracefully handling partial support.
Building blocks give creators freedom to implement what’s important to them in the order it makes most sense, getting positive feedback from low hanging fruit and making complex tasks managable.
Stop designing protocols. Create building blocks.