Presentation and new light web client Ğ1nkgo

[vjrj]

@poka

everything is green …

Now is failing again for some reason. PS: ok, I see now your last comment.

@poka

Why do you need post request on GVA exactly ?

I use durt for payments and durt do the OPTIONS first and later the POST on payments.

@poka

@vjrj I think we should consider this client as temporary, meeting an urgent need for the users now. But do you agree to join forces on Ğecko and Ğ1companion for what concerns v2?

G1nkgo is something that I was not expecting to do, sincerely. It’s quite difficult to me to do these kind of efforts in my spare time (because of my lack of time, because of my health, and for other reasons). But, someone added me to the Spanish tech group , and there mentioned that some light web client was needed. I suggested several times, to use flutter and some code from gecko to do it. And as “to talk is cheap” suddenly I started to code and here I am.

When someone mentioned me about durt, I trash the pure crypt code I had to create wallets, and I started to use the wallet part of durt. Recently when I started to achieve to use gva via a proxy, I did the same with the duniter code I used to calculate the history and the balance (maybe I have to rescue some part in case gva fails temporally to retry with duniter).

I was with the sensation that we were sharing code. Later you, poka, clarified me that you are not using durt right now.

But my motivation to do Ğ1inkgo was the problems that I saw in the markets:

• People using paper
• People without wallets at all for different reasons (lack of knowledge, lack of space, …)
• People asking for help because they lost the pass/phrase (many of them, all the time)
• People with passwords annotated in papers in all the markets (so here I agree with @flodef about the social hacks) some working, some not working
• People like me that couldn’t pay because Cesium was not working correctly
• Other serious usability problems that I suffer myself and I saw in others
• Friends installing Cesium (after talking them about duniter/Ğ1) and trying to use their “I-use-the-same-password-everywhere” and losing the interest minutes later in use Ğ1 after the password/passphrase wall.
• IMHO, the use of “you are not a member” everywhere in Cesium is not a warm welcome to newcomers. This is why I do not mention things related to WOT in Ğ1.

(and these are the reasons that comes to my mind right now, to say something).

So I was thinking mainly in mitigate these kind of scenarios mainly to newcomers. Are these also goals of gecko?

If yes, or partially, count with me. If not, we can try to share as much code as possible in some common libs and not to try to solve the same problems again and again, and to have to faces (gecko and g1nkgo) for the same client libs.

BTW there are some MR in:

Sign in · GitLab

@tuxmain

DNS or just the server being compromised. As the user cannot choose not to update the client, the service admin can just update the server with the compromised version. This could be mitigated using in-browser verification, but this is not standard yet so it will protect too few people.

I was thinking in this a bit, but I didn’t find a good solution. I derived thinking in RO distros, and things like that, but none seems to work.

A signed app sounds like a the better option, and to let the web client just like a starting for the firsts uses (try without effort, continue later with g1nkgo app, continue later with cesium/gecko).

@Moul

I did add Ğ1nkgo to the first general table Clients and tools comparison .

I completed it.

@Moul

Would you like to have the repository moved to clients group ?

Feel free.

BTW, this weekend I installed a production server:

Ğinkgo

More info:

vjrj / ginkgo · GitLab

PS: Duniter CORS successful test:

CORS Tester - Test a URL for valid CORS headers