I wonder if Virtuals Protocol considered to use their governance forum (https://gov.virtuals.io/) to decide upon bounties? I can imagine the community wants to reward way more than 10k for these sort of bugs.
Although I like the concept at this point status pages are very disappointing to me, between those that stay green when everything is failing because they're not updated properly, those that stay green because "it was a localized partial failure only" even though the whole thing breaks (hi aws !), ... Sure some are reliable, but enough aren't that it feels like you can't trust them.
You can't look at the status page and believe what it says, so you go and ask people anyway (on irc, reddit, hnews, whatever community you like). Meaning that page might as well not have existed.
Couldn’t agree more. I pushed for one to be implemented at my last job (api) as I felt it was ridiculous that we didn’t have a means to communicate downtime, outages, issues.
Initially the status page worked. But as more and more people subscribed to it, it became a bigger issue, to issue an alert.
And unfortunately an issue couldn’t be raised only to those it was relevant for.
All this lead to was, not updating the status page and thus it becoming a useless tool to determine if an issue was occurring.
Back to Twitter...
I feel the product needs a lot work in practice, and possibly in implementation and training.
Ah, sadly I believe your personal experience is very common.
It's insane really; a company puts out a status page to say to their customers "you can trust and rely on us through that dedicated medium to know our status", and if the customers in question buy into the proposition and use it the very first thing that company does is make it so you cannot trust and rely on them through that dedicated medium. Succedding is what causes it to ultimately fail.
Status page should have stayed as undocumented features for "the little guys" behind the scene to communicate and never get into the open world where PR and marketing and decision makers can roam.
Status pages shouldn't need any manual intervention.
I setup mine to automatically monitor my website from another service provider in a different datacenter. That way I know if the server is down for any reason and it updates automatically.
If my server goes down, within 5 minutes the status page is red. End of story.
Great job! Love the design. You may consider to preload the first x designs in the html directly, its better for the seo. What about fixing deeplink urls when people click your menu? Just use a hash. Will take a look.at your Js tomorrow, got to sleep now.
I'm not sure if I could see who purchased through my site, as far as I know shopkeepers see it. There is no sort of affiliate program. So I don't see any monetizing options for this moment.
It's fast, it supports JSONP and their API team is great to work with (fast replies on email). I could recommend anyone to build a mashup on top of the Etsy API.
That's great to hear, Jonathan. I personally know two of the people on that team and they're brilliant programmers but never saw their view from the outside. I'm glad to hear you're getting amazing support from them.
If you're enjoying it a lot and love to program, you should consider applying there too.
Along with everyone else's activity indicator complaint, I also think that color coding the bottom "info bar" area of each item according to category would be useful for quickly scanning and separating all of that info with the eye.