My Libraries all say "Pubic access is disabled.", and that is by default; I've never changed that setting.
I haven't tried access by URL. I would hope the same standards apply.
Maybe the Acer? There's a 32GB version of this 15.6" one, also. Not sure about Android.
Acer Chromebook 15 CB5-571-C1DZ (15.6-Inch Full HD IPS, 4GB RAM, 16GB SSD)
https://www.amazon.com/dp/B00TU7U4PU/ref=cm_sw_r_taa_oJVByb2NJ8JN7
There is a solution to your problem. A company doesn't cater to one or two people in their customer base. They look at the masses.
In English they say - the squeaky wheel gets the grease.
In Chinese - the loud rooster gets first into the soup.
Which one do you like better?
...
...
To tell the truth, I don't like the cloud (esp. private cloud) solution either. Not about security, but rather about stability. Using them you become too much dependent on the health / diligence of the support team and cloud traffic conditions.
On the other hand, providing a straight per-library synchronization scheme would totally kill their income. Android development is an absolutely unprofitable business, it's hard, long and prices are under 6 dollars in general.
One could make Memento 100 bucks - but no-one would ever buy it. That's the specifics of Android. 99% apps are cheap and written by amateurs. If it's something professional, like Memento, they deserve making money on it. But, I don't see any other solution than a cheap cloud for masses.
Re-Disclaimer: I don't like clouds either.
I like the Chinese saying.
I understand that the cloud is a way for him to make a profit... money has nothing to do with it for me... it's the other reasons we discussed.
It's a shame these days when people cry about paying a few dollars for an app. Everyone thinks they deserve something for free for some reason. Like I said... I'd gladly pay another $50 for this app if it had just that one more feature.
It's a great app and I have a use for it so Vasya deserves to get paid for it.
Not the end of the world. Once all my libraries are done I'll pull them from the cloud and make a full database backup on the phone and copy to other locations.
After that my libraries will only need small occasional updates that will be easy enough from the phone.
I am very glad this controversial discussion popped up. It's a pity though that both of you are presumptuously not teenagers any more, as if being a teen were something yucky. I'd love to be one. So, allow me to pretend to be a teenager among you two, old dudies, okay?. ;)
I remember a dozen years ago people spat at CDs preferring vanilla discs (or whatever you call that dinosaurish awful tech that grandpas so much yearn about), and Android is becomimng much more convenient (=better) than a PC. Fact!!!
But it seems in the talk with you, the workaround answer is coming up by itself. They say you can organize your own cloud using seafile https://www.seafile.com/en/home/
So, why not make a folder with memento files on several Android devices and sync betwen them using some fast local wi-fi connection or own-cloud solution by copying the **whole repository of Memento** from one device to another when needed.
Provided the Memento paths are the same, Memento should work identically on both the devices. Except, that you will have to always control which device has a newer db version before syncing. Because it will sync the whole database, not parts.
What do you think?
Do you, as an admin, have access to the data?
How can we make sure that the data is safe and is not accessible to anyone except the person who has password?
Is there any link or official Google documentation describing the mechanism of that cloud?
How can one be sure that the data is not leaked some day due to a virus or something on the computer who has administrative access to that cloud?
How can I make sure that the Cloud is using the mechanism you describe? Is there some "WhoIs" service to check that?
With the recent hack events, I think it is important to have all these questions clarified and be as much transparent as possible.
Vasiliy wrote me an extensive response in Russian, that I will translate tomorrow and send to Bill, who is Memento's greatest supporter.
It is a very comprehensive and well-argumented technical response, containing all correct security details that a professional programmer should be aware of and should implement.
Currently, it is absolutely safe to use the cloud if you encrypt your library. He described the encryption method, which I fully understand being a programmer myself, so it is fine.
Next, I hope Bill Crews will help me to correct my Russky mistakes and include a corresponding policy announcement to the wiki with other security details, to which the user will have to agree or disagree.
Memento may have some omissions in provision of security statements (which is mostly a matter of correct English translation and procrastination due to concentration on seemingly more important issues), but the app hasn't been detected to have any issues by Google on that for the past six years of its existence. Which is a good sign, given what draconic measures Google is imposing now on security.
I read somewhere, around 9% of new apps uploaded to Google Play have signs of violating privacy - by unauthorized uploading of data (in most cases, allegedly, with the purpose of trying to understand the client better - for more targeted ads, for example). They get blocked at their start.
Every time I add a new element borrowed from a third party (picture or java-library), the release is delayed. Supposedly, due to additional verification of illegal content - copyright, pornography etc.
Unrooted state, downloading proven apps from Google Play and antivirus highly contribute to the good app behaviour.
I tried writing an app for my own use to scan keyboard for keystroke combinations to be expanded, (like you type: "br" and it would expand to "best regards"), the antivirus blocked it, because it was not properly validated and contained signs of trojan code. It got me annoyed - the antivirus accused me of hacking my own self. But, at least I know it works.
In addition to that, millions of people trust Android. Each case of information leak is a loud case. Besides, most of people's information - like your correspondence, passwords to emails and sites - represent no interest and is not worth slowing down the device, consuming traffic and the hacker's "effort", who should upload it somewhere, store it and read / analyze it with the purpose of taking advantage of it, with little chances for any tangible success, and highly jeopardizing his developer account.
Well, it would be a different story if you were Angela Merkel, of course... But not if you are a mere mortal.