Open opensource21 opened 7 years ago
I agree that having a local backup will be useful. Especially since many users spend a lot of time and effort to write notes. An export-only backup is easier, we don't need to think about overwriting or merging data.
But even for export-only backups, we have to determine whether the backup is human readable (like a HTML file) or machine readable. What do you think?
On Mar 12, 2017 01:43, "Niels" notifications@github.com wrote:
On android devices backups are almost difficult. You provide a sync server, which is fine. But I find that notes on a bible should have a strong privacy protection. So I see two solutions:
I would really appreciate to see solution 2 in the near future. It has the advantage that it enables to use the comments in other applications or context. If you can give at least a hint how to realize it, so that a pull request can be made.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/yukuku/androidbible/issues/51, or mute the thread https://github.com/notifications/unsubscribe-auth/ABV7XRbVbe5gdW9MwDecL48PGDVzxZa0ks5rkt1XgaJpZM4MaRfq .
I would prefer a technical format like xml or json. Then it's possible to create a restore from backup as a second step. Furthermore it allows to change the bibleapp without loosing all date. At last it enables individual reports. Perhaps xml combined with a special stylesheet to create an html report is the perfect solution.
While I am a strong supporter and advocate for privacy, I fail to understand why Bible notes would need strong encryption. What on Earth could the use case possibly be? I thought the whole point of evangelism was to spread the Word. On Sat, Mar 25, 2017 at 3:59 PM Niels notifications@github.com wrote:
I would prefer a technical format like xml or json. Then it's possible to create a restore from backup as a second step. Furthermore it allows to change the bibleapp without loosing all date. At last it enables individual reports. Perhaps xml combined with a special stylesheet to create an html report is the perfect solution.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/yukuku/androidbible/issues/51#issuecomment-289235660, or mute the thread https://github.com/notifications/unsubscribe-auth/ADGs8Mo_dbV-i4XbWRsDnoqErIKS6Sg0ks5rpXIigaJpZM4MaRfq .
Well the point is to spread the Word - not private notes. Think about situation where the word open your eyes, about a misbehavior and you make a note about it. Or imagine you read a bible verse and get an impression to a specific person. Then this impression is special for this person and not for public audience. If we think about sermons it would be indeed useful if they are public.
Ok, I see your point. I had not considered that some people may use the Bible notes functionality to log personal thoughts or other sensitive information. In this case certainly some sort of protection is needed to ensure such notes are kept secure.
From: Niels
Sent: Sunday, March 26, 1:34 PM
Subject: Re: [yukuku/androidbible] Export of comments and settings (#51)
To: yukuku/androidbible
Cc: gmr409, Comment
Well the point is to spread the Word - not private notes. Think about situation where the word open your eyes, about a misbehavior and you make a note about it. Or imagine you read a bible verse and get an impression to a specific person. Then this impression is special for this person and not for public audience. If we think about sermons it would be indeed useful if they are public.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
On android devices backups are almost difficult. You provide a sync server, which is fine. But I find that notes on a bible should have a strong privacy protection. So I see two solutions:
I would really appreciate to see solution 2 in the near future. It has the advantage that it enables to use the comments in other applications or context. If you can give at least a hint how to realize it, so that a pull request can be made.