LinkedIn份额计数API(/countserv/count/share)始终返回"0"， [英] LinkedIn share count API (/countserv/count/share) always returns "0"

问题描述

很容易在JSON结果中看到:

Easily seen in the JSON result from this:

https://www.linkedin. com/countserv/count/share?url = https://www.linkedin.com

当前返回的是:

    IN.Tags.Share.handleCount(
     {
      "count":0,
      "fCnt":"0",
      "fCntPlusOne":"1",
      "url":"https:\/\/www.linkedin.com"
    });

显然，它会影响网络上的大多数LinkedIn共享按钮/计数器，包括WordPress和其他博客.自上周下旬(2018年1月13日)以来，这已被``打破''.

Apparently it affects most of the LinkedIn Share buttons/counters out there on the web, including WordPress and other blogs. This has been "broken" since late last week (13 Jan 2018).

我在LinkedIn支持下打开了一张票.回复是在此处发布，因为这是LinkedIn开发人员支持所在的位置.希望得到这样的答复:糟糕，我们会解决此问题."或者，如果故意使它瘫痪，则发布这样的公告. (Twitter在几年前也采取了类似的措施.这在开发人员中并不受欢迎，但我们已经前进了.)

I opened a ticket with LinkedIn support. Response was to post here, as this is where the LinkedIn Developers support resides. Hoping for a response that says "Oops, we'll fix this." Or, if deliberately crippled, an announcement that says so. (Twitter made a similar move a few years ago. It was unpopular among developers, but we've moved on.)

推荐答案

共享计数服务又恢复了运行，并像以前一样工作.中断是故意的(显然)，但是暂时的.

The share count service is back in operation, working as it was before. The outage was deliberate (apparently) but temporary.

据我所知，这是一个未公开的API，但它是"LinkedIn Share"按钮的组成部分，该按钮在全球无数网站/博客中使用.因此，LinkedIn没有保持该服务运行的合同/义务...因此，应注意非LinkedIn组件中服务的使用者.

As far as I know this is an undocumented API, but it's integral to the "LinkedIn Share" buttons that are used in countless websites/blogs around the world. As such, LinkedIn has no contract/obligation to keep that service running...so consumers of the service in non-LinkedIn components should beware.

这篇关于LinkedIn份额计数API(/countserv/count/share)始终返回"0"，的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！