And I assume that you may also have some recourse in 'small claims' court.
At the very least, file a complaint with the BBB in his area.
http://www.bbb.org/
If he ever tries to become a member, he'll have some explaining to do.

And since what you're going to post is 'the truth' you can't be liable for
libel. And DO name names since that's the only potent club you've got.

And have you tried phoning him to confirm that he really ISN'T going to
pay. Computers do go down and it can sometimes take weeks to get them
back up. Never attribute to malice that which can also come from
stupidity (or long winter vacations). You really should try to
talk to him on the phone before pulling the trigger. And he may have
gone bankrupt, in which case you'll want to file a claim with the
trustee or bankrupcy court in his locale ASAP.

Robert

Jesse Lackey wrote:
>
> Why are you hesitant to name names?  If he is a deadbeat, in other words a
> *CROOK*, I personally want to know who he is, to avoid becoming his next
> victim.  Few *hundred* hours?  Are you kidding me?  Send him another email
> warning him that you will go public with the situation if it makes you feel
> better then POST.  If you are an honest person, and it sounds like you are,
> you deserve honesty from those you do business with.  If he has anything to
> say then he can post too.
>
> Frankly, I'd make a short web page about him and the situation and feed it
> to google.  When he remedies the situation to your satisfaction, you can
> change it or take it down.
>
> Its not like you will be committing libel & you are doing honest freelancers
> a favor.
>
> Jesse
>
> Dale Botkin wrote:
>
> > Well, it finally happened.  What started out as a promising paying
> > code-for-hire job went bad, the customer has stopped responding to emails
> > and has apparently decided not to pay for the work done as agreed.  Since
> > we're several states apart and the amount isn't enough to get lawyers
> > involved, I guess he gets away with it for the time being.  I'm really
> > disappointed; it's not like my kids are going to go without shoes this
> > winter, but there are a few hundred hours of my time I would have spent
> > doing other things if I'd known I wasn't going to get paid for them.  I
> > even offered to be flexible on the amount if he was in financial straits,
> > but there has been no response to my last four or five emails since
> > December.
> >
> > I debated for a few weeks whether or not to post this to the list.  I
> > don't want to be seen as using the list or my so-called position as list
> > admin to push a personal agenda.  Sooner or later, though, the guy is
> > going to need some changes or fixes made to the code, and I suspect he's
> > going to turn to another PICList member to do it.  I'd really like to
> > spare the next guy the same fate, and yes, it would irritate me to know
> > someone else was getting paid to do what I should have already been paid
> > to do.
> >
> > I'm not going to name names or go too deep into details, but if you get an
> > email from someone looking to have some work done on some CCS C source
> > code (that still may or may not have my name attached), you might want to
> > drop me a note privately to see if it's the same guy.  IANAL, but as far
> > as I can tell since I didn't get paid as agreed, he's got no right to the
> > code.
> >
> > Dale
> > ---
> > Time wounds all heels.
> >         -- Me
> >
> > --
> > http://www.piclist.com#nomail Going offline? Don't AutoReply us!
> > email listserv@mitvma.mit.edu with SET PICList DIGEST in the body
> >
> >
> >
> >
>
> --
> http://www.piclist.com#nomail Going offline? Don't AutoReply us!
> email listserv@mitvma.mit.edu with SET PICList DIGEST in the body

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body