People who code: we want your input. Take the Survey

Hot answers tagged

16

According to: http://instagram.com/developer/endpoints/media/ At this time, uploading via the API is not possible. We made a conscious choice not to add this for the following reasons: Instagram is about your life on the go – we hope to encourage photos from within the app. However, in the future we may give whitelist access to individual apps ...


4

I think you answered your question yourself. You need to have Open Graph tags in your webpage head section. Mainly following are the meta tags you will need to add. <meta property="og:title" content="The Rock" /> <meta property="og:type" content="video.movie" /> <meta property="og:url" content="http://www.imdb.com/title/tt0117500/" /> <...


4

The buttons themselves don't need to be loaded from the social site at all. For example, both Facebook and Twitter let you simply open a window with a special URL, which shows a "New post" window with your page's URL already filled in. For Facebook, the documented URL appears to be: https://www.facebook.com/dialog/share?app_id=<APPID>&display=...


2

While the share symbol is not in the Unicode range, maybe this workaround will help you: http://jsfiddle.net/chillybang/a7v5obqj/ HTML <span class="share">&lt;</span> CSS .share { font-weight: bold; position: relative; } .share:before { content: "."; font-size: 2.2em; position: absolute; bottom: -2.5px; left: -...


2

As an alternative to "rolling you own" sharing buttons you could use the shariff library. It's goal is maximum privacy: https://github.com/heiseonline/shariff


2

I don't think this happens like you think it does... From your description, it sounds like you're expecting browsers to just follow URLs to preload whole pages - but from what I know it's a lot more explicit than that... The "Prefetching, preloading, prebrowsing" article on CSS-Tricks goes some way to dispel your presumptions. The wiki page on "Link ...


1

Its a hack, but it works <span style="transform: rotate(90deg);">V</span>


1

Actually it was a problem on Facebook's side. They didn't give us any details on what it was: https://developers.facebook.com/bugs/457940337876559/ https://developers.facebook.com/bugs/1742979185993892/


1

Both are fine, but the URL path has a slight benefit over subdomains, because the backlink juice would be concentrated on one domain. Managing one domain is also easier than multiple subdomains. In all cases, I would put the id of the question/answer in the url, because it will make the url unique for sure.


1

Using the default Facebook sharer, it would see URL's with different query parameters as completely separate URL's so subsequently, not detecting that 3 other Facebook user's have shared the same content. You'd have to come up with a workaround to this.


1

You can't get there with forwarding, as forwarding will, by definition eventually take customers directly to the final location. What you need is reverse proxying. A reverse proxy works by going to a an address, and having that address proxy the request to a different address at the final site. This does, of-course, mean a double-up of bandwidth use - ...


Only top voted, non community-wiki answers of a minimum length are eligible