"abuse" is debatable, but technically it was when developers began using the client-side code that Google uses, on their own sites, while interfacing with the google maps servers to use resources the servers were originally just providing to the google maps website. This was possible because Google cannot restrict access to the servers to their own website because it's actually the browser that makes the connections, not the website. (sorry for the run-on)
Their solution was to create a vastly easier to use API, well-documented and unobfuscated, costing websites only the limit of a finite (large, can't remember it at the moment) number of accesses per day.
As I scanned through the critical discussion of this new compilation of services by Google, I realized how calculated their marketing efforts are. It now seems quite probable that there are any number of Google employees currently tracking this thread on Slashdot. A free analysis by one of the most vocal net cultures of geeks (and n00bs)!
Use FeedBurner as your public newsfeed to let their smart servers handle the brunt of the attack, plus you get stats and format independence (publish both RSS & Atom from 1 feed).
Check their features status page for details on what they've been implementing since their initial release, and what they plan on implementing. It's very encouraging!
Amen to that. Being responsible for the administration of about 10 linux boxes that each provide a unique variety of services, Webmin has been invaluable. If I didn't have Webmin, all of my tasks performed through the shell would take about 10 times longer than they currently do from a browser that can lay out my options much more nicely.
The key is to know/learn how to do what you want to do from the shell first, so that you have the understanding (and for emergencies), but to then use Webmin to boost your efficiency and help remind you of things that a blank console doesn't.
According to the original source at Internet Storm Center, there are 2 different infections going on. M$ IIS servers are vulnerable to an exploit that is undetectable by current virus scanners. However, visitors to infected servers are safe, because a separate method of infection is used there: a common JavaScript exploit, and a common trojan horse is downloaded. The trojan horse IS detected by current virus scanners, it's a "known" trojan horse.
And it manages to get the most relevant results to you in well under a second. Do you think they would be able to acheive this if most (if not all) of the pages were stored on the hard drive?
Don't assume that just because it searches fast, there is no way it's on hard disk. At such a large scale, bandwidth becomes more of an issue than hard drive access speed. Just read about the filesystem they invented for themselves. Don't assume that they're simply mirroring the unix filesystem hierarchy that most websites use. It's a complex database. MySQL and PostgreSQL provide faster access times than simply storing a file on the hard drive, depending on how you're accessing it, and all those are are interfaces to storing data on the hard drive in a different structure.
Slashdot Mirror
curl -sI slashdot.org|head -6|tail -1
"abuse" is debatable, but technically it was when developers began using the client-side code that Google uses, on their own sites, while interfacing with the google maps servers to use resources the servers were originally just providing to the google maps website. This was possible because Google cannot restrict access to the servers to their own website because it's actually the browser that makes the connections, not the website. (sorry for the run-on)
Their solution was to create a vastly easier to use API, well-documented and unobfuscated, costing websites only the limit of a finite (large, can't remember it at the moment) number of accesses per day.
As I scanned through the critical discussion of this new compilation of services by Google, I realized how calculated their marketing efforts are. It now seems quite probable that there are any number of Google employees currently tracking this thread on Slashdot. A free analysis by one of the most vocal net cultures of geeks (and n00bs)!
that we can speed up light too?
Use FeedBurner as your public newsfeed to let their smart servers handle the brunt of the attack, plus you get stats and format independence (publish both RSS & Atom from 1 feed).
Check their features status page for details on what they've been implementing since their initial release, and what they plan on implementing. It's very encouraging!
Amen to that. Being responsible for the administration of about 10 linux boxes that each provide a unique variety of services, Webmin has been invaluable. If I didn't have Webmin, all of my tasks performed through the shell would take about 10 times longer than they currently do from a browser that can lay out my options much more nicely. The key is to know/learn how to do what you want to do from the shell first, so that you have the understanding (and for emergencies), but to then use Webmin to boost your efficiency and help remind you of things that a blank console doesn't.
According to the original source at Internet Storm Center, there are 2 different infections going on. M$ IIS servers are vulnerable to an exploit that is undetectable by current virus scanners. However, visitors to infected servers are safe, because a separate method of infection is used there: a common JavaScript exploit, and a common trojan horse is downloaded. The trojan horse IS detected by current virus scanners, it's a "known" trojan horse.
I could use a GMail invite... could you just go ahead and send it to my GMail account? justinpw @ gmail.com ;-)
PenguinComputing Workstations - very powerful workstations, linux preinstalled, guaranteed compatibility