Update README.md

README.md

@@ -16,21 +16,24 @@ It is a simple and secure way to authenticate users without the need for usernam
 - [x] Consider move the front-end to its own repo (update: It will stay in-repo for simplicity)
 - [x] Create a suitable Cross-Origin policy
 - [x] Actually create challenges that are hash-related to the sing-data, allowing "Document signing" (only BankID flow)
+- [x] Consider adding fictional email to ID Tokens based on user-id eg `ABCDEFG@uyulala.local`
 
 ## Future plans
 
 - [ ] Better error handling, logging and documentation
 - [ ] Nicer Web UI
-- [ ] Replace the websocket-based remote-signer with some webrtc-based solution (eliminate load-balancer issue with
-  multiple instances)?
-- [ ] Consider adding fictional email to ID Tokens based on user-id eg `ABCDEFG@uyulala.local`
 - [ ] Look over any potential useless / missing data with the response from the collect api; it should contain
   everything to validate the signature
 - [ ] Should admin apps be able to create users with arbitrary user-ids? (easier to integrate with other solutions?)
 - [ ] Make up some configuration / rule system for accepting new keys (eg only allow keys with a certain certification
   level)
 - [ ] ....
 
+## Scrapped
+- [x] Replace the websocket-based remote-signer with some webrtc-based solution (eliminate load-balancer issue with
+  multiple instances)?
+
+
 ## Running a local test server
 
 ```bash