When it recommends that the .age extension is used, but does not enforce it or have a really good reason to do it, it is confusing and clunky. I think it is easier for people to make the in file and out file with the extension they want. Either make the .age extension mandatory, or don't tell people they should use it because you recommend it.
And the key file usage is clunky.... all of the key file operation is clunky. Age promises simplicity- so one should be able to figure out using the key file instead of the password. I took over an hour trying to figure things out. EVEN if i was below average intelligence, taking so long to figure out the "easy" system proves that it is NOT "easy" enough. No where close to it.
So the key is injected with special "AGE" markers, and the password option recommends the .age extension. People know they are using rage or age, they do not need the word "age" rammed down their throat in a clunky and confusing way that actually COMPLICATES the operations.
Biz ppl say do not promise what you can not deliver. You promise simplicity, but then you go out of the way to make it complicated by injecting the custom "age" implementations into the key. AES modes or chacha20 modes never say the word "AGE" has to be plastered in every key. The app PROMISES simplicity- it fails to deliver.
In my honest opinion, for something that claims to be easy to use, the app sure goes out of its way to complicate things and make users see or deal with or use the word "age". WAY too clunky for an app that claims to value simplicity.
When it recommends that the .age extension is used, but does not enforce it or have a really good reason to do it, it is confusing and clunky. I think it is easier for people to make the in file and out file with the extension they want. Either make the .age extension mandatory, or don't tell people they should use it because you recommend it.
And the key file usage is clunky.... all of the key file operation is clunky. Age promises simplicity- so one should be able to figure out using the key file instead of the password. I took over an hour trying to figure things out. EVEN if i was below average intelligence, taking so long to figure out the "easy" system proves that it is NOT "easy" enough. No where close to it.
So the key is injected with special "AGE" markers, and the password option recommends the .age extension. People know they are using rage or age, they do not need the word "age" rammed down their throat in a clunky and confusing way that actually COMPLICATES the operations.
Biz ppl say do not promise what you can not deliver. You promise simplicity, but then you go out of the way to make it complicated by injecting the custom "age" implementations into the key. AES modes or chacha20 modes never say the word "AGE" has to be plastered in every key. The app PROMISES simplicity- it fails to deliver.
In my honest opinion, for something that claims to be easy to use, the app sure goes out of its way to complicate things and make users see or deal with or use the word "age". WAY too clunky for an app that claims to value simplicity.