Work-for-Hire, Royalties, and Freelancing

2015-09-25, 9:15 am
Categories: Comics, Politics, Stream of Consciousness

In my previous post, I linked to a piece on Ken Penders written by TheAmazingSallyHogan, and I said that I had a few minor quibbles with it that I'd come back to. So here they are.

Ms. Hogan says this about work-for-hire law:

Under Work for Hire contracts, a creator is paid a flat fee for producing content. All artwork, stories, characters, plots, symbols, etc. become the property of the employer (or a third party, which would be SEGA in this example). Under Work For Hire, a creator does not receive further compensation/royalties if their work is reprinted, if their characters are reused due to popularity, or even if their work results in merchandise/mass media. This is not a salaried position – at any point a publisher can decide to simply stop asking a creator to submit work.

While that's true of Archie's work-for-hire agreements, it's not true of work-for-hire in general as Hogan suggests. It is entirely possible to have a work-for-hire agreement that does allow for royalties, or other profit-sharing arrangements; for example, the audiobooks I've recorded were all produced under work-for-hire agreements that only pay royalties, with no money upfront. Likewise, while the creators who produce work for Archie Comics are freelancers and not employees, it is possible (and indeed standard practice) for an employment agreement to include a work-for-hire clause.

And while Hogan correctly notes, here, that Ken was not an employee on salary, she incorrectly uses the word "employment" several times throughout the article to describe his work for Archie. But a job is not the same thing as employment. Ken was not an employee; he was a freelancer and Archie was his customer.

Hogan goes on to say:

These “no royalties” contracts are no longer the norm in the industry for creators working extensively on titles.

This is true (though the qualifier "extensively" is unnecessary); DC and Marvel both have royalty clauses in their work-for-hire contracts (Comic Book Resources has discussed both DC's current royalty policy and Marvel's). Archie is not the only comics publisher that does not pay royalties, but it is lagging behind the Big Two in terms of compensating its creators.

The point of all this is that all work-for-hire means is: Alice hires Bob to create something, under a contract which stipulates that for legal purposes, Alice is the creator.

That's it. That's what work-for-hire means.

How Alice pays Bob, whether Bob is Alice's employee or Alice is Bob's customer, and any other details of the arrangement between Alice and Bob are separate issues, and not determined by whether or not the work is for-hire. All work-for-hire determines is who is the legal creator of the work.

Some work-for-hire agreements pay a flat fee, some work-for-hire agreements pay royalties, some work-for-hire agreements are between a freelancer and a client, some are between an employee and an employer.

But in Archie's case, Hogan is correct: money upfront, no royalties; freelancers, not employees.

Go, Ken, Go! -- Part 6: Penders v Sega Dismissed

2015-09-24, 8:36 am
Categories: Comics, Games, Politics, Stream of Consciousness

I'm going to talk about Ken Penders for a bit, because apparently somewhere along the line my blog became the Internet's foremost resource for information on Archie v Penders. And I never did get around to writing about the conclusion to the other suit, Penders v Sega et al, so I should probably start there.

To read my previous Ken Penders coverage, peruse the handy Ken Penders tag.

The gist: Archie forgets to make Ken Penders sign work-for-hire agreements prior to his work on the Sonic the Hedgehog comic, Penders asserts that he still owns or co-owns the copyrights to all that work and will be working on his own sequel, Archie sues him and writes all his characters out of the comic, fanboys flip out, Archie and Penders settle for undisclosed terms. And that's where I left off back in 2013.

Well, there were two lawsuits: Archie v Penders, where Archie sued Penders to assert that his work was for-hire and he held no ownership stake in it, and Penders v Sega et al, where Penders sued Sega and EA over Sonic Chronicles: The Dark Brotherhood, a game which featured characters similar to the Dark Legion he had created in the Knuckles the Echidna comic.

Last I talked about this, Penders v Sega was still awaiting resolution, but I learned recently that last year it was dismissed on a technicality.

I took a look at Ken Penders's messageboard a little while ago (I'll come back to that in a future post), and he linked to a Tumblr post by TheAmazingSallyHogan, citing it as an authoritative and scholarly rundown of the case.

I have a couple of minor, tangential quibbles with Ms. Hogan's piece, such as how she defines work-for-hire; I'll get to them in a later post. But they're not relevant to the specifics of the Penders case, which, near as I can tell, she has exactly right, and describes in great detail.

