3 ms·
Cope. HTML and CSS is delivered client-side, for the past 10-odd years any so-inclined asshole dev could slurp up and reproduce your website instantly. > But h
by talldayo 2y ago
Cope. HTML and CSS is delivered client-side, for the past 10-odd years any so-inclined asshole dev could slurp up and reproduce your website instantly.
> But how do we protect our work from being copied? What can we do to ensure our original work isn’t taken and used by others?
Simply put; you keep it to yourself, and never share it with another living soul. Further reading: https://en.wikipedia.org/wiki/Tragedy_of_the_commons https://en.wikipedia.org/wiki/Tragedy_of_the_commons
- bob1029 2y ago> Simply put; you keep it to yourself, and never share it with another living soul. Server-side rendering and mandatory logins can go a long way toward making it painful for others to slurp up your IP. If you build your products the way all the cool kids have been the last ~half decade (i.e., shipping the entire product & business logic to the client), then you may find this kind of frustration inevitable.
- aiagents_dir 2y agovalid point. i will need to put more effort in security to minimaze impact of the cloning.
- beardyw 2y ago> Simply put; you keep it to yourself, and never share it with another living soul. Hey, that's what I do. Also cuts down maintenance, complaints, cost, judgementalism, you name it.