Indeed the backend useable by U1Db was not shut down. Unfortunately
however all documentation is gone so I sympathize with the fact that
it's basically impossible to discover that the servers are still
running.
https://u1db.one.ubuntu.com/~/test.db
That's what the API endpoint looks like. It won't work as-is in a
browser because it requires OAuth. This was also at the time one of the
challenges in making it work, since the authentication methods were
being implemented in online accounts in parallel to U1Db QML bindings
adding support for synchronization. So the code was mainly implemented
based on a local server, which was easy to run. But it wasn't
straightforward how apps would authenticate, including signing the API
URLs, and ideally, be able to use any server of the user's choosing.
The sync branch didn't make it past proof of concept - see
https://code.launchpad.net/~uonedb-qt/u1db-qt/syncWithU1 - it basically
works but the code needed cleaning up when my time then was
increasingly going into UI Toolkit work, and the aforementioned design
problems are still unsolved.
I'd be very happy to see this work being picked up if there's enough
interest, especially with concrete use cases to solve, as looking back
the original API was not written in the best possible way, especially
the Synchronizer.
ciao,
C
On mar, Feb 2, 2016 at 4:57 , Robert Schroll <rschr...@gmail.com> wrote:
On Mon, Feb 1, 2016 at 10:06 PM, Rodney Dawes
<rodney.da...@canonical.com> wrote:
It was always clearly stated that the U1DB server was still up, and
that
it was not done via file synchronization.
I'm afraid I completely missed this point up til now. I looked back
at the announcement of the shutdown of Ubuntu One (not to be confused
with Ubuntu One!) [1], and the only only reference to U1DB I found
was in the second to last paragraph, which says,
The shutdown will not affect ... the backend U1DB database service.
Even after your explanation, I'm still not quite sure how to parse
that.
I'm pretty sure the Qt U1DB
implementation that exists on the phone was also written mostly after
the Ubuntu One file sync services were taken offline, or at least
announced that the service would be taken offline. Would be a bit
odd to
continue promoting an API for a service that was dead, don't you
think? :)
All the documentation I've seen for U1DB has focused on local use. I
assumed that the network syncing was being put on the back burner.
That seemed more sensible than giving the same name to three
different components that had nothing to do with each other.
There is u1db.ubuntu.com of course.
$ nslookup u1db.ubuntu.com
Server: 8.8.8.8
Address: 8.8.8.8#53
** server can't find u1db.ubuntu.com: NXDOMAIN
I'm assuming you've mistyped the domain, but Googling "U1DB server"
isn't giving me anything useful. How are people supposed to find out
about this?
I thought there was a blog post somewhere about how to sync a U1DB
with
Ubuntu One using the account on the phone, in QML, but I can't seem
to
find it now. Maybe Christian (kalikiana) can help clarify that when
he
comes back on-line.
I'd love to see this, if anyone can find it.
Thanks,
Robert
[1]
http://blog.canonical.com/2014/04/02/shutting-down-ubuntu-one-file-services/
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
