I just think this is absolutely the wrong response. As a freelancer or business your reputation is paramount - that reputation should be for professionalism and courtesy, even when others are not professional with you. This sort of incident teaches us the value of contracts, staged payments, and trust with your clients. If you don't have a good trusting relationship with clients, it's best to end that relationship and find other clients. If a client screws you, I think the best response is to make sure people know what they did, and adjust your process so that future clients can't do that, not abuse your power over their domain/server to post a partisan message like this.
So I'm afraid your assumptions about my motivations are completely unfounded - perhaps you'd like to rethink them and offer me an apology?
I'd definitely like to offer you the advice to never indulge in this sort of passive-aggression, it's very unprofessional and should make anyone think twice about working with you.
Noting this does not require thinking you are one of those people. There is an explanation that is at least equally plausible: You, like so many others, have been inculcated with contradictory views by a society which gives power freely to the dishonest, while purporting to value honesty, but in a form designed to further empower the dishonest.
Noting this does not require thinking that you are one of these people, in the context of strict logical inference.
Noting this is absolutely an (oblique) accusation in the context of a conversation in English.
Pragmatics is an interesting field.
If you hand over the keys to a car and tell them that they can start driving it and then pay you when ready, would you post the same response?
Car dealerships don't work that way, you need to sign a contract to use the car - usually web agencies are similar and require full payment or atleast a "payment plan" in place for a website to launch.
Quite true. This isn't a car dealership. Doing website support for small businesses in medium and small markets often does work that way. They have a site, they would prefer that things are added to it, instead of a complete replacement. Back when I was doing webapps in this situation, the business would often insist on running the site from their T1 or ISDN line, refusing to spring for hosting someplace where they can't see the physical hardware to reassure themselves that there is something there.
"You want to back up the database for testing? No, just connect to the production database."
"No, you don't have access to webserver config; just build it in a folder." (It turns out that they don't have such access, either, since they "had a disagreement" with the guy who set up the box for them before he left on bad terms. Asking about how to contact this guy is apparently suspicious).
"You want us to sign a contract? We'll look at it." (They never get back to you, since they can find a dozen other people who are grateful for the promise of payment).
"Pay before it launches? Oh, no, we pay net 60, but our site says 'New site coming Oct 1st!', so unless it's up then, there's no reason for us to pay you." (Of course, they put this up without consulting you after you agreed to start prototyping).
And this is to say nothing of the people who insist on detailed designs and specification documents, then say, "Actually, we're going to wait a little while", and then you find your designed system on their site creaking along like it was written by the nephew of the boss's secretary, who totally learned computer science stuff in high school this semester. Surprise! It was written by that guy, except they hired someone else at $15/hr to randomly change things until it worked, since he had to go back to school when spring break ended...
It's not that there are a few businesses that operate like this: this seems to be the majority of small-town businesses who need webapps. When I ran a business doing webapps and web design in the mid-2000s, I'm not sure I ever ran into an end customer who didn't try to pull something I found really shady, though for them it was just the normal way they think they have to deal with vendors so that they can stay in business.
When I gave up and got a salaried job in 2008, my stress evaporated, even though it was a job at a failing startup. :)