You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2020. It is now read-only.
There's a share count mismatch between http and https urls for (some) social networks. This means that even if a website (like meddelare.com) which always redirects to https gets shared with a http link (for any reason), the share count will be lower than expected.
My suggestion is to add automatic addition of the counts in meddelare-node-counters, where it would also be known which networks need separate http/https count requests.
Does any social network merge http and https counts internally?
Is it ok to have the default be to merge http and https? To me it seems like something to opt out of, rather than opt in to.
Websites which do not strictly redirect to either http or https would also benefit (be able to display higher share counts) from this change.
For websites strictly using (either http or) https, there might be other ways to solve this problem -- perhaps by (somehow) forcing social networks to re-index the http url, which would then redirect to https and make sure the the canonical url has been set to use https. Any concrete suggestions?
Domain url examples
It looks like Twitter and Facebook doesn't add http and https counts, while Google Plus does (the small difference below can be due to internal caching).
There's a share count mismatch between http and https urls for (some) social networks. This means that even if a website (like meddelare.com) which always redirects to https gets shared with a http link (for any reason), the share count will be lower than expected.
My suggestion is to add automatic addition of the counts in meddelare-node-counters, where it would also be known which networks need separate http/https count requests.
Websites which do not strictly redirect to either http or https would also benefit (be able to display higher share counts) from this change.
For websites strictly using (either http or) https, there might be other ways to solve this problem -- perhaps by (somehow) forcing social networks to re-index the http url, which would then redirect to https and make sure the the canonical url has been set to use https. Any concrete suggestions?
Domain url examples
It looks like Twitter and Facebook doesn't add http and https counts, while Google Plus does (the small difference below can be due to internal caching).
meddelare.com
https://meddelare.com/
https://meddelare-node-server.herokuapp.com/?networks=facebook,twitter,googleplus&url=http://meddelare.com
https://meddelare-node-server.herokuapp.com/?networks=facebook,twitter,googleplus&url=https://meddelare.com
dnssec-name-and-shame.com
https://dnssec-name-and-shame.com/
https://meddelare-node-server.herokuapp.com/?networks=facebook,twitter,googleplus&url=http://dnssec-name-and-shame.com/
https://meddelare-node-server.herokuapp.com/?networks=facebook,twitter,googleplus&url=https://dnssec-name-and-shame.com/
google.com
https://www.google.com/
https://meddelare-node-server.herokuapp.com/?networks=facebook,twitter,googleplus&url=http://www.google.com/
https://meddelare-node-server.herokuapp.com/?networks=facebook,twitter,googleplus&url=https://www.google.com/
The text was updated successfully, but these errors were encountered: