Hi everyone, I am developing an app for Boxee that is experimenting with bringing data from theyworkforyou.com and publicwhip.org.uk to a TV/set top box context, I've not released it yet but have written a blog post about it at: http://www.greenhughes.com/content/experimental-boxee-app-keep-track-how-your-mp-votes
I'm new to this mailing list so please forgive me if this has been discussed before (I looked through the archives but didn't see anything relating to my question). At the moment to you the theyworkforyou.com API you need an API key which is fair enough. However in this app I am doing everything client side (the app directly talks to the sites) and I am worried that having to apply for an API key might put end users off, especially as Boxee starts selling set top boxes and people join the community who might not be familiar with things like API keys. Does anyone have any advice about how this should be handled? Has anyone else written a client side app for TWFY, if so how do you handle it? I don't want to distribute the code (which will be open source) with my API key in it so what is the best way to deal with this? Any advice or ideas gratefully received! Thanks Liam Green-Hughes _______________________________________________ Mailing list [email protected] Archive, settings, or unsubscribe: https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public
