Mobile QBN
- Started
- Last post
- 32 Responses
- aliastime0
I don't see anything either.
- rosem0
updating, sorry. I'm going to upload tomorrow with updates.
- SteveJobs0
you might want to offer a disclaimer/privacy policy to everyone here notifying them of how you are using their login information, and ensure them none of their data is being stored on your website/database.
i'm sure you aren't planning anything malicious, but not doing so is a bit shady.
- rosem0
* i'm not storing any information on my server at all.
* all content is coming from QBN and sent back to QBN.
* however, I can't guarantee that it's 100% secure (at this point).
* use at your own risk.
- SteveJobs0
"all content is coming from QBN and sent back to QBN."
not really. you are acting as a proxy here as the request is going to:
http://www.rosem.com/dev/qbn/php…so before you pass that data to qbn, you could take their username/password and store it. it's a good idea that everyone understands this before they start using your site.
- SteveJobs0
"however, I can't guarantee that it's 100% secure (at this point)."
i don't really see this as an issue. qbn doesn't secure their requests either.
- SteveJobs0
"I'm not going to spend my time building an app to steal QBN account passwords. I promise. :)"
of course not. i don't think anyone here would assume that. you're obviously doing this because you enjoy using this site and you want to be able to take the experience with you anywhere. i get it.
it's just that, everyone here might not understand how this technology works, and it's their right to know that you are in-fact, 'handling' their credentials. as a responsible developer, it's your duty to inform them. this is why you see privacy policy's all over the web, or at atm's, etc. i'd do the same thing if my app were released.
- rosem0
you can now respond to posts. I'm working on optimizing the images for web this week — it should cut down on bogging down your iphone.