Skip to main content

APP Interop Final Score

The APPInterop event was a lot of fun.  Thanks everybody!  I saw a bunchof people who I've only talked to via email.  And a few I haven't seenin a long time... perhaps since the original Atom kick-off at Googlemany years ago. 

The final scorefor AOL Journals is 1-1.  If you want to continue testing againstour production endpoint, feel free to update the matrix:

service document:
user: atomprotocol
password: password

I also got a chance to play with EC2 (thanks to M. David Peterson) inan attempt to get our latest server available for testing against.  Itwas tremendous fun to play with EC2 and I'd love to try using it for areal scalable application.  I did eventually get a server up longenough to verify our current bug fixes, but I didn't have time to fixthe date bug that James Snell found. 

I've now found 3 bugs in our date parsing code; it seems to be the mostfragile part of the parsing by far.  I'd love to see what test casesother people have for dates.  So far I know I need to add both UTC andvarious timezones, and now I know we need to round fractional seconds. (Does anybody but James send fractional seconds?)

Popular posts from this blog

Personal Web Discovery (aka Webfinger)

There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

The problem with creation date metadata in PDF documents

Last night Rachel Maddow talked about an apparently fake NSA document "leaked" to her organization.  There's a lot of info there, I suggest you listen to the whole thing:

There's a lot to unpack there but it looks like somebody tried to fool MSNBC into running with a fake accusation based on faked NSA documents, apparently based on cloning the document the Intercept published back on 6/5/2017, which to all appearances was itself a real NSA document in PDF form.

I think the main thrust of this story is chilling and really important to get straight -- some person or persons unknown is sending forged PDFs to news organization(s), apparently trying to get them to run stories based on forged documents.  And I completely agree with Maddow that she was right to send up a "signal flare" to all the news organizations to look out for forgeries.  Really, really, really import…
Twister is interesting.  It's a decentralized "microblogging" system based on putting together existing protocols:  Bitcoin, distributed hash tables, and Bittorrent.  The most interesting part for me is using Bitcoin for user registration and spam control.  Federated systems handle this with federated trust, which is at least conceptually simple.  The Twister/Bitcoin mechanism looks intriguing though I don't know enough about Bitcoin to really comment.  Need to read further.