Index a DMCA Complaint with the assistance of Google Docs

The instant you distribute a revamped item on your online presence or web journal, the "net scratching" bots far and wide will spring into movement. They'll duplicate your items to distribute them on different homepages and the way that you syndicate substance through RSS channels produces their "duplicate-glue" work even less difficult.
These bots are regularly nonchalant – they could infrequently adjust your sections before republishing them – and therefore it ends up absolutely effortless for you simultaneously to recognize the destinations that are utilizing your substance without liberty. For example, I join a line "This story was basically printed at Digital Inspiration" to the food and along these lines a fast Google pursuit can uncover the names of destinations that are probably duplicating my stories.
The most straightforward gameplan to bargain with within the web based world written falsification is that you send a DMCA acknowledge to search applications, the network hosting supplier and the broadcasting associates (like AdSense) of the culpable destination. Google Search needs you to fax the DMCA perceives, AdSense offers a digital shape while most net accommodates receive DMCA over message.
Identify Copies of your Work with Google Docs
It is pretty effortless to compose a DMCA protest but there's one area in the frame that would include a small exertion – you ought to furnish a post of URLs of pages that "professedly hold encroaching material" and additionally the comparing URLs that hold the first work.
Since you have been searching for a device that can programmedly produce this record for you, take a glimpse at this Google Docs Sheet. Verify you are marked in with your Google Account and the utilization File-> Make a duplicate to make your particular working duplicate of the Google Sheet. Then put in your destination's RSS channel URL in the Cell B3 and the URL of culpable locale in Cell B4 and the sheet will make the information you require for the DMCA. 
What happens obsolete
Here's the means by which the above Google Docs sheet work-it take your RSS channel and figures the title and the URL of your 10 just printed stories utilizing the ImportFeed capacity.
The sheet then runs a marked Google Search for each and every of the 10 stories to figure if a story with the same title exists on the culpable post. Since a duplicate is found, the URL of that page is removed from Google Search utilizing XPath and ImportXML as demonstrated underneath.
=ImportXML(CONCATENATE("http://www.google.com/search?q=intitle:%22", A6, "%22 post:", $B$4), "//a[@class='l']/@href")
In the event that you are getting a N/A for some fields, it either demonstrates that the specific story was not found on the culpable destination or it might be interim situation with Google seek too.

---

This story, File a DMCA Complaint with the help of Google Docs, was originally published at Digital Inspiration on August 21, 2011 under Dmca, Google Docs, Internet.

Google Offers Cash For Security Bugs In Its Web Applications

Smart companies tolerate security researchers who hack their products. Smarter companies pay them for it.
Put Google in that second category.
On Monday, the search giant announced on its security blog that it’s expanding its “bug bounty” program, a rewards system that offers payments of up to $3,1337 to anyone who can demonstrate a serious security vulnerability in its software. Instead of merely focusing on Chromium, the open source code behind its Chrome browser, those bounties now apply to the company’s Web application bugs, too.
Any hacker that finds an exploitable bug on a Google site that hosts “highly sensitive authenticated user data or accounts”–domains like Gmail, YouTube, Blogger or any other Google service–can tell Google about the issue privately and earn anywhere from $500 to $3,1337 for especially clever finds. (That 1337 signifies “leet”, semi-ironic hacker jargon for an “elite” practitioner of the digital dark arts.) If any researcher would rather donate their bug bounty to charity, Google is offering to match it.
On top of giving independent researchers an incentive to help eliminate vulnerabilities in Google’s code, the program may also help keep those bugs private before they’re fixed. Google’s rewards come packaged with restrictions on how the researcher can publicize his or her find. “We believe handling vulnerabilities responsibly is a two-way street,” Google’s security team writes. “It’s our job to fix serious bugs within a reasonable time frame, and we in turn request advance, private notice of any issues that are uncovered.”
Google is far from the only bug-buyer on the market: Firefox-creator Mozilla, Verisign’s iDefense, and HP’s Zero Day Initiative all offer bounties for vulnerabilities. (Last month a twelve-year-old earned $3,000 by exposing a bug in Firefox.) But those companies pay for bugs in traditional desktop applications, not Web-based apps. Google’s program doesn’t apply to its client programs like Picasa or Android, but opens the bounty field to common Web bugs like cross-site scripting and cross-site request forgery, weak points that Web-focused security firms like White Hat Security say exist in over 80% of sites.