[duaneb]

> This developer may have exposed himself to a level of risk based on his own contracts and work arrangement. Why was the site up in the first place if he was not paid in full?

I mean, I'm a small fish compared to this guy, but I always have the site up and running before hand. Most of the time, I just outright buy the domain and transfer domain rights. This is exactly the kind of thing I do when the contract is violated- that is, when I deliver on my end, and there is a functional site, but they didn't pay.

What I'm saying is, I think you're assuming too much about the nature of how this guy does business. Money isn't about trust, it's about contracts; trust is just what gets the contract signed.

[greaterweb]

I was a small fish as well for many years, 5 as a freelancer and 5 as a small business owner. We all have to take those risks initially when getting started, "I can build you a site that looks like this for this much money!" But we concede those risks when we do so.

In all of my years I have only taken 2 sites down for non-payment. That was the extent of it though, no payment, no site. I personally would never feel comfortable using a clients domain as my own platform to state my side of the story, it's just not appropriate in my opinion.

I want to support fellow designer and developers but in this case I just can't blindly do so without hearing both sides on this or a bit more detail from the developer. The developer has posted little more than invoices were unpaid and he's shutting down the studio like P-Diddy. For all we know through his own initiative he exceeded the agreed scope of work and wants to be paid for it.

Maybe more information can be surfaced and we can rally behind this guy. Until then I've got to stay neutral and look at things objectively.

[duaneb]

> I personally would never feel comfortable using a clients domain as my own platform to state my side of the story, it's just not appropriate in my opinion.

I would agree about this-I just throw up a site that looks OK with the company's contact information on it, or just take it down entirely.

[dhimes]

This developer did expose himself to a real risk, and one he probably didn't even think of: that little site, which is essentially a text message, is driving my Chrome instance crazy. WTF did he code into it? Would I hire him?