- https://twitter.com/the_sohail_azim
- Joined on
2021-10-26
Block a user
Migration compatibility and tooling
The current pins are stored in hashed format. It looks like in this implementation we store them in plaintext. Is this an update we can make?
Change alias to FQDN
For better UX. The user doesn't need to type in the FQDN. They would just type in "alfred" and we would save/retrieve it internally as alfred.sarafu.eth and .
devops: add Dockerfile and GH build config
Example for adding to the token index
Have a Space after each colon.
@carlos It should cosmetically closely resemble the current USSD menu.
Add short code (alias)
@willruddick Should it be truly random (but human readable) aliases? Like flyingcat56
?
Validate aliases, addresses and phone numbers in the send menu
feat: upgrade go-vise dep, minor cleanups to go.mod
Validate aliases, addresses and phone numbers in the send menu
It should be + prefixed. Why? That is how we save it in our common db (graph) and also how most, if not all, API providers expect the phone number.