sharing saves across devices
15 views
Skip to first unread message
yowzadave
Dec 15, 2010, 4:30:24 AM12/15/10
to Parchment
Hi, just joined the group....and I'm really excited by how great
everything looks already.
I've been thinking about my ideal implementation of the "save"
function, and was wondering if it might be technically possible for a
"save" to be remembered across devices--if, say, I begin a game on the
browser, click save, and then pick it up on my iPhone a few hours
later with the save bookmarked. This is a killer feature of Kindle
books--you can read on your browser, your iPhone, your Kindle, and
they sync automatically.
My first instinct was to think this would require a database that
stores all of the usernames for every user, and their save points in
the book, and you'd have to log in to the site to access your stored
saves...which would be something, but probably not the most compelling
solution for a user.
But I wonder if the same state-saving might be possible via the url-
based bookmarking that Parchment currently uses, a la the way
Instapaper works. In this instance, clicking a "save" bookmarklet in
your browser could automatically send the saved state to your central
repository, which you could then access from any other browser, or
from Frotz on your iPhone...
What do you think? Maybe I should be asking this question of the Frotz
guys?
Thanks,
Dave
everything looks already.
I've been thinking about my ideal implementation of the "save"
function, and was wondering if it might be technically possible for a
"save" to be remembered across devices--if, say, I begin a game on the
browser, click save, and then pick it up on my iPhone a few hours
later with the save bookmarked. This is a killer feature of Kindle
books--you can read on your browser, your iPhone, your Kindle, and
they sync automatically.
My first instinct was to think this would require a database that
stores all of the usernames for every user, and their save points in
the book, and you'd have to log in to the site to access your stored
saves...which would be something, but probably not the most compelling
solution for a user.
But I wonder if the same state-saving might be possible via the url-
based bookmarking that Parchment currently uses, a la the way
Instapaper works. In this instance, clicking a "save" bookmarklet in
your browser could automatically send the saved state to your central
repository, which you could then access from any other browser, or
from Frotz on your iPhone...
What do you think? Maybe I should be asking this question of the Frotz
guys?
Thanks,
Dave
Ben Collins-Sussman
Dec 15, 2010, 10:26:11 AM12/15/10
to parc...@googlegroups.com
Sounds like a perfect use-case for Google AppEngine, no? Parchment
used this in the beginning, IIRC.
used this in the beginning, IIRC.
> --
> You received this message because you're subscribed to the Parchment Google Group. http://groups.google.com/group/parchment
>
Atul Varma
Dec 15, 2010, 2:52:23 PM12/15/10
to parc...@googlegroups.com
Yeah, I think this would be a great use for a Twitblob [1] hosted on Google AppEngine. This would basically allow users to authenticate with Twitter to save their game.
Currently Twitblob uses MongoDB as a backend, but it shouldn't be too hard to make it work with Google's storage backend (in fact I think the MongoDB folks might have made an adapter that provides a MongoDB API to the Google backend).
- Atul
yowzadave
Dec 15, 2010, 5:01:17 PM12/15/10
to Parchment
It looks like most of the Frotz readers for different devices use
dropbox for save syncing... so what this proposed new web app should
do is simply implement the Parchment reader for a saved collection of
stories; it can work with the dropbox API to manage saves, and they
will automatically be visible to all other devices. A bookmarklet
could be prepared that would send a given story or save-state found
elsewhere to the web app. Yes? Should I give it a shot with Google
AppEngine?
On Dec 15, 2:52 pm, Atul Varma <var...@gmail.com> wrote:
> Yeah, I think this would be a great use for a Twitblob [1] hosted on Google
> AppEngine. This would basically allow users to authenticate with Twitter to
> save their game.
>
> Currently Twitblob uses MongoDB as a backend, but it shouldn't be too hard
> to make it work with Google's storage backend (in fact I think the MongoDB
> folks might have made an adapter that provides a MongoDB API to the Google
> backend).
>
> - Atul
>
> [1]http://toolness.github.com/twitblob/
>
> On Wed, Dec 15, 2010 at 7:26 AM, Ben Collins-Sussman
> <suss...@red-bean.com>wrote:
> > Google Group.http://groups.google.com/group/parchment
>
> --
> atul varma ⋅ toolness.com ⋅ @toolness <http://twitter.com/toolness>
dropbox for save syncing... so what this proposed new web app should
do is simply implement the Parchment reader for a saved collection of
stories; it can work with the dropbox API to manage saves, and they
will automatically be visible to all other devices. A bookmarklet
could be prepared that would send a given story or save-state found
elsewhere to the web app. Yes? Should I give it a shot with Google
AppEngine?
On Dec 15, 2:52 pm, Atul Varma <var...@gmail.com> wrote:
> Yeah, I think this would be a great use for a Twitblob [1] hosted on Google
> AppEngine. This would basically allow users to authenticate with Twitter to
> save their game.
>
> Currently Twitblob uses MongoDB as a backend, but it shouldn't be too hard
> to make it work with Google's storage backend (in fact I think the MongoDB
> folks might have made an adapter that provides a MongoDB API to the Google
> backend).
>
> - Atul
>
> [1]http://toolness.github.com/twitblob/
>
> On Wed, Dec 15, 2010 at 7:26 AM, Ben Collins-Sussman
>
>
>
>
>
>
>
>
>
> > Sounds like a perfect use-case for Google AppEngine, no? Parchment
> > used this in the beginning, IIRC.
>
>
>
>
>
>
>
>
>
> > Sounds like a perfect use-case for Google AppEngine, no? Parchment
> > used this in the beginning, IIRC.
>
>
> > --
> > You received this message because you're subscribed to the Parchment Google
> > Group.http://groups.google.com/group/parchment
> > --
> > You received this message because you're subscribed to the Parchment Google
>
> --
> atul varma ⋅ toolness.com ⋅ @toolness <http://twitter.com/toolness>
yowzadave
Dec 16, 2010, 5:19:28 PM12/16/10
to Parchment
Scratch that--there is apparently no web API for dropbox yet--just for
mobile devices and client apps. Seems a shame, as that might have been
the perfect solution for a web implementation of a library that could
store saves seamlessly between devices.
mobile devices and client apps. Seems a shame, as that might have been
the perfect solution for a web implementation of a library that could
store saves seamlessly between devices.
Rob
Dec 16, 2010, 5:52:10 PM12/16/10
to parc...@googlegroups.com
I've seen a web based application called AirDropper that allowed files to be directly uploaded into someones dropbox account. Doesn't need any client or software loaded. Might our be worth finding our how that works, maybe repurpose it?
Reply all
Reply to author
Forward
0 new messages