OpinionOutpost Apology

Last June, I got a comment on my site that as far as I could tell was comment spam advertising a site called Opinion Outpost. Not being a fan of that style of advertising, I posted about it. In the following months I’ve gotten a few comments from satisfied Opinion Outpost customers defending the company — but yesterday, I actually got an apology from the person who originally left the comment that started it all.

I was looking your webpage this morning and wanted to apologize for posting our email on your weblog.  When I first posted on your site I was looking for your email address to contact you about our affiliate program and I could not find it so I thought I would make a post not knowing what I was doing was inappropriate in the weblogging community.  I was new with the company when I posted this and learned very early that this kind of practice was wrong and I haven’t done it since.  I know that what I have done has made you very upset with me and Opinion Outpost.  I ask that you hold nothing against Opinion Outpost, I am the one at fault.

As for this email that you said you sent me, I don’t ever remember receiving it.  I receive large amounts of emails every day and I probably looked at it with confusion (not understanding it or not knowing what I did wrong) and discarded it.  I am very sorry for my actions and hope this post will ease the tension and conflict between you, your weblog and me.

I am willing to post this on your weblog if you would like me to.  Just let me know what you would prefer.  Thank you!

Sounds reasonable to me — it’s a pity my original e-mail got lost, but everyone makes mistakes from time to time, and he was kind enough to send the apology along. The apology is certainly accepted, and I’ve gone back and edited out all the names and contact information from the original post and the follow-up comments.

Opinion Outpost still doesn’t look like the kind of thing I’m interested in for my own needs, but with this, I’ll file them back into the “on the level” bin. :)

Frappr

Check out our Frappr!There’s a new Google Maps hack/toy out bouncing across the ‘net now: Frappr, which allows people to put their location in (zip code only, so no stalking possible) and have it displayed as part of a group.

I’ve created a group for Eclecticism readers…feel free to drop by and add yourself to the map. I’d love to get an idea of just how widespread my readers are!

LJ-style links for Ecto

This is actually fairly simple, but you never know.

