Looks nice and is definitely something I'd get some use out of -- it would be good to provide some more information...
What kind of analytics and visualization are you going to provide?
"Real-time" takes many meanings and for many visualization tasks, particularly on rapidly changing data, requires some computation map-reduction to craft presentable metrics.
Or are your just emitting on a callback updates of the key-val pairs? (Which could still definitely be useful, but then reddish wouldn't really be an endpoint for redis analysis)
We use real-time to refer to two different things:
If a key is deleted (or any other update is made), the interface reflects that change. Right now we throttle those updates and have some other ideas to limit them so the interface isn't overwhelmed if 1m keys suddenly expire.
We also use real-time to describe the analytics. They're still in development but in their current form are line and pie graphs of user-selected data (optionally over time). There are a number of avenues we could take when it comes to visualizations and user feedback will impact how we proceed after the initial prototype of the visualizations is released.
Probably due too the Certificate for https used by mailchimp is for *mailchimp.com domains while you are on a us2.list-manage.com. It worked fine when i switched to http.
Didn't you hear? Once we used it to dethrone MSIE, we realized that we didn't actually give a shit about compatibility. It was just the best stick we had to beat IE with.
atm we are only supporting the latest browser versions to speed up development but if there's enough interest in supporting other versions we're happy to do so
After looking at your CSS, I believe the only issue is that you don't appear to be defining how the newer HTML5 elements should be displayed. It's common to simply put display: block, or inline-block, for all of the HTML5 element that you're using. This should fix the garbled mess that you see in the screenshot. I don't believe that there is much more to it than that. Although, I do not have the version of Firefox mentioned to test on.
The copy on https://reddi.sh/ is fine. It's more the blog post that talked about phpmyadmin and stuff that I found confusing.
How do you plan on handling security? Seems like people will need to poke holes in the FW directly into their data store for this (that's probably the other thing that was pulling me towards a non-hosted product).
You can either connect directly to public instances (like from redistogo.com) or use our proxy which will (before we release) support encrypted connections.
I like these types of applications. I think real-time data visualization is neat, especially on kind of a meta level like this. What makes this one different than Radish, though? (http://radishapp.com/) Even the name is similar.
What kind of analytics and visualization are you going to provide?
"Real-time" takes many meanings and for many visualization tasks, particularly on rapidly changing data, requires some computation map-reduction to craft presentable metrics.
Or are your just emitting on a callback updates of the key-val pairs? (Which could still definitely be useful, but then reddish wouldn't really be an endpoint for redis analysis)