When I launched trackmycv.com I had this exact problem, no one from the US seemed to know what a CV was, I had to buy whoreadsmyresume.com in the end. Almost everywhere apart from the US uses CV, not resumé, but CV doesn't seem to be used at all in the US.
Sorry, but this sounds illogical to me. How introducing some additional new CSS syntax is less Yet Another Syntax than just using some already established (but not popular) syntax? SASS has its user share (and easy to learn too) and new syntax has no users at all.
The new syntax has no users at all sure, but CSS has far more users than SASS or LESS will ever have. You're asking web developers and browser developers to learn and support a completely different technology, rather than adding an incremental, much needed improvement to something that has been used for many years.
I don't know if this is a snarky, rhetorical question, but there are many legitimate SEO companies out there. SEOMoz is a good example. A general rule is, if they guarantee certain rankings, avoid them, if they offer "directory submission" services, avoid them.
As soon as they start talking about "link building" my spam sense tingles. The same for "social media optimization".
So what is left? Glorified mod_rewrite hackery?
/edit: That's not a flame. I'm just interested what non shady SEOs do. The last time I looked into SEO it was all about rearranging your HTML so the spider would get to the content fast. And to put nofollows on your links to get the juice flowing the way you wanted.
But this wasn't that complex that it justified hiring an expensive SEO company. Sure, they all did that link building stuff too - but as noted above to me that's shady (it was mostly about spamming digg-like sites with top 10/5 articles).
I've started working with an SEO on a few things and I've seen a few things he does. mod_rewrite hackery is a part of it, as is validated HTML,/CSS meaningful titles, reducing load times as much as possible (basically doing well in all Yslow tests), accessibility stuff and other bits & pieces (like generating XML sitemaps, product feeds for Google product search etc etc).
A lot of this should be covered by any half decent site but as you may not find surprising, most sites out there don't know or don't bother.
Link building and social media optimization aren't necessarily spam activities (but I can see why you might correlate the two; there are a lot of shady link building operators out there and a lot of social media charlatans, for lack of a better word.)
While there are a lot of technical pieces to SEO (that go beyond mod_rewrite hackery, as you put it), most legitimate SEOs spend as much time on the marketing side of the equation. There are a few legitimate link building "tricks" out there, but most SEOs doing a good job at link building & social activities are focused on creating worthy content that ranks well in search and gets attention on social media sites.
BTW, nofollowing links to "sculpt" the way PageRank flows through your site doesn't work anymore - nofollow now "evaporates" the PageRank rather than forcing more of it through the other links on your page :)
Link building has all to do with making content that people find interesting enough to link to/talk about on social networks, and designing it to get links from certain types of sites with certain types of anchor text. As far as I know, Google is quite happy with that particular part of the SEO process, and it's firmly white hat.
Through the search results it's involved in. Actually, you wouldn't detect this for single keywords, but for keyword tuples, which is exactly what SEO spammers who are scraping stackoverflow are optimizing on.
this implies that you can detect the spammy sites in the first place, take a ridiculously spammy keyword like "buy viagra", how would you detect useful sites in this mess:
http://www.google.com/search?sourceid=chrome&ie=UTF-8...
this implies that you can detect the spammy sites in the first place
In essence, you've just admitted the feasibility of rating the "spammyness" of keyword tuples, provided you can do the classifier.
Second, of course this is possible! SEO-spammers must have some way of determining what to spam. They must have some metric for determining how they can make money and for targeting their efforts for the most profitable scraped content, determining what keyword-tuples to optimize for. An anti-SEO spam engine just has to take the same steps. Just as email spammers put on their email-filterer hats to evade filters, anti-SEO spam engines just have to think like SEO spammers to figure out what SEO spammers are likely to target.
Let's suppose it's possible to tell that a keyword is spammy, what benefit does that provide? The person typing the keyword doesn't care if it's spammy, they just want useful results, quickly.
You can't just reverse the spammer's process, because it's a process followed by many legitimate, successful websites: Research keywords that drive traffic > produce content > build links > get traffic.
Here's the problem - how do you 1. define SEO spam, 2. detect SEO spam. It's not as simple as saying "deindex anything that has optimized title tags or lots of links or shows adsense" because plenty of useful websites optimise for search engines, show ads and have lots of links. What you'd end up with is the dregs of the web, because although you'd reduce the number of spam sites in the results, you'd likely also reduce the number of useful sites in the results because you're specifically targeting and removing the sites that optimise for search engines, which is 99% of the most successful sites on the web today.
SEO is not an inherently bad thing, it's valueless, spammy content that's bad. The real challenge is in determining whether a page is useful, original and relevant to the search query, and that's where Google et al are falling down at the moment.
It's not as simple as saying "deindex anything that has optimized title tags or lots of links or shows adsense"
No, it's not. But undoubtedly, SEO spammers are leaving behind the same kind of clues that email spammers do. Using techniques like Bayesian classifiers should be able to classify such pages. Just detecting all the pages that are slightly edited/SEO-optimized stackoverflow answers would be a good start for me.
you'd likely also reduce the number of useful sites in the results because you're specifically targeting and removing the sites that optimise for search engines, which is 99% of the most successful sites on the web today.
I'd be putting useful sites in the "useful" corpus.
SEO is not an inherently bad thing, it's valueless, spammy content that's bad.
Agreed, just as email marketing is not an inherently bad thing, just spammy emails.
There are billions and billions of pages in the index, let's say they produce a page classifier that can correctly identify spam an unrealistic 99% of the time. They'd still misidentify tens of millions of pages. Regarding your second point, how do you determine usefulness in a way that can't be gamed? My point is, this is a very, very, very hard problem to solve at their scale, a lot of posters on here are trivialising it.
99% classifier? So I get to have a search that's like Google/Bing for all the non-spammy searches, and it only gets 1/100th the spam for the spammy searches? I think I could sell a proposition like that!
Right, but you'll also disincentivize legitimate websites that happen to make their money through such ads or affiliate links. Where do you draw the line?
The solution is simple here: have an alternative search engine that makes their money a different way. Even though it would just be a niche, I bet there's a pretty healthy income to be had for a highly SEO-spam resistant paid search engine. (Supplemented with Google-style search ads.)
A small minority would use such a search engine, so the impact on legitimate sites would be minimal.
If your new search engine gets enough traffic to be worth it, spammers will just target your search engine too, and you'll have exactly the same problem Google has now, but presumably with far fewer engineering resources to throw at the problem.
If your new search engine gets enough traffic to be worth it, spammers will just target your search engine too
I think you're dead wrong here. I only need to catch a sliver of Google/Bing traffic for such a search engine to be worth it. Let's say I get a 1% share of traffic -- which I would characterize as wildly successful -- why would it be worth the while of SEO spammers? How many resources can you throw at something worth 1% of your income?
Because spam is cheap and easy, far easier to produce than to fight, you can spam in your sleep with automated tools. Let's take your 1% example, that's millions of searches a day, well worth a spammer's time and effort. Some people will spam your search engine just because you say they can't, and that kills your unique selling point straight away.
Because spam is cheap and easy, far easier to produce than to fight, you can spam in your sleep with automated tools.
What you are saying is that that someone could algorithmically determine the profitable targets of spam. This opens the door to an economic hack of spamming. Simply run the same algorithms yourself, then if the spam-profit potential of a particular search is above a certain threshold, simply present a "hammy" search based on well-known authoritative sites.
This scheme would work, precisely because spam is cheap and easy.
Some people will spam your search engine just because you say they can't, and that kills your unique selling point straight away.
This only works against the scheme I just described if you can spam my method for determining "well-known authoritative sites." If you curate that, then you can't. What I'm advocating is actually switching between curated and algorithmic search depending on spam-economics. This means that spamming such a site might end up being equivalent to "internally spamming Wikipedia and StackOverflow." I don't think that's going to be viable to SEO spammers for going after an extra 1% income.
Ah yes, "curated search". That's been tried, and it's literally impossible to keep up to date, web pages change all the time, what was an authoritative site yesterday is a phishing site or online pharmacy today. And you're wrong about the economics of spamming wikipedia or stackoverflow, spammers already target sites like that, there are even spammers who target HN, and your model would just make it even more worth it for them.
Ah yes, "curated search". That's been tried, and it's literally impossible to keep up to date
Weak. I'm not advocating "curated search" for everything. Your point is like trumpeting dynamic RAM over NAND gates and not mentioning caching.
And you're wrong about the economics of spamming wikipedia or stackoverflow, spammers already target sites like that, there are even spammers who target HN, and your model would just make it even more worth it for them.
Wow. that's kinda fuzzy thinking there. For it to be worth it for spammers to specifically target an anti-SEO engine, it would have to be successful in the first place, which undercuts the point you were trying to make.
Also, even though spammers target wikipedia, HN, and stackoverflow, why don't I perceive spam as a problem?
ok, I don't believe we're getting anywhere. My challenge to you is, if it's so easy, build it. Prove me wrong and make your millions while you're at it :)
If Google serves AdSense, it already knows how long you as a reader spends on site before clicking through an ad. Presumably, if statistically speaking, visitors have high probability of hitting the back button or clicking through immediately, then it is a red flag that the content wasn't useful.
That's not really the case, plenty of spammers optimize for long tail searches because 1. they're easy to rank for. 2. they're easy to create ambiguous, autogenerated content for
You're thinking short term, Groupon just needs to get to the stage where people think "I'll just check Groupon to see if I can get this cheaper" before every purchase. Then there's a million things they could do to take advantage of that visitor's purchasing intent, local price comparison for example
None of these things are exclusive to Groupon, though. There are already lots of aggregators for coupons where you can check if you can get something cheaper.
The point is that these aggregators are not in everyone's mind today. Groupon can use their current offering to reach everyone's mind, and then use that positioning (and therefore you going to their site) to do price comparison, focus on the user choosing specific topics of interest, etc.
Yeah but my point is, the only point of Groupon is their web site. So I don't see the point of them throwing sales people at small businesses. They need mindshare with their website, and I don't think you can drive internet traffic with sales people.
Also, unless you have a very good reason for doing otherwise, please include a JSON version of your API. JSON libraries are just about ubiquitous and it causes far, far less pain than SOAP.
> Except for consuming the API directly in a browser, there's little reason that XML should cause you pain.
I disagree. Unless the data I'm working with are awkward/difficult to represent in JSON (ie, they're highly structured documents, for which XML is ideal), XML is always more painful to work with. More painful to produce and to consume.
This is working primarily with Python and Javascript.
I can echo this for working on iOS with Cocoa touch as well. While there's no native JSON provided by Cocoa touch, there are excellent third-party tools.
XML in iOS is a beast, and a real pain to read (and I've never attempted to write it).
Plus, on mobile devices especially, XML is slower to download because it is more verbose than the equivalent JSON object.
So I agree, unless you need a highly structured document, I always go with JSON over XML.
The only applications I've made that interface with JSON or XML APIs were in Java, and JSON was less headache every time. GSON makes it trivial to marshall/unmarshall, and I haven't found an equivalent XML library - not for lack of trying!
not really, JSON makes it easy to exchange standard objects and arrays between languages, in PHP it's as simple as:
$json = json_encode($object);
$object = json_decode($json);
I'm sure it's equally easy in other languages, XML is not good in this use case. There's no standard way to do it.
Icey, I'm presuming you knew that the point of the plan was to educate and remind us all that we're not immune from this kind of thing. So it's quite clear jacquesm had no malice here, if he did do you think he'd discuss it so openly? Since you've come out and spoiled this quite valuable opportunity, do you believe your post is in any way more effective at communicating the message than submitting the fake phishing site would have been?
That's how it's being spun now, and perhaps in the email that went out today that I have not been privy to (probably because I voiced my disagreement with the idea at the time).
That's not how it was being discussed at the time.
From the email he sent out, it was pretty clear that he hoped to do this in good faith. Nevertheless, blunting this stunt with a post was the right thing to do. Everyone should just drop it now.
This is missing parts of the conversation; but seriously Jacques, I've got no appetite for making this about you.
We both agree that it's easy to phish people. I disagreed then and still disagree now that the right way to do that is to embarrass them.
If I wanted to "shame" you somehow, I could have easily done that by naming names to begin with. The only intention of this submission was to warn people that you must be careful with your information because you never know who might be out to get it.
I don't believe you were out to snag people's financial data, but beyond that it was pretty tough to tell what you were after other than "teaching other people a lesson" (yes, this is paraphrased).
I fail to see what positive outcome could occur from essentially pointing and laughing at people because they fell for your scheme.
[Edit: I did a bad and edited this comment. Originally it only said "This is missing parts of the conversation", which is what jacquesm is replying to.]
It absolutely is not, that's a 1:1 log of my stuff and no parts were removed other than the lines not spoken by me or referring to me.
I don't think posting a full log of the channel is appropriate, if the other people that were there wish to publish their parts with their ids in there that's fine with me.
I did not post the article above, and I did not use the words 'that's how it is being spun now', those were yours and they are what prompted this, you chose the forum.
The email you refer to which explained the whole thing in some detail was sent to the one person whose reputation might have been harmed but if I had not I would not have been able to tell if he had fallen for it or not (highly unlikely anyway) because identifying information is hashed to make sure that even I can't accidentally leak who fell for it.