Skip to main content

application/atom+json? and more on our converter

Sam Ruby's recent post (Application/Atom+JSON) has sparked some interesting comments.  Is there value in a standard way to represent Atom data in JSON data structures?  I think so.  I do think that we need to have a way for transparent pass-through of generic elements (which means some scheme for dealing with Atom extensions, which means dealing with at least some subset of XML namespaces).

In other news, we're  working on fixing the issues that Sam noted in AOL's Atom-to-JSON converter.  The good news is that most of these issues have to do with the underlying ROME library we're using, and so the fixes that Joseph van Valen is making will be contributed back to the community. 

It turns out that the same issues are present even if you specify Atom as the output format; while Atom-to-Atom isn't a very useful converter, it's awfully useful as a test case.  For example, the Feed Validator tells us that something is munging hreflang.  It's also dropping rel="self" and other links for some reason... all of these things look like simple bugs, easily fixed.  The converter actually does seem to pass through elements it doesn't understand for entries, but not for feeds, which looks like a simple oversight.

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:

http://www.msnbc.com/rachel-maddow/watch/maddow-to-news-orgs-heads-up-for-hoaxes-985491523709

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.