Earn cash with google

-
I was reading slashdot this morning and saw an interesting ad pop up. It was for a site called http://www.earncashfastwithgoogle.com. It sure smelled funny, but thought it was an amusing approach. From what I can determine it's something like:

#1 Target advertising
#1 Ask a bunch of questions to "Qualify" the applicant (Optional?)
#2 ask for some cash up front to "ship" the "instructions" (Dubious)
#3 Profit!

First of I took [very quick] peek on google about this and found a couple of complaints: here . Then, I started thinking about it... What better way to make money than to charge people a very low amount of money for instructions on how to make money.

From what I can see, while this really seems like it could be a bit unethical, it is an interesting way to make money. If one keeps the number of people "in" the network widely distributed enough and keeps the costs low, this could continue this for quite some time. I'm not a lawyer, but this might even be legal in the US (Let the buyer beware). It hardly seems illegal to charge someone $2 for information about how you made money charging people $2 for information about how to make money.

Now, from what I can see, the proposed business plan is actually something about posting links on google. While this may be a legit way to make money, I'm still trying to figure it out. I can see how perhaps you could make money if your adsense account was well targeted, but this would require a pretty high clickthrough rate. The other thing that might be is to build a network of zombies to click on web sites that will change a pages SEO ranking. This is certainly ethically dubious and I would probably want to shy away from it.

Now mind you, I'm not sure exactly what the "instructions" really are as I am hesitant to give out my personal information, but it certainly sounds shady. If, in fact, it is one of the things outlined above it's probably on pretty shaky ground. Probably, if I really where interested, I could get a PO box and see what they're promoting.

Comments

Post a Comment

Popular posts from this blog

Please use ANSI-92 SQL Join Syntax

-
Image
Way back in 1992, a standard was published for SQL. In it, the syntax for specifying joins in SQL Database was finally standardized. This was a good thing because (for folks who've been doing this a while), trying to decode the vagaries of how various Databases handled outer joins could drive you bonkers yielding different results depending on the parse order of things in the from and where clauses. Unfortunately, some DBMS vendors took a while to adopt this standard (Oracle didn't support it until 2001), but at this point if you're using a major RDBMS and NOT using it, you're probably mired in a tradition or habit that bears changing. As an example of what I'm describing, here are some examples of what I mean. Old School (no standard syntax + implementation and evaluation of predicates varied by vendor [and query]): select * from customer, order where customer.customer = order.customerid ANSI way (agreed to standard, predicate evaluation has some rules ...
Read more

The difference between Scalability, Performance, Efficiency, and Concurrency explained

-
I thought I'd give some explanation of the difference between scalability, performance, Efficiency, and concurrency. To make things more accessible (and because I'm watching a cooking show on TV) I'm going to use a baking metaphor to help explain the differences. In our case, the system in question is baking cookies for consumers. Scalability, is how well something responds to adding more resources. If we can double our capacity by doubling the number of resources, we've got linear scalability. In our baking example, if we add more ingredients, we can scale to a larger number of cookies. To contrast with our other metrics, this doesn't actually increase the performance of creating a single cookie (they still take 10 minutes to bake), and the efficiency is the same (we just have more capacity). We also cannot bake more cookies in a fixed time period, but over a larger time period we can produce more cookies. Performance is how fast something can get done, u...
Read more

the myth of asynchronous JDBC

-
Image
I keep seeing people (especially in the scala/typesafe world) posting about async jdbc libraries. STOP IT! Under the current APIs, async JDBC belongs in a realm with Unicorns, Tiger Squirrels, and 8' spiders. While you might be able to move the blocking operations and queue requests and keep your "main" worker threads from blocking, jdbc is synchronous. At some point, somewhere, there's going to be a thread blocking waiting for a response. It's frustrating to see so many folks hyping this and muddying the waters. Unless you write your own client for a dbms and have a dbms that can multiplex calls over a single connection (or using some other strategy to enable this capability) db access is going to block. It's not impossible to make the calls completely async, but nobody's built it yet. Yes, I know ajdbc is taking a stab at this capability, but even IT uses a thread pool for the blocking calls (be default). Someday we'll have async databa...
Read more