The following comments are all IMHO not those of Microsoft.......blah blah blah.... you get the idea!
As readers will be aware, I recently linked to content on a third party site. My intent was to advocate the author's content to my followers(both of them!) as in my view it was worthy of attention. Unfortunately the author of the original site received so much attention as a result of my post that they appear to have drowned in traffic. They ended up removing their content.
The author of original content SHOULDN'T suffer as a result of a high profile blogger linking to them. I've read some discussion in the blogsphere on this topic though little sign of progress. What do you think? Where are we going with this?
After all my readership is tiny compared to highly respected Bloggers such as the Scobleizer - imagine if he linked to your content which may be hosted on server @ your house which is only connected by DSL. Yet - as an author I'd Love it if Robert Scoble linked to my content even if I was a home blogger :-)
One option would be for the referrer (me in this case) to negotiate to host the content of the original author. My concern is that the content author shouldn't loose out on the kudos/profile.
Thoughts? Gimme some useful feedback.
add .nyud.net:8090 after the domain itself, and it serves your content in a /. proof way.
Obviously doesn't work for sites which require user feedback etc, but very useful for static content.
PS To give 'GoogleLove' to the site, make two links, one to the original and one to the Coral Cache. Add the shiny new rel="nofollow" attribute to the link pointing to the Coral cache to prevent PageRank dilution. Voila, Googlelove.
This isn't about the "How to turn your Windows machine into a Linux box" link, is it? :-)
No interesting feedback from me, just that lots of people call this a slashdoting... (Because slashdot is known for sometimes linking to websites with a small connection and "slashdoting" them in result)
If an expert, such as Steve, finds content that he thinks deserves to be viewed by a wider audience, then surely it is in both the author's and others' interests to have that content announced. The recommender could approach the author beforehand to check that their site could handle the (probable) increase in traffic, or offer to host content on their behalf. I, for one, would be more than happy if an expert decided to recommend some of my content to the general 'net community, and would gladly give a copy to be hosted elsewhere, provided the proper kudos was given.
Unfortunately it is not the GoogleLove or MSNLove that causes the traffic it's the clickthroughs. I have seen what being mentioned on primetime tv or slashdotted can do to a site and it aint pretty (not my own site btw) but after the initial torrent of traffic the longer term affect is beneficial. All you can do is give prior warning so they can in turn warn their ISP that there might be a spike coming.
Mirroring content is an option but what might happen is search engines see the duplicate content and penalise the site with the lower PR - in the case you mention of being scobled the higher pr would be the blog not the content, meaning that content might dissapear from the search results!
I've actually been scoblized, on a tiny web server, with a 20Mb drive, a PIII 600, 512Mb of memory, running Windows 2003, hosted in my top room, running over a wireless bridged connection to my 256k up DLS connection.
And the code for my site is, err, my code. You know how it is, you knock something out you'll make better, smaller, faster, real soon now.
It actually wasn't bad.
slashdot on the other hand would be a killer. For days.
The problem with approaching people is how much diligence are you able to do about their server. Checking who owns the IP might be a start, but that gives no real idea how bandwidth they have, or how large their server is.
I liked the hits because I'm a hit slut; others may not, but there's no way to tell until you ask them.
I'd say if you're concerned mail them. There's always coralised links ( http://coral.scs.cs.nyu.edu/wiki/wiki.php/Main/FAQ ) or freecache ( http://www.archive.org/web/freecache.php )