Re:Mozilla's secure coding guidelines for web developers
by zobzu on Saturday October 01, 2011 @08:59AM
(#3059963)
I'm not sure you can do this without voiding the agreement with twitter/facebook unfortunately.
I'd suggest the use of Ghostery (works on all major browsers) on the client side, and on the server site, well, you know, not use any like button :>
Re:Mozilla's secure coding guidelines for web developers
by skymt on Saturday October 01, 2011 @09:07AM
(#3059977)
Heise Online worked out a solution[0]: a two-click Like button. The first click replaces a placeholder with the official Facebook Like button. Facebook objected at first, but only because Heise tried to make their placeholder look official. A quick design change allowed them to keep it.
Re:Mozilla's secure coding guidelines for web developers
by zobzu on Saturday October 01, 2011 @09:11AM
(#3059984)
Yeah that's why I'm not sure. It could be attacked depending on the country I guess, and if you don't use a facebook-like icon, its hard to tell what you're going to like. Debatable I guess
Re:Mozilla's secure coding guidelines for web developers
by cowboyhero on Saturday October 01, 2011 @09:14AM
(#3059990)
twitter allows custom links/ buttons. These don't require on-loading JavaScript or any calls to their services.
Re:Mozilla's secure coding guidelines for web developers
by justincormack on Saturday October 01, 2011 @08:44AM
(#3059953)
Most GET requests to third part sites are fine, you need to be more precise.
Re:Mozilla's secure coding guidelines for web developers
by darrikmazey on Saturday October 01, 2011 @10:40AM
(#3060119)
A GET request for an embedded resource exposes the user's cookies for that domain and associates a user of one site as a user of another. This is fine when it is at the user's explicitly intended request, but when paired with certain sites known not to delete all cookies on logout, this is nefarious and should not be done.
Thank you for this.