Some «security» features dont need to be secure. This is obviously one of those as the data is readable by all, but only modifiable by «those in the know», but if someone does anyway who cares.
I’ve done hardcoded frontend identity whitelists for authorization. Some times it’s fine to let hackers access stuff, but not the vanilla mass-market browsers. Feature flags etc
Actually, I think this one is better if it isn't perfectly secure. I make spreadsheets with passwords just so people won't go in there and accidentally delete something or make other silly mistakes. I'm not trying to hide anything or keep it safe from the outside worldor anything. Every once in a while I forget one of the passwords or set it up with a typo or something, and I have to crack it. I'm sure there's loads of people doing something similar. For me, the weak security on this particular password is a feature.
Research also suggests that NAFLD is present in up to 75% of people who are overweight and in more than 90% of people who have severe obesity, also called extreme obesity.
I found caprover to be great for simple web apps. the git push and build on prod server feels like a remnant from before proper ci/cd with docker built separately was as available.
Friggin love CapRover! It's definitely helped take the anxiety out deployments for me. OPs solution is cool & novel but still looks like too many moving parts for my taste. I find CR too be a great balance between fully rolling your own with scripts and custom commands, and the full blown automation of kubernetes.
this seems to be a common attitude in America. It’s game theory, but you should look more to the nash equilibrium than the prisoners dilemma. Unfortunately it must all start with trust, which seems like the fundamental scarcity in the US
The problem is we have basically 2 "phenotypes" (gross oversimplification) with radically different risk tolerances, one "tribe" is okay with abstracting away their security/defense, the other wants granular control over it.
So there's 3 agents:
1. Government. Trustworthy, until it isnt.
2. "Union" - Trusts govt. Ok with "gun grabbing" because civians with guns make them feel safe.
3. "Rebels". doesn't trust government. Ok with guns - armed society is polite society.
So it's a very unstable dynamic. It's stable at the extreme ends - everybody has guns, or only government has guns - but the transitions are high activation energy states.
> everything (local state management, API calls, forms, URL routing, etc)
hooks, axios, html, reach-router.
my point is that if you start with the assumption that browser APIs are sufficient, there is a natural progression to your project and «taste» in supporting libraries to react
I’ve done hardcoded frontend identity whitelists for authorization. Some times it’s fine to let hackers access stuff, but not the vanilla mass-market browsers. Feature flags etc