The podcast is on the road again this week, with Jeff and Joel coming to you live from Jeff's living room in El Cerrito, CA. They're also joined by Josh Heyer (aka Shog9
) who calls in from Colorado. This is actually the second time we've done a podcast from Jeff's house, the first time being Episode #51
Server Fault and Super User have recently seen a substantial hit in the amount of traffic coming from Google the last few weeks. There's a number of possible reasons, but Joel wonders if it has to do with long clicks vs short clicks.
Joel's theory is that Google is looking at this ratio as a signal for the quality of a site: high quality sites should have more long clicks (meaning you don't return to Google quickly) and fewer short clicks (where you click a link and then immediately return to the search page).
We're also wondering if the Google algorithm change is penalizing sysadmin content - since a number of other sites focused on System Administrators / IT Professionals have also seen big drops in traffic from Google.
Jeff previously blogged about Google algorithm issues and the fundamental risks of any site relying on a single source for so much of their traffic.
- If you have any data or observations from running your sites, make sure to hop over to our webmasters.stackexchange question on this topic.
Our guest today is Josh Heyer, our new part-time community manager. Josh was originally on Usenet, then moved to forums and Code Project, and joined Stack Overflow right after it launched; he's been with us from the beginning.
One of the first things that Josh pushed to change after joining the team was to make it more clear why accounts were being suspended. Someone would get suspended and then complain about it publicly; they had a reason, but other people didn't. This sometimes led to lots of heat and noise on meta, detracting from the quality of the site. By making the reason for a suspensions public, you remove the gossiping and public discussion. And if you don't -- you get the Streisand effect.
We're now tackling the last of the low hanging fruit in making the site performance better: serving static content using a CDN. By utilizing a CDN for lower priority/static content (like logos and other images) we can serve files faster to different areas of the world.
Make sure to hop over to that blog post and help us (and you!) out by telling us which CDN works best for you.
We've been using our own home-brew CDN-like setup that offloads all of our static content off the main servers (to reduce CPU loads) and onto a side domain. Unfortunately, these secondary servers were still located in our NY data center, so it did not do anything to reduce ping times to distant locations.
- In our experience, breaking your static content off onto its own server can have a huge performance benefit, even for small or medium sites.
It's amazing how many highly technical people don't think to clear their browser cache when they're having a problem with a website loading. Always clear your browser cache and try again before contacting a site's support team. Please?
We started a logo contest for Lucene.net, the open source project powering our search. If you want to help out by trying your hand at designing a logo for this project, check out the 99designs contest we created on their behalf.
Because our search currently focuses on relevance (determined by keyword mentions), we recommend editing good questions to make sure a proper set of keywords appear in them; this makes it easier for others to find these questions in search.
- Remember that search results have several tabs, but always defaults to relevance. Try the votes, active, and other tabs to get a different sort of your search results.
Currently, there's no way for anonymous users to indicate their satisfaction with a page -- should we add something to allow drive-by visitors to contribute? There's always anonymous editing, of course, and this is the reason we keep view counters on pages - it's the only way for people who don't ask or answer, and don't have the 15 rep "citizenship" required to vote, to make an impact on the questions they visit.
How should we handle "missing semi-colon" questions -- where someone posts a chunk of code that isn't working and the only problem is that they had the name of a variable wrong, or forgot a semicolon somewhere? Since these questions will never be of benefit to anyone down the line, there's no real reason to keep them on the site.
- This is also why we modified the language for the Too Localized close reason to read "this question will not be helpful to future visitors". It's a much clearer explanation of what that close reason is intended for, and we've already seen an uptick in usage.
There's no podcast next week, but we'll be back the week after, so make sure to join us then!