WindPowa
- Quote
- Report Post
- Posted: Fri, 28 Oct 2011 06:01:59 +0000
allvanishing
Users are made clear with our notices of permissions that with using BetterGaia, they expect BetterGaia to preform as expected with the help of BetterGaia's own code and it's developer's services. Users cannot expect to deal with a non-working, incomplete product because all of the developer's tools are barred from being used by themselves.
Also, using Chrome's developer tools and analyzing BetterGaia's requests are a form of reverse-engineering.
Also, using Chrome's developer tools and analyzing BetterGaia's requests are a form of reverse-engineering.
◢ ♜ ✜ ♞ ✜ ♜ ◣
Here is what the aforementioned permissions notice says:
Quote:
► PERMISSIONS FAQ
We understand your concerns about the permissions Chrome asks to use BetterGaia. Many extensions similar to BetterGaia in the Chrome Web Store require such permissions as we do. Here are the reasons as to why Chrome requests these permissions:
* "Your data on gaiaonline.com"
BetterGaia adds features to Gaia by placing JavaScript and CSS into the page,
which needs the correct permissions to be able to so.
* "Your browsing history"
BetterGaia has to open new tabs for pages such as your Options.
BetterGaia will NEVER access your browsing history at any time.
We understand your concerns about the permissions Chrome asks to use BetterGaia. Many extensions similar to BetterGaia in the Chrome Web Store require such permissions as we do. Here are the reasons as to why Chrome requests these permissions:
* "Your data on gaiaonline.com"
BetterGaia adds features to Gaia by placing JavaScript and CSS into the page,
which needs the correct permissions to be able to so.
* "Your browsing history"
BetterGaia has to open new tabs for pages such as your Options.
BetterGaia will NEVER access your browsing history at any time.
Additionally, using Google Chrome's own tools is not reverse-engineering; it's simply using the browser.
Whether BetterGaia's requests show up there or not is not necessarily due to a conscious reverse engineering act; one might simply need to run the developer tools on a gaiaonline.com page, and notice that there is an extra request there that, upon inspection of gaiaonline.com's JavaScript code (not BetterGaia's), this request cannot have been made by the page itself, therefore deducting that this request must have been initiated by BetterGaia.
Was that how I found out? No, I simply used intuition from past knowledge. Did that violate the end-user agreement? Not sure there was one there at the time, but perhaps I did.