[aitorciki]

Hi lamby, I'm one of the co-founders at Ducksboard.

We approach things from a different angle than Geckoboard.

* As far as I know, they just visualize whatever comes from their data sources. We don't just visualize it, but we store it in our databases. This enables us to provide historic charts and other goodies.

* We make a strong focus on realtime as well, using WebSockets to push updates to the frontend as soon as they're available in the backend. I don't think they're going this far.

* The visual part is just a matter of taste, each one has a very particular style. We actually prefer ours :)

* And from today, our APIs allow handling your data and dashboards without a need to actually use the web frontend. This can be pretty useful in certain integration scenarios.

If you have more questions, feel free to ask.

[lamby]

The main beef I have with geckoboard is a litany of embarrassing unresolved bugs but these features sound pretty cool. Am trying out your API tutorial right now.

[pmjoyce]

Paul from Geckoboard here. Would love to hear how we can do better. Happy to respond here or you can shoot me a mail, paul at geckoboard.com

[fomojola]

All in all, minor issues, but: you filter out "target" attributes on URLs. I have links in my dashboard that I want to automatically open in another window so I don't close the dashboard window. Not sure why "target" is a banned attribute.

Also, public loop URLs don't appear to actually loop: I have 2 dashboards both added to the public loop, and nothing I seem to do will make them do that in either Firefox 11, Chrome 18 or Chrome 13 (on my Google TV that I use to display on a big screen).

Also, making your push interface public WOULD be a significant improvement over the existing interface: it gets tedious having to write authenticated web handlers purely to feed data to the dashboard, I'd much rather write cron jobs to do that.

[pmjoyce]

Thanks for the feedback.

The filtering of the "target" attribute is down to an overly aggressive attribute whitelist but I've created and story and that's being added now.

Looping issue - it's working for us and we've had no other reports of failure. Can you check the Sharing URLs tab under the account link to ensure that the dashboards in question are enabled for read-only viewing? This is off by default for security & privacy considerations but agree that the UX is currently sub-optimal. If you're still having problems then just ping me a mail: paul at geckoboard.com and I'll look into it.

We're just about to make the push API public for everyone (early next week), in the meantime feel free to shoot me a mail with your account deets and I'll enable it for you.