1 min read
Has it been 2 years already? Time flies when you're +1'ing
[oh and the cake was delicious..]
Originally shared by Fred Gilbert
Happy second birthday +1 and happy donut day to you all! I hope y'all get a chance to pick up a free one at Krispy Kreme :)
1 min read
I was talking to Brett Slatkin about authorship and he mentioned the Google Consumer surveys offers an A/B image survey that would be perfect for Authorship profile photo optimization.
You also get geographic/demographic breakdowns so I suspect that it's a good deal more informative than the OK Cupid bestface system.
2 min read
Happy to see OAuth support for CalDAV. Still sad that it's always going to be saddled with legacy vCalendar issues.
Both CalDAV and CardDAV suffer from their history and badly need redesigning. Not much has changed in the 10 years since I was hacking on libical. I mean, consider the following CDATA chunk from the RFC. No one should need to parse/generate this ancient format. It's complicated, finicky and plain awful.
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
BEGIN:VTIMEZONE
LAST-MODIFIED:20040110T032845Z
TZID:US/Eastern
BEGIN:DAYLIGHT
DTSTART:20000404T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20001026T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20060206T001102Z
DTSTART;TZID=US/Eastern:20060102T100000
DURATION:PT1H
SUMMARY:Event #1
Description:Go Steelers!
UID:74855313FA803DA593CD579A@example.com
END:VEVENT
END:VCALENDAR
Maybe I should standardize SnmpDav? At least it has XER which would make it slot into XML without the ugliness above.
In any case I hope that a new calendaring standard emerges from this muck that is more developer friendly.
1 min read
truth:
Another option is to take a hard look at how the accident actually happened, treat the engineers involved with respect, and learn from the event.
1 min read
My local electric utility PG&E has a low tech solution for their Smart meters. If you want to activate the remote sensor you fill out this form and wait 5 days for your "HAN eligibility code".
Well.. it turns out that submitting this form emails customerservice@pge.com with the information (and cc's the person filling out the form). A quick check reveals that it posts to '/cgi-bin/pgemail.pl' with the included account number and other personal information.
I wonder how they'll send me this super secret code? Email too? But don't worry it's secure, they have "PKI certificates using Certicom Elliptic Curve Qu Vanstone (ECQV) technology."
1 min read
At LinkedIn HQ they have a time-capsule made of legos. I hope they invite me over when they decide to open it back up.
Of course this would be the handiwork of Adam Nash.
And thanks again to Brandon Duncan for inviting me over for lunch to see this and other LinkedIn wonders.
