@gerarde Wondering why shares route through AddToAny is fair, but you assumed a lot that isn’t true. The plugin has an FAQ, “Why do share links route through AddToAny?”:
This routing enables publisher customization, visitor personalization, and keeps the AddToAny plugin remarkably lightweight without the need for constant plugin updates. In AddToAny menus, visitors see the services they actually use. On mobile, AddToAny presents the choice of sharing to a service’s native app or mobile site and the preference is used on the next share. Publishers take advantage of AddToAny services such as email templates, Twitter templates, URL shortener & parameters, and more. Just as service icons change, service endpoints change too, and AddToAny is updated daily to reflect service endpoint and API changes.
Routing isn’t even used for all buttons. Some major services have standard protocols on mobile (SMS, email, messaging apps), so the usual AddToAny route is bypassed when no AddToAny server-side features are used for the service.
I don’t want anyone seeing what I share, except who I choose to share with.
Same. That’s why AddToAny is HSTS preloaded in browsers (for secure sharing over networks) and doesn’t know — or want to know — who you are (no user accounts, and no personal information is ever requested).
AddToAny remains a universal routing service; it’s not a sharing destination that actually knows you and what you share.
