brainwidth

Try the Customizable Post Listings plugin.

Warning: NSFW.

I just think it’s embarrassing that despite being skilled enough to create “fully proprietary code, with full support,” you can’t come up with your own name. That’s bad business.

I notice that your style sheet is on a different subdomain than your blog address: https://joshazzarella.com/blog/wp-content/themes/wuhan/style.css. IE is fickle about loading stylesheets from different domains or subdomains.

Keep in mind that relative paths break when viewed in many feedreaders.

The main css file calls two other css files: layout.css, which has what it says, and spring_flavour.css, which has colors and fonts. Make a copy of the spring_flavour.css file and call it whatever you want. Change the main css file to point at your new css files, then you can play around with the colors however you like. Check my blog for an example.

I’m not sure I understand the objection to a search engine indexing your content. It’s kind of interesting as a copyright thought problem, but what exactly is the objection?

I’m not sure that’s exactly true. The test for commercial use does not demand that ads be placed directly on the reproduction of the protected work. Simply republishing the work in a commercial context, as Google clearly is, may be enough to violate the non-commercial restrictions of certain CC licenses.

The Creative Commons licenses grant viewers and consumers additional expanded rights to use the protected works under certain specified circumstances. The licenses do not restrict rights under the existing copyright law. If a consumer has a fair use right to use excerpts of the protected work under existing law, the license does nothing–and in fact, can’t do anything–to remove those preexisting rights.

The author’s copyright on the blog will only cover the work itself, not links to the work. Even if the search engine adds short excerpts to the search results, like Google does, it’s likely that those are protected by fair use. In a similar case, the Ninth circuit ruled that it was indeed fair use for a search engine to display thumbnails of copyrighted images in its search results. Therefore, it’s probably unnecessary for the search engine to obtain a license to use the excerpts.

The stickier problem, in my mind, is the Google cache. Google effectively redistributes a copy of your page when someone accesses the cached version.

Confirmed as a feed parsing error on the development server side. I guess it will be fixed shortly.

Thanks, Ryan.

Thanks for pointing out that thread, holographic; I missed it when I went searching for the problem. @podz: I’m on dreamhost, and there hasn’t been any announcement of any changes. Given the number of people having an identical problem in that other thread, I suspect its not a dreamhost problem.

This isn’t a a direct answer to your question, but your aside entries are siting in the “col” div, rather than having a div of their own like regular entries. You might try putting each aside in a div, and I bet that would fix the problem.

Take a look at reBlog.