-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status Efforts #169
Comments
Backend relation to blockchain There is another posibility that bockchain is offline (infura service, our Can we add more identification inside icons that one of them is our platform? (like small userfeeds icon) Not sure if good idea Transaction mode I would add color to those small dots showing Activity feed This looks good. We need to define exactly what activities are possible, and not only in link exchange. This is something new that I haven't thought through so I don't have much comments. |
#133
#121
+
https://github.com/Userfeeds/Userfeeds/issues/145
As part of bigger effort we should start working on showing current status of network and our backend in comparison to its network.
Per @michalwarda suggestion we could use the space that's currently occupied with Metamask button. Here's the short proposal that could use some feedback:
It would consist of two elements:
1. Status of the backend & blockchhain
a) Synchronized (less than x blocks of difference)
https://codepen.io/patrykadas/pen/MQwywp
b) Asynchronized (more than x blocks of difference)
https://codepen.io/patrykadas/pen/zRxeZj
c) Offline / error
https://codepen.io/patrykadas/pen/eVNJav
2. Status of the transaction
a) Type (link / boost)
b) Current stage
On Chain, In Review, Whitelisted (visible)
On Chain, Visible
Clicking it should expand a status view of particular transaction. At this point I also thought about aggregating those statuses in a form of an activity feed of an address. This one's just a wireframe:
We have an aggregated view of statuses of past transaction per address that could be an entry point for future experiments (cryptopurr), I would like to keep the possibility to address particular status though, as currently implemented.
The text was updated successfully, but these errors were encountered: