2 ms·
In general, you can't assume people won't deep-link your content, and that includes embedding. Technically, no, you can't with current protocols. However, this
by Silhouette 11y ago
In general, you can't assume people won't deep-link your content, and that includes embedding.
Technically, no, you can't with current protocols. However, this has been regarded as bad manners ("hot linking", "bandwidth theft", etc.) since forever.
Taking steps to protect against or take advantage of traffic spikes is the responsibility of a content provider.
The trouble is, with the increasing concentration of attention on the web in the hands of a few high profile traffic aggregators and social networking sites, this kind of argument holds less credibility than it used to. It's all very well saying if you put something on-line then you're responsible for supporting it, but the reality is that someone else suddenly diverting large amounts of traffic to your site is statistically indistinguishable from a denial of service attack.
If it's qualified traffic and being directed to somewhere you welcome the extra visitors, you might appreciate it. If it's unqualified traffic and overloading your servers at your and/or your normal visitors' expense, you probably won't appreciate it. If it's not even being directed to your normal site but instead deliberately freeloading on your servers and bandwidth via hot-linking, I think you're at least well into a grey area in terms of both ethics and legality.
- fixermark 11y agoPerhaps more accurate to say "Taking steps to manage traffic is the responsibility of a content host." People make HTTP requests for all kinds of reasons. If you don't have someone managing your hosting, the responsibility defaults to you. That's one of the reasons there's an ecosystem of cloud providers now to shoulder the burden of this implementation detail that people don't want to know just to make content available online. But the core point stands: It's the Internet. You can't trust the clients to behave; assume the worst of user input. Calling out Daily Mail as terrible (which they are, and which people should do at every opportunity ;) ) doesn't solve the root problem that nothing about the protocols restricts using <iframe> to pull in cross-domain content.
- Silhouette 11y agoIf you don't have someone managing your hosting, the responsibility defaults to you. That's one of the reasons there's an ecosystem of cloud providers now to shoulder the burden of this implementation detail that people don't want to know just to make content available online. I think it is extremely dangerous to argue that anyone who wants to publish safely on the Internet should be required to do so via some huge cloud provider. We shouldn't conflate what is technically possible because our old protocols give too much trust with what we consider ethical or legal. You can't trust the clients to behave; assume the worst of user input. By the same argument, spammers and those PPI cold callers are OK, because we agreed to have e-mail accounts and phones. In reality, bad actors like this screw up the system for everyone, and dealing with people who screw things up for other people is why we have laws. Treating negligence or particularly actively hostile action as the victim's fault is usually a very bad idea.