§ 18 - Licensing

Let's not play this game. I built dTank (β) so people (including myself) could use it, not so lawyers could buy new cars. If you bought the dTank (β) application executable from me, or I gave you a copy of it, then you own that copy of the application executable.

Does that give you the ability to resell dTank (β) or share it? Yes, it sure does.

Does that mean that the person or persons you share with, or sell the application to, now own a copy of the application? Yes, it means that as well.

Do I want you to sell copies of something I sold you, or re-share it? No. If you do that, this could negatively impact my income. So I ask that you not do those things. That's all. It's just an ask, or perhaps it's fair to call it a concern of mine. I have no concern with you selling a copy of software I sold you and then deleting your own copy, by the way — that seems perfectly fair to me. But either way, it's yours now, so you decide.

Presently, dTank (β) is donate-ware, meaning that I give it to you, not sell it to you. But the above may become more relevant should I change the distribution model to a cost-per-unit one. That, in turn, will depend on how donations go.

So anyway, thanks for taking an interest in my work. I hope you get some benefit from it. Cheers!

§ 19 - Warranty

Here's the deal: I'll try to keep the application maintained. I'll try to fix any bugs I can that I know about. I won't charge you for either of those things. You might want to consider reporting any bugs you find to me so you're sure I know about them; that way there's at least a chance they'll get fixed, or at least looked into. Please be aware that some bugs are not bugs of mine; they are bugs in the operating system, and those are things I can't fix.

You do use the application completely at your own risk. If you're not willing to do that, then you shouldn't use it. Duh.

Yeah, there are some laws that could end up putting me through the wringer regardless of how honestly and forthrightly I manage our business relationship, try to keep the application reliable, etc. There's nothing I can do about that which I am actually willing to do. I'm old anyway — you sue me, I'd probably die of a heart attack, and you wouldn't get squat, even from my estate — I donate most of my income over my cost of living to charity. So suck it, lawyers.

§ 20 - Host Operating System Compatibility Over Time

I have developed dTank (β) on the oldest version of OS X that supported 64-bit applications I could manage, which is OS X 10.6.8. This means (hopefully) that it will work as intended on that version, and every subsequent version of OS X. However, please be aware that Apple often makes changes to OS X that can result in serious incompatibility, perhaps even complete failure to run, for applications that actually follow the development rules they had previously put in place (which I try very hard to do.) I can't promise that won't happen; so I can't promise that an OS upgrade won't cause dTank (β) to fail in some way, either minor or major.

Tip: Should you run into an OS X revision that won't run dTank (β), it might be worth your time to set up a virtual machine running a previous version of OS X to get around that. In fact, that's how I develop dTank (β) — on a 10.6.8 virtual machine, which is how I know it continues to work there. I use it under OS X 10.12.6, though, on a reasonably robust Mac Pro: 12/24 cores, 64GB of RAM, plenty of fast SSD storage.
Keyboard Navigation
, Previous Page . Next Page t TOC i Index o Operators g Glossary

Valid HTML 4.01 Loose
 

This manual was generated with wtfm
wtfm uses aa_macro and SqLite
aa_macro uses python 2.7
Please consider supporting my dTank (β) development efforts via a small PayPal donation.