2011/5/26 Doug Blank <doug.blank@gmail.com>
On Thu, May 26, 2011 at 8:50 AM, Benny Malengier
<benny.malengier@gmail.com> wrote:

...

Yes, I don't think it would be hard to get the data (or update it).
Much more difficult doing something with it with Gramps. That would be
a full project, and some commitment.

> So the configuration of the Gramplet should allow the user to set username
> and password. We would have to store that in a safe way, so that password
> cannot be exposed by reading the ini file!

This is one reason I haven't released the gramps-tweet code... these
interfaces are not designed for open source projects. They say keep
the key private, but there isn't a way to do that in Python, except
through obscurity.


Haha.
If you look in the code, you see that queries go to
http://www.dev.usys.org/familytree/v2/

So, it is plain text when you send it anyway ;-)

A developer key for Gramps would indeed be known and usable by the entire world right after we commit it to sourceforge.

Benny

-Doug