roemba / xsplit Goto Github PK

Probably use Web Share API

Needs to be able to add people to a new bill, send it out to the members and the amount for each member should be correctly split between them.

User registration complete/confirmation, add/remove friends, upgrade balance, ...

The browser should be able to send a request to retrieve the encrypted private key for a certain username. The api should be hosted on api/v1/login/ and support a GET request to get only the encrypted private key for

Setup the ORM connecting to PostgreSQL

Node server should be able to launch and run.

For now, the API should be able to be called on /api/v1/user and only support a GET and POST request for getting a user and creating one. Both calls have to be authenticated.

Add data structures for the bills, should contain total, participants, who paid already, date, id, who created the bill and a description.
Probably make a transaction request object for this that contains who pays who for what bill and whether they paid it.

User has to add its signature to accept the payment, payment should be processed and correctly added to the transaction.

Maybe handling this is a bit overkill but it should not be that difficult to do.

Creator of the bill can set the status of a transactionrequest to paid.
This way payments can also be settled outside of the system.

Everything on the page is the same, even after a page refresh, but in the background, the user has been logged out automatically which causes non-authorized errors at certain pages. Links in navbar are also in the logged-in state.

Implement the user interface for search and adding a member to a bill

Fix the layout when a new user is created and display server side errors if they occur.

Once a decrypted private key has been obtained, all requests going to the server have to be signed by this private key and verified using the stored public key of the user (which for now is set manually in the DB)

Create a first super basic DB schema and a script that cleans and recreates the DB on startup

The user that receives the request needs to be able to sign it and pay

Fill account with some XRP to simulate the function of buying some XRP by means of IDeal, creditcard, or ...

If you request from a friend and then click one of the navigation buttons, for example home, you are redirected to /request/home instead of /home

Once the browser has received the encrypted private key, it should be decrypted using the user password entered in the login form. The decrypted private key should then be stored temporarily in a local session storage which is deleted on tab close.

When a user logs out he is currently still on the page he need authority to see, should be redirected to home page.

This way we don't have to set the settings separately everywhere the logger is used.

Right now if the server errors when a request is made the error is returned to the user.

User groups collect bills for a group of users and maintain all users' balances.
All group members can add bills to the group.

User should be able to enter a username and password and press submit.

Back-end should be able to check and save whether transactions have succeeded.
Use transaction hash received from a user as proof.