For ecto users who want to post LiveJournal-style links to LJ user accounts (such as [djwudi's info]djwudi) into a weblog entry on a non-LJ system:

  1. Open Window > HTML Tags.
  2. Click the + button to create a new tag set.
  3. Paste the following code into the ‘opening tag’ box (as a single line):
    <a href="http://www.livejournal.com/userinfo.bml?user=%*">
    <img src="http://stat.livejournal.com/img/userinfo.gif" alt="[%*'s info]" width="17" height="17" /></a>
    <a href="http://www.livejournal.com/users/%*/"><b>
    
  4. Paste the following code into the ‘closing tag’ box:
    </b></a>
    
  5. Assign a command key sequence (optional, of course — I used option-command-J).

Viola! You’re done. Now, just type someone’s LJ username into a weblog post, select it, and choose the new tag set (or type the command key sequence you set), and the LJ-style link is created.

Help: CSS2 selectors

I’m working on setting up a print stylesheet for the site. I’ve got it about, oh, 98% done — done enough that I could leave it as-is, except that there’s one little thing that’s bothering me that so far, I’m not able to fix. Any and all help would be greatly appreciated.

Because hyperlinks are essentially useless on the printed page, in the print stylesheet, I’m using CSS2 selectors as outlined in this A List Apart article to insert URLs after links in the text. This way, instead of links simply printing as colored and underlined text, the destination address of the link is printed out after the link text.

Here’s the code I’m using to accomplish this:

a:link, a:visited {
    text-decoration: none;
    }

.entry-body a[href]:before,
.entry-more a[href]:before,
.trackback-content a[href]:before,
.comment-content a[href]:before {
    content: " [";
    color: #000;
    text-decoration: none;
    }

.entry-body a[href]:after,
.entry-more a[href]:after,
.trackback-content a[href]:after,
.comment-content a[href]:after {
    content: " " attr(href) "] ";
    color: #000;
    text-decoration: none;
    }

So far, so good, it’s doing exactly what it should. Here’s a sample of what it looks like when printed from a browser that understands CSS2 declarations (that is, pretty much everything except IE):

However, I often insert images into my posts that are linked, either to larger versions as in the above screenshot, or to the Flickr pages for the original images. In that instance, I’d prefer that the target URLs not be inserted, as they are less relevant, and tend to muck up the final printed page in odd ways.

Example number one: the panoramic image that appears at the beginning of the Cal Anderson Park post from earlier today:

Example number two: the Flickr imagebar from the bottom of the same post. The web version shows five thumbnails side-by-side, but once the URLs are appended for the print version…

…only two of the thumbnails can even appear on the page.

Okay, sure, so these things aren’t exactly major disasters, but I’m just anal enough that I’d like to fix them. What I’d like to do, then, is figure out just what CSS code I’d need to use to exclude images from the code shown above.

Of course, I haven’t got a clue how to do this (obviously, or this post wouldn’t even exist). I’ve been poking at it all morning, and I’m stuck. Any ideas?

Anyone?

Bueller?


NOTE: Possible Safari Bug? In the original A List Apart article, the example code used a combination of a:link:after and a:visited:after to ensure that the links were inserted after all the links — if the code was only attached to a:link:after, then any links that the user had visited would not get the link appended when the page was printed.

While I was working on this, I started with that code. However, I was noticing an odd bug that was only appearing in Safari (at least, it wasn’t appearing in Firefox or Opera, the other browsers I have available to test with) — Safari would pick one URL of the URLs on that page and insert it after every link. In other words, if one link on the page pointed to www.example.com, then no matter how many other links were on the page, they would all display as www.example.com.

I wrote that off as something to worry about later, and kept fiddling around trying to get my images to do what I wanted. In the process, I skimmed over a more recent ALA article on print stylesheets and noticed that Eric Meyer had presented slightly different code: instead of combining a:link:after and a:visited:after, he simply wrote a[href]:after, and that took care of both instances. I swapped out my old code for the new, more concise version, and not only did it work as it should…but the repeating URL bug disappeared. Now, when printing from Safari, all the correct links print out just as they should.

Weird…but good to know.

Yet More Tweaks

A few more tweaks and oddments:

  • Re-worded the post metadata.
  • Added Technorati tags to the metadata.
  • Added pseudo-hidden ‘admin only’ links to all posts, comments, and TrackBack pings, allowing for single-click jumps to the edit screen for each item.
  • Used SimpleComments to combine comments and TrackBack pings into a single chronological list.
  • Added small icons (yanked right from the MT interface, actually) to comment and TrackBack listings to more easily visually identify which is which.
  • Added a :hover effect border to comment and TrackBack listings.
  • Comments I leave will display with a colored background to easily distinguish them from visitors’ comments.
  • Lots of templates updated so that all a links have an associated title attribute.

And…that’s all I’m remembering right now.

LiveJournal/OpenID Authenticated Commenting

So much for declaring a “no more tweaks” point. I just can’t resist the urge to fiddle around…

Thanks to Mark Paschal‘s OpenId Comments plugin (announced and described here, current release here), visitors can now authenticate themselves when leaving comments using a LiveJournal or OpenID account in addition to TypeKey authentication (or no authentication at all).

I’ve also increased the width of the comment entry field, as it was a bit cramped (thanks to mom for prompting me on this, as it was bugging me too).

Leave a comment, play around, and let me know if anything seems goofy!

(Update: Some goofiness exists. Generic, TypeKey, and LiveJournal options are working fine, OpenID comments are coming through as ‘anonymous’ even though the commenting UI reports that they’re successfully signed in. Something to fiddle with….)

Transitioned

There are a few benefits to being unemployed for a little bit. One of those is having more available hours in the day to spend tinkering around with some of my neverending PROJECTs.

I’ve just (mostly) finished converting all of my pages over to the new template styles provided by Movable Type 3.2. There’s a few tweaks that I didn’t bring over (multiple stylesheets, the live comment preview, gravatar support, and incorporating TrackBack pings and comments into a single list), and I’m still running over in my head which, if any, will be re-incorporated down the line.

For now, though, I’m declaring things done. Feel free to poke around, and as always, suggestions are always appreciated.

Here’s a brief overview of the changes I’ve made to MT’s default templates…

Read more

In Transition

Along with upgrading the backend of the site to Movable Type 3.2, which I did last week sometime, I’ve decided to upgrade my templates to the new MT3.2 styles. As I’ve had a fair number of customizations that I’ve been using, though, it’s taking a bit of time to incorporate them into the default templates provided by Six Apart.

Expect some oddities for a few days as I get things tweaked and configured. Once I’ve got everything working with a basic startpoint, then I’ll see about customizing the style to something a little more “me”.

For now, though…things might be a bit odd. Bear with me, hopefully this won’t last too long.