View Single Post
Old 02-19-2012, 04:41 AM   #8
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
In my opinion, using the x-fsn header in an application that actually enhances the kindle, like building a better web browser that works on the kindle, is acceptable use. Using the x-fsn header to download unapproved files, or to export amazon 3G service to a non-Kindle computer (tethering) is unacceptable. Tools like corkscrew that supply 3G service to any application or external device fall into the second (unacceptable) category. You should build x-fsn support into each application that needs it, and follow the amazon rules about what content may be downloaded by their webkit browser. Of course, Wi-Fi access should bypass the amazon proxy and use the local Wi-Fi connection, to download unrestricted content. The application must be "3G-aware" and follow the rules when it uses 3G.

At least, that is my opinion. Just remember the Golden Rule here, and behave accordingly...

Thanks.
geekmaster is offline   Reply With Quote