remotestorage is now an Internet Draft at IETF

[mic...@michielbdejong.com]

Thank you everybody who contributed! Even though it's just a draft (work in progress),
it still feels like a step forward to have our remotestorage standard in a bit more
official format now:

http://tools.ietf.org/id/draft-dejong-remotestorage-00.txt

You could say that this is the product of two years of independent research by an
unorganized group, supported only by crowd-funding, volunteers, and donations. In the
acknowledgements I tried to list the people who convinced me to quit my job two years
ago, and the people who have worked full-time or part-time on the project since then,
as well as the people who were at the unconference in Unhost this year
( http://2012.unhosted.org/ ).

It was not really feasible to list everybody who contributed
to the discussions, aported ideas, helped to take important decisions, etcetera, because
-- a luxury problem if there ever was one -- there are just too many of you guys! So I put
"and many others" at the end to mean all the people posting on this mailing list and
chatting in the irc channel and tweeting about us. Thank you so much!! :)

I am really happy with how the standard worked out so far.
Of course the real work has only just begun. I am typing this email in an unhosted web app,
but to send it i still have to type a function call into the console, because there is no
'send' button yet. :) But at least the basis is working now, and i'm confident that more and
more useful unhosted web apps will start appearing, and become more usable over the coming years.

If you haven't yet, do check out https://github.com/remotestorage where Niklas is
maintaining all the latest tools for adding remotestorage support to your
unhosted web apps.

I am currently working on my 'Unhosted Adventures' blog series, trying to build up a bit
of headstart, and I think I will start publishing it as weekly episodes every Tuesday,
starting 18 December which will be my first Tuesday at Hacker Beach. :)


Ciao!
Michiel

[Melvin Carvalho]

On 6 December 2012 12:43, <mic...@michielbdejong.com> wrote:

Thank you everybody who contributed! Even though it's just a draft (work in progress),
it still feels like a step forward to have our remotestorage standard in a bit more
official format now:

http://tools.ietf.org/id/draft-dejong-remotestorage-00.txt

Congrats on this milestone!

I'll review this in more detail and get back.  The most obvious comment is that remotestorage is quite a similar sounding spec to the already existing localStorage spec., so perhaps in the final version the two concepts would have an overlapping API.

If I've understood the IETF correctly, there's two tracks, one which is RFC to describe a system or process (e.g. remotestorage) and another which is to create sort of a best practice for the whole internet.  The latter is understandably a lot more work to achieve consensus, basically because the whole internet has billions of stake holders.  Do you have an idea of which route you wish to go down yet?
 

You could say that this is the product of two years of independent research by an
unorganized group, supported only by crowd-funding, volunteers, and donations. In the
acknowledgements I tried to list the people who convinced me to quit my job two years
ago, and the people who have worked full-time or part-time on the project since then,
as well as the people who were at the unconference in Unhost this year
( http://2012.unhosted.org/ ).

It was not really feasible to list everybody who contributed
to the discussions, aported ideas, helped to take important decisions, etcetera, because
-- a luxury problem if there ever was one -- there are just too many of you guys! So I put
"and many others" at the end to mean all the people posting on this mailing list and
chatting in the irc channel and tweeting about us. Thank you so much!! :)

I am really happy with how the standard worked out so far.
Of course the real work has only just begun. I am typing this email in an unhosted web app,
but to send it i still have to type a function call into the console, because there is no
'send' button yet. :) But at least the basis is working now, and i'm confident that more and
more useful unhosted web apps will start appearing, and become more usable over the coming years.

If you haven't yet, do check out https://github.com/remotestorage where Niklas is
maintaining all the latest tools for adding remotestorage support to your
unhosted web apps.

I am currently working on my 'Unhosted Adventures' blog series, trying to build up a bit
of headstart, and I think I will start publishing it as weekly episodes every Tuesday,
starting 18 December which will be my first Tuesday at Hacker Beach. :)


Ciao!
Michiel

--

[Nick Jennings]

Congratulations! This is great progress!

> --
>
>
>

[Jan-Christoph Borchardt]

Yeah! Thanks & congrats to everyone!

On Thu, Dec 6, 2012 at 12:43 PM, <mic...@michielbdejong.com> wrote:

I am typing this email in an unhosted web app,
but to send it i still have to type a function call into the console, because there is no
'send' button yet. :)

Like a boss! Looking forward to a more advanced version of that.

[Melvin Carvalho]

On 6 December 2012 14:00, Jan-Christoph Borchardt <h...@jancborchardt.net> wrote:

Yeah! Thanks & congrats to everyone!

On Thu, Dec 6, 2012 at 12:43 PM, <mic...@michielbdejong.com> wrote:

I am typing this email in an unhosted web app,
but to send it i still have to type a function call into the console, because there is no
'send' button yet. :)

Yes I very often use this technique.  Actually I often provide in 'hooks' so that it will calls something like hook() if it exists, at certain points, and if not just run normally.  The main way I use this is to associate payments (webcredits) with certain actions.  And the just type them into the console when I need them, or into localStorage if I want the browser to remember.
 

Like a boss! Looking forward to a more advanced version of that.

--
 
 
 

[Thad Guidry]

Michiel,

A quick tip, and I appreciate your hard work on getting the IETF draft together.

Ensure that when you have listed your rules of the spec (SHOULDs, MUST NOTs, etc) in paragraph form especially those paragraphs with a lot of ANDs and ALSOs, that you break those out into a bulleted or numbered style, to ease the burden of adherents to the spec and peer-reviewers.  Here is a small paragraph that I saw briefly...

  
    Empty folders are treated as non-existing, and therefore GET
    requests to them SHOULD be responded to with a 404 response, and an


de Jong                                                         [Page 3]
 
Internet-Draft              remotestorage                  December 2012


    empty folder MUST NOT be listed as an item in its parent folder.
    Also, folders SHOULD be created silently, as necessary to contain
    newly added items. This way, PUT and DELETE requests only need to be
    made to documents, and folder management becomes an implicit result.

-- 
-Thad
http://www.freebase.com/view/en/thad_guidry