Tantek Çelik

Wanna be neighbors? Downstairs from me is on sale, open house *today* from 2-4pm. Come on by Port Zero; ping me for further details (or if you don't know where Port Zero is).

Web workers of the world, take "The State of the Web 2010" survey (via @johnallsopp) http://bit.ly/bfES1G longurl @ http://surveys.webdirections.org/index.php?sid=69882

How many comments did you sharecrop on Haloscan? Whither permalinks? #ownyourdata http://j.mp/cs6qZy longurl @ http://blog.js-kit.com/2009/12/09/haloscan-is-getting-upgraded-to-echo/

never compromise simplicity for the sake of politics.

conceptualizing #DiSo 2.0: #1 personal site+shortlink domains. #2 algorithmic URL shortener. #3 hAtom store (no DBA tax - easier to maintain/backup than MySQL). #4 hAtom activity stream (DRY). #5 update notifications to PubSubHubbub (PuSH). #6 your own PuSH hub. #7 content-type-specific syndication to specific sites (e.g. text notes to Twitter, geo checkins to Foursquare, photos to Flickr, events to Upcoming, etc.). #8 reverse syndication of comments+tags+notes from said specific sites. #9 edit/comment authorization via RelMeAuth (OAuth + rel-me). #10 personal OAuth endpoint.

@deanpence you need your own URL shortener because it's part of what I see as #DiSo 2.0. bit.ly is fragile due to: 1 Libyan domain; 2 opaque database-dependent ids; 3 all the reasons mentioned in http://joshua.schachter.org/2009/04/on-url-shorteners.html

thanks @singpolyma for suggesting negative integer support in NewBase60 CASSIS lib. submitted patch had a few minor bugs: $n*-1 is slightly less optimal than 0-$n; .= is not supported in CASSIS (which must run in javascript as well as PHP), use strcat() instead; finally numtosxg() works by prepend constructing the sexagesimal return value and thus the minus sign needs to be prepended afterwards. for completeness I added negative sexagesimal support to sxgtonum() as well. updated: http://tantek.com/cassis.js

defining a phrase since @singpolyma asked: "epoch days" - the number of days since Unix epoch start 1970-001. quite useful for simple personal post datestamps. 3 sexagesimal +NewBase60 digits worth of epoch days represents over 591 years, plenty overengineered for a human lifetime of activities.

summary of inventions+conventions I had to create+build (so far) to start tweeting from my own site: #1 multi-content-type permalink URL design; #2 algorithmic URL shortener #Whistle; #3 print-safe +NewBase60 encoding; #4 ISO8601 ordinal date (+NewCalendar) functions; #5 CASSIS JS/PHP hybrid coding model+library; #6 HTML5+hAtom storage system; #7 "smart" ellipsing; #8 syndication discoverable permashortlinks; #9 item time sequential nav (Flickr inspired buttons, FB inspired arrow-key shortcuts); #10 item shortlink/permalink copy/re-use fields (YouTube inspired).

that's right @progrium, RelMeAuth (nice suggestion) works for any #OAuth + rel-me site, and enables auto-fallback with use of alternate identities for authentication: 1 user enters their site URL; 2 iterate through their outbound rel-me links; 3 if a rel-me destination is up, and rel-me links back to user's site, and has OAuth endpoint, then do OAuth authentication. Thus user links to their RelMeAuth profiles in preference order, and authentication code tries them in order. e.g. Twitter, Identi.ca, ... etc. No more OpenID server/delegate single point of failure, nor need to learn yet another XML format.

modest proposal for "good enough" authentication via your own URL: OAuth + Twitter (AKA TwitterAuth) + rel-me bidirectional identity consolidation. works for all users who enter their site in their Twitter "More Info URL" setting, and put a rel="me" hyperlink from their site to their Twitter - easier than having to write/maintain two invisible link rel="openid.*" tags to their OpenID server/delegate URLs (and having to learn what those mean/are).

contrast easy Twitter/PuSH/#OAuth APIs + examples with huge/complex #OpenID PHP libraries (cc: @chrismessina) - over a dozen classes with dozens of methods total in http://openidenabled.com/php-openid/. that's the 1.x libs (nevermind 2.x) and samples just for consuming OpenIDs. I have a lot more sympathy now for those who give up on or deprioritize OpenID support. The barrier to entry for OpenID support is far too high for independent developers.

documenting bits of tweeting from my own site. thanks @leyink for the favicon, and Twitter + PubSubHubbub (PuSH) for simple APIs easily implemented with a few lines of PHP.

if I had a Mac128 rather than an Apple //e as a kid, I'd never be a programmer today. #ipad with apologies to @al3x: http://al3x.net/2010/01/28/ipad.html

recommending http://workshopsfortheweb.com for copywriting #HTML5 UX usability http://forabeautifulweb.com #CSS3 #jQuery

"No one will be using Flash ... The world is moving to HTML5." -Steve Jobs #ipad http://j.mp/9uWJVN longurl @ http://www.wired.com/epicenter/2010/01/googles-dont-be-evil-mantra-is-bullshit-adobe-is-lazy-apples-steve-jobs/

First sunny weekend of 2010 in SF. Thanks BTW to @daveman692 and @Facebook for hosting the OWF board meeting on Friday.

Heading to Palo Alto for the 1st f2f mtg of the elected Open Web Foundation (OWF) board. What can OWF do for you?

"Mac development in the early days (circa 1983-1985) was done using the Apple Lisa ..." http://j.mp/9lFkb0 longurl @ http://folklore.org/StoryView.py?project=Macintosh&story=3rd_Party_Developers_and_Macintosh_Development.txt

no multitasking, needs a "real" computer for appdev. iPad 2010? No, Mac 1984 (Lisa for appdev). history. repeats.