I'm playing around a bit more with our Journals mobile upload feature. It not only lets you blog photos, but also short videos. Here's my son learning how to command doors:
I've got it set up to drop the results into a draft blog first, then previewing and copying the results over to a public blog later. It'd be nice to automate that step a bit more. Sometimes you really don't want to liveblog your mobile life.
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…
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.
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.
Comments
Post a Comment