Hi Norman,
the issue with different share counts for http and https is a tricky one. In general we do not know, if a social network is counting them separately for a certain site or not. Unfortunately they do not handle it consistently. But the more pressing issue is, that it would double the amount of request and would probably push many people into the request limits of the networks. Of course there are ways around that, for example by storing it in the database tables for each post permanently instead of in the transient cache, but overall that would take quiet a lot of work for something that will eventually become less and less important, since new content is not affected. The value of content degenerates over time and so does the value of the share counts of outdated content. We added the option to hide zero share counts, so that old posts do not show any share counts for the most part.
So long story short: I don’t see us putting the time and effort into this any time soon (Maybe I’ll add the option to simply double all request for http and https, but with a big red warning to use on on risk of getting blocked). I still hope the social networks will take care of this inconsistency as some of them already do. Facebook responded a while back that they are aware of this issue, but do not see it as a high priority since in the long run only up to date content matters (that was about a year ago).
Cheers
JP
Hey JP,
thanks for the detailed reply and your opinion about it.
On the one hand I’m totally with you and the social networks. But on the other hand I’m very disappointed about their point of view. Some of the good old content will still be relevant over time but the ideas behind social networks is to publish regularly so that people will still participate. :/ For my opinion it’s not always necessary nor valuable to reinvent the wheel (content) over and over again.
So let’s hope they will finally do something and thanks alot for your time
Cheers
Norman
