Closed Aga-C closed 2 years ago
I wrote that description based on this comment from an F-Droid repo maintainer: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/9671#note_670782217
?
This app is an alternative front-end to GoogleTranslate, but it doesn't directly connect to it.
It works as follows:
+-------------+ | | +--> | instance #1 | ---+ | | | | | +-------------+ | +------+ | +-------------+ | +-----------------+ | | | | | | | | | user | ---+ | instance #2 | +--> | GoogleTranslate | | | | | | | +------+ +-------------+ +-----------------+ +-------------+ | | | instance #3 | | | +-------------+
This way GoogleTranslate won't know youre identity. Auto selecting a random instance (default mode) each time will obfuscate and spread your data more so nothing will be linked easily as it's not in a centralized database.
This description looks great, but I think this picture is not necessary and there is still missing list of features of the app. Instead of this picture, there could be a Features section, and below something like this:
It's just my first thought, a draft. You can do something better based on this.
This app is an alternative front-end to GoogleTranslate, but it doesn't directly connect to it.
It works as follows:
+-------------+ | | +--> | instance #1 | ---+ | | | | | +-------------+ | +------+ | +-------------+ | +-----------------+ | | | | | | | | | user | ---+ | instance #2 | +--> | GoogleTranslate | | | | | | | +------+ +-------------+ +-----------------+ +-------------+ | | | instance #3 | | | +-------------+
Features
This way GoogleTranslate won't know youre identity. Auto selecting a random instance (default mode) each time will obfuscate and spread your data more so nothing will be linked easily as it's not in a centralized database.
Supported languages:
Kept the image as it really helps grasping the idea. It's not easy for non-technical people to understand what a VPN is. What do you think @Aga-C?
Supported x languages
@ManeraKai Aga-C meant a number in how many languages the app translates. Currently the list of languages is too long.
This app is an alternative front-end to GoogleTranslate, but it doesn't directly connect to it.
It works as follows:
+-------------+ | | +--> | instance #1 | ---+ | | | | | +-------------+ | +------+ | +-------------+ | +-----------------+ | | | | | | | | | user | ---+ | instance #2 | +--> | GoogleTranslate | | | | | | | +------+ +-------------+ +-----------------+ +-------------+ | | | instance #3 | | | +-------------+
Features
This way GoogleTranslate won't know youre identity. Auto selecting a random instance (default mode) each time will obfuscate and spread your data more so nothing will be linked easily as it's not in a centralized database.
Kept the image as it really helps grasping the idea. It's not easy for non-technical people to understand what a VPN is.
You're right 👍
The description looks good, but "This way..." should be below the image, as it is related to this description. And maybe @Valdnet would like to correct some text or add something to this feature list?
Typo:
A tranlate button in the text selection toolbar.
Shouldn't there be and
instead of in
?
You can understand that the "Translate" button is in the text selection toolbar :stuck_out_tongue_winking_eye:.
Corrected: A translate button and the text selection toolbar.
As for the "Translate" button itself that it is, I wouldn't mention it. It is obvious it should be.
Additionally, in the graphic image I would give arrows to all instances and return arrows as well. Currently, they only illustrate that one instance is selected with no return path of translation 😉.
You can understand that the "Translate" button is in the text selection toolbar stuck_out_tongue_winking_eye.
Bruh that is what I meant:
Additionally, in the graphic image I would give arrows to all instances and return arrows as well. Currently, they only illustrate that one instance is selected with no return path of translation wink.
Thought of this, but it will make the drawing so complex. The text describes that the request will go back. The text also said that it will be random. I may change the arrow's position though to the instance #3
to appear random as 1 isn't a random selection.
With all arrows
+-------------+ | | +--> | instance #1 | <--+ | | | | | +-------------+ | +------+ | +-------------+ | +-----------------+ | | | | | | | | | user | <--+--> | instance #2 | <--+--> | GoogleTranslate | | | | | | | | | +------+ | +-------------+ | +-----------------+ | +-------------+ | | | | | +--> | instance #3 | <--+ | | +-------------+
With one arrow the instance #3
+-------------+ | | | instance #1 | | | +-------------+ +------+ +-------------+ +-----------------+ | | | | | | | user | ---+ | instance #2 | +--> | GoogleTranslate | | | | | | | | | +------+ | +-------------+ | +-----------------+ | +-------------+ | | | | | +--> | instance #3 | --+ | | +-------------+
What do you think @Valdnet?
Ah, that toolbar you meant 😉.
With one arrow the instance #3
This can be 😁.
Maybe it should be added that the application gets the official list of instances.
This app is an alternative front-end to GoogleTranslate, but it doesn't directly connect to it.
It works as follows:
+-------------+ | | | instance #1 | | | +-------------+ +--------+ +-------------+ +-----------------+ | | | | | | | user | ---+ | instance #2 | +--> | GoogleTranslate | | | | | | | | | +--------+ | +-------------+ | +-----------------+ | +-------------+ | | | | | +--> | instance #3 | --+ | | +-------------+
This way GoogleTranslate won't know your identity. Auto selecting a random instance (default mode) each request will obfuscate and spread your data more between instances so nothing will be linked easily as it's not in a centralized database.
Features
Very good for me 👍.
For me too, but please fix the typos:
@Valdnet sorry I thought you were only talking about the text selection toolbar problem here: https://github.com/ManeraKai/simplytranslate_mobile/issues/144#issuecomment-946744915
This app is an alternative front-end to GoogleTranslate, but doesn't directly connect to it.
It works as follows:
+-------------+ | | | instance #1 | | | +-------------+ +--------+ +-------------+ +-----------------+ | | | | | | | user | ---+ | instance #2 | +--> | GoogleTranslate | | | | | | | | | +--------+ | +-------------+ | +-----------------+ | +-------------+ | | | | | +--> | instance #3 | --+ | | +-------------+
This way GoogleTranslate won't know your identity. Auto selecting a random instance (default mode) each request will obfuscate and spread your data more between instances so nothing will be linked easily as it's not in a centralized database.
Features
@ManeraKai Using <p>
is not a good idea. F-Droid adds <br>
on its own with every line break in metadata file what produces ugly result. Also, for the same reason, I wouldn't create a list with <ul>
and <ol>
. Take a look on a metadata from another project, where HTML tags aren't used for paragraphs and lists, and it looks good both on a website and F-Droid app: https://github.com/SmartPack/PackageManager/blob/master/fastlane/metadata/android/en-US/full_description.txt (it looks like this: https://f-droid.org/en/packages/com.smartpack.packagemanager/)
Also, I would use <b>
for Features header to make it more visible.
Let's just hope F-Droid won't break pre
🙂
Hopefully
Hi,
I think, at this time, it would be great to change the app description a bit. The most important thing, to encourage to download the app, is to list what features it has - it would be easier to read the few paragraphs. Many apps have listed its features on F-Droid, starting with dash, period or star. So, except for one introductory paragraph at the beginning, there would be such list with short sentences, and maybe some ending. It's up to you to decide how it will look like best :)