rajvosa07

Super helpful, thanks!

Interesting take here as well: https://prospect.org/power/senator-thom-tillis-pushes-prison...

I really liked: The REST API Design Handbook by George Reese.

It is everything you need to know and thinks about the angle of the people who need to consume your API. Quick read too.

https://www.amazon.com/REST-API-Design-Handbook-ebook/dp/B00...

I used to keep that up and thought it essential to survival, but I lost the battle. Instead, I've created alternate methods to make sure I don't miss the important stuff. I use Polymail for most of my email which allows me to snooze emails for a few hrs, days, a month, etc. and resurface them as if they were new at a better time. I also file away very important emails into folders / tags depending on the system so I can find them more easily.

The reason sharing requires a registration is so it can be end-2-end encrypted. Anything less than that is way easier for hackers to get their hands on.

You shouldn't do this UNTIL you need to.

You NEED to before allowing any operations that rely on this information being accurate. Let's say you are allowing users to chat with each other, or share information. In that case it is super helpful to verify the initiating user's email as proof of identity, so I can't just enter your email and phish someone...

Personal.com has a solution for this. It is cloud-based, with strong crypto and no need/motivation to see your data = secure. Secure Share is built-in and allows each team member to manage the passwords they are responsible for and share them with exactly the individuals that need access to them. Access can be revoked allowing you to revoke/change password on a regular basis, or as needed.