3 ms·
For something as simple as a like button, surely they could just include a unique image url wrapped in a link, and generate the image on demand to update number
by grey-area 13y ago
For something as simple as a like button, surely they could just include a unique image url wrapped in a link, and generate the image on demand to update numbers?
I do find this trend of including third party js on websites worrying. At present I've got twitter js for feeds on a few websites, and even that worries me, but it seems every website now wants me to include their js for a like button or any other service. It's simple for them to update, track users etc, and I see the attraction, but it's also incredibly dangerous if this practice proliferates. Soon we'll be including js for tens of sites, not all of which are perfectly secure, and if any one of them is hacked, it means you're serving malignant code on your domain to every user.
While js is sandboxed, it has full access to any data displayed or entered on a page, and can trigger silent transmission of that data to other servers. So by including the js you're trusting that website never to be hacked, and never to misuse your users' data. I'm waiting in trepidation for the big scandal when a large site with js served all over the web is hacked, and that js is used to silently record millions of logins and details over a few hours/days before it is discovered.