And as for the conclusion of the Sega case, here's what she has to say:

On September 26, 2011, Penders’ lawsuit against SEGA/Electronic arts was dismissed, with the Judge essentially telling Penders that he needed settle matters with Archie first, and then he could re-file. Penders re-filed on September 30, just four days later. The same Judge dismissed the case a second time, saying very firmly that Penders needed to settle matters with Archie before re-filing against SEGA/Electronic Arts.

[...]

In May 2012, Penders’ council appealed the dismissal of his case against SEGA and EA. Penders’ determination to have a case in progress against SEGA/Electronic Arts, instead of just waiting to re-file, was because there is a three year statute of limitations on US copyright claims – a legal time limit intended to make sure cases are tried while the evidence is fresh. Sonic Chronicles was released September 25, 2008, almost exactly three years earlier. Filing a new case later would mean he would lose the chance to sue SEGA for Sonic Chronicles’ sales, so Penders appealed the dismissal. The importance of these dates was not stated in his appeal, an omission that would later prove crucial.

[...]

On October 11, 2013, Penders’ appeal (concerning his case against SEGA/Electronic Arts) was heard. While the judges agreed that the timeline was highly relevant and that if the case was dismissed he would largely lose the ability to seek compensation for Sonic Chronicles, his previous lawyer had failed to state why the dates were important in the appeal, and thus the judges could not take that issue into consideration. Shortly after, the court rejected his appeal and upheld the dismissal. While he could re-file, Sonic Chronicles had been released September 2008. It was now well past three years later, putting essentially all sales outside of the three year statute of limitations window. However, any new usage of the characters introduced in that game (such as an appearance in the comic), could potentially lead to a lawsuit from Penders. Late October, Penders stated “this case may yet end up in the US Supreme Court if a resolution isn’t found prior to that”.

So there it is: due to a mistake in Penders's lawyer's legal filing, Penders v Sega was dismissed, and he missed the statute of limitations for collecting any of the money generated by Sonic Chronicles. No ruling, no settlement, no resolution. While I wouldn't be surprised to see some fanboys take the words "case dismissed" to mean that Penders's case against Sega was flimsy or lacking in some way, that is not what this dismissal means; the case was dismissed due to a mistake in filling out the paperwork, and no other reason.

I wouldn't expect to see Sega re-release Sonic Chronicles any time soon, as that would open them up to a new suit.

Penders's allusions to a Supreme Court case notwithstanding, this is most likely the end of it, though he's still got his own series coming at some point, whatever form it may take.

I noted before that a lot of the other writers and artists who worked on Sonic around the time Penders did could potentially file for their own copyrights (and that Scott Shaw already had). I haven't heard anything more about that. However, given how the Penders case went, I would expect Archie to quietly settle with any other creators who made similar claims, on similar terms, without suing them, and it's entirely possible this has already happened. It's one of those things we'll most likely never know.

Meanwhile, if you're interested in the case at all, I highly recommend that you read the entire piece by TheAmazingSallyHogan. It's as good and thorough a summary of the case as you'll find anywhere.

Web Design Got Complicated

2015-09-23, 1:46 pm
Categories: Stream of Consciousness, Tech

It's probably not surprising that rebuilding my website has gotten me thinking about web development.

The first six years I ran this site, I did it all by hand -- my own HTML, my own CSS, no scripting languages. I thought that CMS software was for pussies.

But ultimately, plain old HTML just doesn't scale. I conceded that when I started using b2evolution for my blog back in '06, and it's truer now than it was then.

