Consider hosting all web resources and dependencies on your own domain(s). I don't need google, cloudfront etc etc to know i'm using a certain web application. Certainly not if i was paying for it.
Thanks for the feedback! This is the first time that we hear about this concern, but we will look into it. Serving these kinds of resources (fonts, icons) ourselves has a disadvantage in terms of caching, so we'll have to decide if it's worth the trade-off.
It's not that I haven't heard about leaking traffic to third parties before. What I meant is that so far none of our users have complained about this being a concern for them.
Comments
Consider hosting all web resources and dependencies on your own domain(s). I don't need google, cloudfront etc etc to know i'm using a certain web application. Certainly not if i was paying for it.
Thanks for the feedback! This is the first time that we hear about this concern, but we will look into it. Serving these kinds of resources (fonts, icons) ourselves has a disadvantage in terms of caching, so we'll have to decide if it's worth the trade-off.
I'm surprised to hear a webapp dev say it is the first time he hears about leaking traffic to third parties. Kind of worrying.
It's not that I haven't heard about leaking traffic to third parties before. What I meant is that so far none of our users have complained about this being a concern for them.