Use a jsMsg or the new version of it, and deliver images as data url in the css. If you use ordinary lmages in a scripted html-tingy it will load a long time after the dom is generated. Most social networks can be accessed with a single url, but it is a lot of sites right now. We have 36 at no.wp and that isn't everyone.
So far as to create the request to the social network to do a posting isn't really difficult. The problem is if you add text and images in the posting and you want the posting to update as the article itself is changed. John On Sun, Oct 23, 2011 at 7:03 PM, Roan Kattouw <[email protected]> wrote: > On Fri, Oct 21, 2011 at 3:27 PM, John Du Hart <[email protected]> wrote: >> There's also the technical problems this would incur. Each of these buttons >> require yet another HTTP request each, which would make the hard work by RL >> team moot. >> > That depends on whether the icons are hosted offsite or not. If the > icons are hosted at WMF, we can use data URI embedding as we normally > do for icons, and there would be virtually no additional cost. If the > icons are hosted offsite, we would indeed incur one extra HTTP request > per icon, but we would also be sharing private data (IP address and > Referer header) with a third party, which is forbidden in our own > privacy policy. This is the reason why we absolutely cannot have the > Facebook Like button: Facebook makes you use an FB-hosted button image > (and JS too, I think), collects data from every user that views the > Like button even if they don't click it (this is the part that > violates the privacy policy), and disallows self-hosting. > > Roan > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
