Archive for May, 2007

PayPerPost is spamming ReviewMe Affiliates

PayPayPost Sucks

So I received the following email today from some guy named Chris Abraham:

On behalf of the gang at PPP I wanted to help you get rid of ReviewMe as the middleman and do it direct with PayPerPost Direct, www.payperpostdirect.com. PayPerPost Direct would allow you to keep $90 for that post rather than the paltry $50 ReviewMe is paying you.

Check it out at http://www.payperpostdirect.com. Feel free to ping me any time if you have any questions - or for any reason, for that matter. The official announcement is on the PPP blog, http://blog.payperpost.com/2007/05/payperpost-direct-overview.html.

Cheers,

Chris

– Chris Abraham cja@well.com +1 (202) xxx-xxxx
http://chrisabraham.com http://cabraham.com

What a great strategy.. login to a ReviewMe account and start spamming all of the ReviewMe affiliates to get them to switch over to your service. Nice! Yeah, I may not agree with that fact that ReviewMe takes 50% of the revenue but hey its better than nothing right? Chris, I do appreciate the help but please don’t go around spamming people about it.

Comments (3)

Google Drops $100 Million on FeedBurner

FeedBurnerGoogle is in the final stages of acquiring RSS publisher FeedBurner.com for a cool $100 million. FeedBurner publishes the feeds from a number of large companies like AOL, Newsweek and also claims to be handling over 720,000 feeds. Most of the feeds FeedBurner handles is from blogs.

I can see Google integrating AdSense into the RSS feeds. Ads in RSS feeds is becoming much more common these days as a large amount of people will read blog posts and or stories from their RSS reader only. So far Google has remained kind of quite about the acquisition. Maybe we will see an official announcement sometime next week. Congrats to FeedBurner..

Comments

Month of Search Engine Bugs?

Below is a brief description from the site:

Purpose of this Month of Bugs is a demonstration of real state with security in search engines, which are the most popular sites in Internet. To let users of search engines and web community as a whole to understand all risks, which search engines bring to them. And also to draw attention of search engines’ owners to security issues of their sites.

During the month everyday will be publish vulnerabilities in most popular search engines of the world. Cross-Site Scripting vulnerabilities in particular. Everyday will be publish vulnerabilities in different engines (minimum one publication at a time, but there will be bonus publications also).

When is this trend of Month of Blah Bugs going to end? Anyway, I am wondering if they will have any kind of Blackhat SEO type of stuff they release. Like how to get 200,000 pages indexed in Google in one night or something. I highly doubt it, but who knows what they might have to release.

You can read more on their site: http://websecurity.com.ua/category/moseb/

Comments

GetClicky With It!

GetClickyGetClicky.com is a web analytics 2.0 which provides some really neat features including backlinks information, exit page and search engine keyword information. You can see a demo of the product here, and or register for a free account. What I like most of all about GetClicky is the interface is really clean, and very easy to use.

Comments

Vector Rewrite Attacks

Barnaby Jack, a security researcher at Juniper Networks has released a paper which is about exploitable NULL Pointer vulnerabilities on ARM and XScale architectures.

NULL pointer dereference flaws typically account for the majority of published denial-of -service attacks, both locally and remotely. A NULL pointer dereference occurs when a pointer with the value of 0 is assumed to be a valid memory location, and that pointer is then accessed. A NULL pointer dereference is rarely more than an annoyance, with the worst case scenario typically resulting in a software crash. A write from, or read to, the memory address 0×0 will generally reference invalid or unused memory.

You can read the white paper here:

Exploitable NULL Pointer Vulnerabilities on ARM and XScale Architectures

Comments