“every single direction change I suggest, codex is all: "that's a great idea, and we should totally go that [very different] direction", try as I might to get it to act like more of a peer.“
That’s not the model, that’s a personality setting you can change in the codex config file.
Set it to Pragmatic, and ask it (not command it) about your new direction in planning mode.
It will tell you if your idea is not good for the given project.
It’s an excellent peer.
At the same time, everything you ever posted online has already been scraped by hundreds (maybe thousands) of entities and distributed/sold to countless other entities. The only difference is that OP shared his project here.
This is completely offtopic, but I would bet it was a government-funded museum.
A reasonable institution would have worked with you to find an acceptable compromise, something much easier to implement with a small sacrifice of aesthetics.
Anyway, great work, and thank you for taking the time to share it!
"mostly profit someone else who did nothing but write you a check"
There is quite a bit of work involved in reaching the point where you write a check for a Series A round. Also, the better VCs spend significant time with their portfolio companies.
Strange that I had to scroll down this far for this answer. Creating a normal, non-admin user for them will greatly limit the damage they can do as they won't be able to make system-wide changes. I also disabled installing extensions in Edge.
You should never store unencrypted secrets, like this export file, on an unencrypted disk. Not even temporarily.
Instead, create a small encrypted drive on a pendrive or as a file with LUKS or Veracrypt, mount it, and save the file _directly_ there.
Not sure about GPL, but this is one of the very few (2-4) restrictions of a BSD license:
"Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission."
This is exactly how most web applications were written 15 years ago. Server side rendering with PHP, ASP, JSP, and then Javascript for the interactive bits.
Both options have risks, in 90% of the cases, the risk you pointed out is smaller then the risk from the lost opportunity cost (working on something not relevant for the service), insecure implementation, sub-optimal UI, etc.
What do you mean exactly here What do you think LastPass could have done to prevent this specific issue?