You can poke around some of the old sections of the site a bit, the ones that haven't been updated significantly since the turn of the century -- KateStory's a good one, or the Features page (though I'd like to get at least the Features page up to date sooner than later, and maybe the KateStory one too, so maybe there'll be people reading this post well after those pages shed their 1990's style) -- and they get the job done. Breadcrumb navigation at the bottom of every section, leading you back to either the parent page or the main index.

But Jesus, you can only manually copy and paste "Back to Features / Back to Index" so many times.

And maintaining a years-long blog archive without a CMS to automate it for you? It gets old.

So, you want some automation? You're going to need a scripting language. That usually means PHP for server-side, and JavaScript for client-side.

I got to thinking the other day -- man, it's weird that you need extra toolsets to perform such common tasks as, say, reusing a navigation bar. It's weird that there's not some way just to write up a navigation bar and then write code, in HTML, no scripting required, to embed that common HTML block on the current page.

I thought this was a pretty smart observation.

For about three seconds.

At which point I realized I had just described fucking frames.

Course, the biggest problem with frames is that they weren't exactly what I'm describing. I'm talking about just an HTML snippet in some secondary file that you call from a primary file -- like an include in PHP.

That's not what frames were. Frames were complete fucking HTML pages -- <html>, <head>, <body> (or, more likely, <HTML>, <HEAD>, <BODY>, because in the old days we wrote HTML tags in all-caps) -- which is, most times, downright stupid and wasteful, and was much moreso in the days of 14.4 dialup. Even worse than the load time was the logistics -- if you used frames to build a website with a header, a footer, and a sidebar, you'd have a total of five separate web pages -- a content area, the three other sections, and some kind of main page that all of them were embedded into. This was a fucking nightmare for linking, both for the developer (who had to remember to set the target attribute on every single link, lest the page load in the navigation bar instead of the content area) and the end user (because the URL in the location bar would be the container page that called all the other pages, not the content page the user was currently looking at).

In a way, it's kinda weird that nobody's gone back to that well and tried to do it again, but do it right this time. Update the HTML spec to allow an HTML file to call a reusable snippet of HTML from another file, one that isn't a complete page.

Given all the concessions HTML5 has made to the modern Web, it's surprising that hasn't happened, even given how slowly it takes for a spec to be approved. We've got a <nav> tag, which is nice and all, but who the hell uses a <nav> tag without calling some kind of scripting language that automates code reuse? There really aren't that damn many reasons to use the <nav> tag for code that isn't going to be reused on multiple pages throughout a site.

And I dunno, I'm sure somebody's brought this up, maybe it's on the itinerary as a consideration for HTML6.

Which is another thing, really: the people making the decisions on the specs do not want the same things I want.

I liked XHTML. (In fact, lest this whole thing come off as a curmudgeonly damn-kids-get-off-my-lawn diatribe against new technologies and standards, I'd like to note that I was using XHTML Strict back when you pretty much had to be using a beta version of Phoenix -- before it was Firebird, before it was Firefox -- for it to render correctly.) I thought it was the future. I wish XHTML2 had taken off. HTML5 feels ugly and inconsistent by comparison, and, as legitimately goddamn useful as it is to be able to put something like data-reveal aria-hidden="true" in the middle of a tag's attributes, it always feels dirty somehow.

But I digress.

Point is, in 2006, I switched the blog from just plain old HTML and CSS, and added two more elements: a MySQL database to actually store all the shit, and a PHP CMS (originally b2evolution, later switched to WordPress).

And then came smartphones.

We live in a world now where every website has to be designed for multiple layouts at multiple resolutions. You wanna try doing that without using an existing library as a base? Try it for a few days. I guarantee you will no longer want that.

I think my resistance to picking up new libraries is that every time you do it, you cede a measure of control for the sake of convenience. I don't like ceding control. I like my website to do what the fuck I tell it to, not what some piece of software thinks I want it to.

I've spent the last decade arguing with blogging software to get it to quit doing stupid shit like turn my straight quotes into "smart" quotes and my double-hyphens into dashes. Just the other day, I built a page in WordPress and discovered that it replaced all my HTML comments with fucking empty paragraphs. Why would I want that? Why would anyone want that?! And that's after I put all the remove_filter code in my functions.php.

And that's the thing: WordPress isn't built for guys like me. Guys like me use it, extensively (it is the world's most popular CMS), because it automates a bunch of shit that we'd rather not have to deal with ourselves and because when we're done we can hand it off to end users so they can update their own site.

But I still write these posts in HTML. I want to define my own paragraph breaks, my own code tags, the difference between an <em> and a <cite> even though they look the same to an end user.

(And okay, I still use <em> and <strong> over <i> and <b>; there's really no explaining that except as a ridiculous affectation. I recently learned Markdown and used it to write a short story -- I'll come back to that at a later date -- and I could see switching to that. HTML really is too damn verbose.)

...and that was another lengthy digression.

So. Mobile design.

Bootstrap is the most commonly used toolkit for responsive websites. I've used it, it works well, but it's not my favorite idiom, and I've decided I prefer Zurb Foundation. So that's what I used to build the new site layout.

Except, of course, then you've got to get two dueling design kits to play nice to each other. Square the circle between WordPress and Foundation.

I started to build the new theme from scratch, and I'm glad I was only a few hours into that project when I discovered JointsWP, because that would have been one hell of a project.

JointsWP is poorly documented but has proven pretty easy to pick up anyway.

So. I've gone from HTML and CSS to HTML, CSS, and WordPress (HTML/CSS/PHP/MySQL), to HTML, CSS, WordPress, Foundation (HTML/SCSS/JavaScript, importing libraries including jQuery), and JointsWP (ditto plus PHP). And on top of that I'm using Git for version tracking, Gulp to process the SCSS, and Bower to download all the other scripts and toolkits I need and keep them updated.

So, going with Foundation (or Bootstrap, or whatever) as a standard toolkit, you get somebody else's codebase to start from. That comes with some elements that are a necessary evil (I hate fucking CSS resets, and think writing p { margin: 0; } is an abomination in the sight of God and Nature -- but if it means I can assume my site will look more or less correct in Mobile Safari without having to go out and buy an iPhone, then I guess I'll take it), and others that are actually pretty great -- I find SCSS to be really exciting, a huge saver of time and tedium, and it's hard to go back to vanilla CSS now that I've used it.

Course, with increasing complexity, you still hit those things that don't quite work right. One example I've found is that Foundation sets your placeholder text (the gray letters that appear in an "empty" input field) too light to be legible, and does not have a simple definition in _settings.scss to let you adjust it to darker. I've found a mixin that allows you to create such a definition pretty simply, but for some reason JointsWP doesn't like it (or maybe Gulp doesn't). So until I get around to finding a fix, the text stays light, and I'll just have to trust that you the user will be able to determine that the input field under the phrase "Search for:" and to the left of the big blue button that says "Search" is a search box.

I've also got loads of optimization still to do; part of that's going to mean figuring out what parts of Foundation's CSS and JS I'm not actually using and cutting them out of the calls, and part of it's probably going to mean minification.

Minification is one of those things I resisted for awhile but have come around on. It can be a real hassle for debugging, not being able to view a stylesheet or script in full, and it may not be practical just to save a few kilobytes (or a few dozen, rarely a few hundred) -- but on the other hand, well, it's not so different from compiling source code to binary; the end result is still that you take something human-readable and turn it into something much less human-readable.

And of course now that I'm using a preprocessor, my CSS file isn't my real source code anyway; it's already the result of taking my code, feeding it through an interpreter, and outputting something that is not my code. If you want to look at the stylesheet for this site, you want to look at the SCSS file anyway (it's on Github), not the CSS file. And if I'm already telling people "Look at the SCSS file, not the CSS file," then what's the harm in minifying the CSS file and making it harder for people to read?

For now -- prior to removing unnecessary code calls and minifying everything -- I feel like the site design's a lot more bloated than it needs to be. And even once I slim it down, there are going to be some compromises that go against my sensibilities -- for example, when you loaded this page, you loaded two separate navigation systems, the desktop version (top navigation and sidebar) and the mobile version (just a sidebar, which contains many of the same elements as the topnav and sidebar from the desktop version but is not exactly the same), even though you can only see one of them. That redundancy makes me wince a little bit, but ultimately I think it's the best and simplest way of doing it. Sometimes, good design does require some redundancy.

All that to say -- man, there have been a lot of changes to web design in the last twenty years. And while there are trends I really don't like (if I never have to build another slideshow it'll be too soon; gradients are usually dumb and pointless; and the trend of making visited links the same color as unvisited ones feels like a step backward into 1995), there are also a lot that I've eventually warmed up to, or at least accepted as something I've gotta deal with.

Anyway. Welcome to the new corporate-sellout.com.

And one more thing about the site before I go: it's probably worth noting that this site is different from the other sites I build, because it's mine. Its primary audience is me. I like having an audience, but frankly I'm always a little (pleasantly) surprised whenever anyone actually tells me they enjoyed something I put on this site.

Because this site isn't one of my professional sites. I didn't build it for a client. It's not my portfolio site, which I built to attract clients. This one? It's for me. As should be clear from this rambling, 2200-word stream-of-consciousness post about the technical ins and outs of web design, as it applies specifically to me and to this site.

Frankly I'm always surprised when anyone actually reads anything like this.

I'll Call It a Good Start

2015-09-20, 4:18 pm
Categories: Announcements, Tech

Well, that's the update done, and you should be looking at the new theme now.

It needs work (the current "Archives" list in the sidebar is 67 lines long and I need to remember how to limit it to just the last few months like in the old version), but it's a start.

I'll be puttering around behind the scenes for a little while yet. Course, the point of all this is that I'd like to start blogging regularly again; there's not much point to going to all this trouble to pretty it up if I don't start using it.

As you might expect, just the update itself gives me plenty of things to talk about -- what I like about modern Web design and what I don't.

More to come, I should think.

Hang On to Your Butts

2015-09-20, 2:35 pm
Categories: Announcements, Tech

Gearing up for a major site update -- first I'm disabling all my plugins, then I'm updating WordPress, then I'm installing a brand new theme, and then I'll be beating the theme into working shape. Things may break at any and all points of this process.

Ubuntu on an Old Mac Pro

2015-06-28, 9:45 am
Categories: Stream of Consciousness, Tech

So I spent the past few days trying to get Ubuntu Studio installed on my 2006-era Mac Pro 1,1. I can't speak for other Macs specifically, but here are some details you're going to want to know if you engage in that undertaking:

  • The Mac Pro 1,1 won't boot Linux from a USB stick.
  • It also won't boot it from a dual-layer DVD. Double-check and make sure you're not using dual-layer.
  • The LTS releases of Ubuntu (such as 14.04) have images that are specifically labeled "amd64+mac". Use those. Otherwise you might wind up stuck on an unresponsive "Select CD-ROM Boot Type" prompt.
  • You may or may not need to install rEFInd to help you boot from a Linux disc. If your disc isn't showing up when you hold the Option key at boot, give rEFInd a shot.
  • There's a useful guide at Ubuntu Community Help called Installing on a Mac Pro - Cylinder (Late 2013). As the title implies, it's not written for the older-model Mac Pros, but most of what it says is still applicable. (But it tells you not to use the Mac-specific ISO files. Don't listen to that part; you should use those on the 1,1 model.)

On Advertisements

2015-06-03, 4:41 pm
Categories: Comics, E-Mail, Stream of Consciousness

Dear DC,

Here is a list of DC Comics I would have purchased today if they had not contained obnoxious half-page Twix ads:

  • Batman Beyond #1
  • Bat-Mite #1
  • Bizarro #1

Here is a list of DC comics I purchased today:

DC, I do not have a fancy marketing degree. However, I can offer you a marketing suggestion for free: if one team of marketers suggests making money by releasing new comics that appeal to a different audience from the core DC line (albeit, granted, still pretty much just made up of spinoffs of Batman and Superman comics), and another team of marketers suggests making money through finding a really irritating and distracting way of putting advertisements in your comics, perhaps you might consider rolling out those two ideas separately instead of simultaneously. This is what is known as "isolating the variables".

I would also suggest that, if I were one of the writers, artists, editors, or marketers who had gone to considerable effort to create and market a new and different comic book to a nontraditional audience, I would be pretty unhappy right now with the people in management who had made a decision that actively sabotaged the appeal of that comic book.

I do not wish to be negative or ungrateful here. I greatly appreciate your decision to convince me to keep the nine dollars I would have spent on those three comic books. I went nextdoor and spent that money on beer instead. I had a Four Peaks Kiltlifter and a New Belgium Slow Ride. They were very good beers, and at no point in my drinking experience did they interrupt me and try to convince me to buy Twix.

Kisses,

Thad

Job Spammers are the Worst

2015-02-04, 10:34 am
Categories: E-Mail, Stream of Consciousness, Work

I'm looking for work right now.

So I've got a current resume posted publicly up on CareerBuilder.

And oh God, the spam that brings.

It's kind of amazing how many hiring agencies seem to have taken a look at the scammers who sell penis pills and decided, "Yeah, that looks like a pretty good business strategy."

I'm inundated, every day, with postings for jobs that aren't even in my state. I've gotten ten of them this week alone (and one phone call), and it's only Wednesday morning.

Most of them seem to be coming through one single distributor, or at least one single software kit -- because they follow the same format, and if you click Unsubscribe, all the Unsubscribe pages look exactly the same except for the logo.

Needless to say, they do not actually honor the unsubscribe requests. These are spammers we're talking about.

Of course, the big problem here is that unlike the spambots selling Cialis, I can't just mark these as spam and rely on Bayesian filters to sort the wheat from the chaff -- because aside from the location, these postings are indistinguishable from real job posting E-Mails, of the sort I want and need, because I am trying to find a job. Job spammers have an in that other spammers don't: they're advertising something I actually want, they're just advertising it in a place I don't want it. So I can't filter out an entire class of E-Mails, because the risk of false positives is far too high.

Which leaves me relying on filtering by domain name. Which, as anybody knows, is unreliable Stone Age Whac-a-Mole shit, because spammers use all the domain names they can get their mitts on.

Still, it's better than nothing, and I'll be putting a list of the spam domains I've filtered so far at the end of this post -- maybe it'll be of some help to some other folks out there looking for work. And maybe it'll give these agencies a little bad publicity.

But first, here's a story about the absolute worst, slimiest job spam I've gotten to date.

It's from an organization called Strategic Staffing Solutions, which started out by straight-up brazenly lying to me. Here's a portion of the E-Mail I got, with the rep's last name and E-Mail redacted -- I don't want to rain down Internet mob justice on anybody, even if they are engaging in sleazy tactics; I just want to name and shame the company that encourages this type of behavior.

From: Adam [redacted] <[redacted]@strategicstaff.com>
Subject: data scientist - MO
01/26/2015 02:17 PM

Hello Thad Boyd,

Please contact me as I have many job opportunities to discuss.

We have 24 locations within the USA.

I have called your phone number about your resume. The phone number has been disconnected.

Would you be interested in this job position? Please send me your resume.

Here are two job orders:

What followed were two job listings that have absolutely nothing to do with my education, training, or job experience.

So, straight into the circular file it went.

And then I thought, you know what? No. That line about trying to call me and my phone being disconnected was low. That's just a gross way to start any kind of relationship.

So I replied to the guy, and decided to press him on the "Your phone has been disconnected" lie.

From: Thad Boyd <[redacted]>
Subject: Re: data scientist - MO
01/27/2015 08:45 AM

Hi Adam,

I've had the same phone number for ten years, and haven't had any trouble receiving calls that I'm aware of. What number were you trying to call, and where did you get it?

He, of course, completely ignored my question, and responded with this boilerplate:

From: Adam [redacted] <[redacted]@strategicstaff.com>
Subject: Re: data scientist - MO
01/27/2015 09:55 AM

Hello Thad,

Please send me your resume.
Are you actively seeking work?

Please make use of Central Sourcing@STRATEGIC, as they can accelerate your recruiting.

I decided to press the issue one more time:

From: Thad Boyd <[redacted]>
Subject: Re: data scientist - MO
01/29/2015 09:52 AM

Hi Adam,

Yes, I'm actively seeking work.

Where did you say you got my contact details, and what phone number were you trying to call? I'd like to know if there's something wrong with my phone service. My grandfather is in the hospital right now and I need to know that people can reach me.

(And since he pretended not to notice my question about the phone, I pretended not to notice he'd asked for my resume.)

That last part is true, by the way -- Grandpa's going to be okay but he is currently in the hospital. I brought this up to make a point: lying to somebody about his phone being disconnected has consequences. If I had been gullible enough to believe his lie, I could have wound up wasting a good chunk of my day on the phone with Sprint, trying to figure out what was wrong with my phone service, and worrying all the time that I was missing important calls about a family member's health.

Lying to somebody like that -- what the hell is even the point? You think you're going to build a rapport with me by starting our relationship off by lying to me? Specifically, lying about something that could cause me a considerable amount of stress if I believed you? And how long do you think you can keep somebody believing the lie when you clearly have never even looked at his resume?

Does this actually work often enough to keep Strategic Staffing Solutions in business?

I sent that E-Mail out on the 29th. It's been four business days and I think it's a pretty safe bet that Adam's not going to be getting back to me. Not so much as a "Look, I'm sorry, they make us say that, there's no problem with your phone and I hope your grandpa gets better; is there any way I can still help you?" When faced with the potential consequences of his lie, he didn't take the thirty seconds it would have taken to come clean and apologize to me. He just chalked me up as a loss and moved on to the next sucker.

So I'm pretty comfortable in saying fuck Strategic Staffing Solutions, fuck their sleazy, dishonest recruitment tactics, and fuck the horse they rode in on. If you do business with Strategic Staffing Solutions, know that you are doing business with spammers and liars -- and that if they were so cavalier about lying to me, they're probably going to be more than happy to lie to you too.

Finally, here's a list of domains that have sent me job spam, and I'll probably add to it as time goes on. Please feel free to add them to your own spam filters. And hey, if this creates some negative word association for these domains on Google, I'd be pretty okay with that.

  • strategicstaff.com
  • enterprisesolutioninc.com
  • net2source.com
  • colcon.com
  • pyramidci.com
  • ittblazers.com
  • artechinfo.com
  • usgrpinc.com
  • diverselynx.com
  • axelon.com
  • h3-technologies.com
  • mondo.com
  • simplion.com
  • genuent.net
  • abacusservice.com
  • compnova.com
  • spectraforce.com
  • syscomtechinc.com
  • iit-inc.com
  • eteaminc.com
  • project1.com
  • globalsyst.com
  • ustsmail.com
  • ustechsolutionsinc.com
  • rconnectllc.com
  • lorventech.com
  • talentburst.com
  • softpath.net
  • waddellcareers.com
  • first-tek.com
  • quantitativesystems.com
  • advantageresourcing.com
  • gtt-it.com
  • mamsys.com
  • enterprise-logic.com
  • diversant.com
  • fortek.com
  • stemxpert.com
  • panzersolutions.com
  • opensystemstech.com
  • itstaffinc.com
  • princetoninformation.com
  • rjtcompuquest.com
  • greenlightstaff.com
  • judge.com
  • techdigitalcorp.com
  • ttiofusa.com

More from Busiek on that Final Fantasy Comic

2015-01-08, 12:26 pm
Categories: Comics, Games

For those of you just joining us by way of a link from Kurt Busiek or CBR, welcome. I guess I should probably figure out something interesting to say so you'll feel like sticking around for a bit. For what it's worth, I've written quite a bit about Final Fantasy over the years, and three posts I wrote about FF7 back in 2011 (the first on mods for the PC version, the second on iconic images, and the third a general look back on the game) are pretty consistently the most popular thing on the site.

In lieu of me saying anything interesting, I'm going to quote a little bit more from Kurt Busiek on the unfinished Final Fantasy comic, in the comments section of the Robot 6 article on the subject.

I will also add that if the book came out, I don’t think that Final Fantasy fans would be particularly happy with it. It was 1991, and I was a workmanlike-but-not-particularly-noted writer. Dell Barras was a workmanlike artist, and, well, the covers were gorgeous.

But I don’t think I really started to make strides creatively as a writer until VAMPIRELLA: MORNING IN AMERICA (late that year) and the industry didn’t notice ’til MARVELS in 1993.

So, while I barely remember the details, I expect it was a workmanlike story that made sense but wasn’t particularly memorable, with workmanlike art and great covers.

And heresy upon heresies, I changed things (with Squaresoft’s permission). I thought it was so odd that the manly heroic lead was named Cecil and his loyal buddy was named Cain (really? You name the loyal guy Cain?) that I suggested maybe they needed Americanized names, and Squarest agreed. I don’t remember what I changed them to, but Squarest liked them enough that they asked if I’d be interested in a staff position making the games more American-appropriate. We never talked much about it, because I wanted to freelance. But I bet fans devoted to the game wouldn’t have liked the changes, especially not from a current POV, looking back.

What can I say? I wasn’t particularly a Final Fantasy fan — I’d played their first US game a little, and the second wasn’t even done yet.

He adds, in a later comment, that the bible he'd been given didn't even mention that Kain spends half the game betraying Cecil, and talks a little bit more about the original (FF1-based) outline he wrote.

(If he had been involved in localizing the game, I'm willing to bet it would have been better than what we initially got. But he'd have still been contending with cartridge space limitations and weird Nintendo censorship.)

Mignola Final Fantasy Covers

2015-01-04, 9:47 pm
Categories: Comics, Games

Well now. It appears that Kurt Busiek just reblogged a Tumblr post by Alex Chung, which, in turn, links back to a post I wrote back in '012 about Busiek, Barras, and Mignola's unfinished Final Fantasy comic (based on Final Fantasy 4).

So since that old post is probably getting a little bit of new traffic, I should follow it up, now that I have a couple of Mignola's covers for the series.

This one is via Chung's post, and would have been the cover to issue #2:
Final Fantasy #2 cover

And this was sent to me just over a year ago by Dale Jackson, who owns the original art; it would have been the cover of #4:
Final Fantasy #4 cover

Alex, thanks for linking to my post and for including the #2 cover; Dale, thanks for the heads-up on the #4 cover and I'm sorry it took so long to post it.