ctomaybe
ctomaybe on Hacker News
4) Put secrets in that bucket (duh)
Snooze.
Concepts are a dime a dozen and while these are nice pieces of art I can't really take them seriously as App designs.
Focus on real products and the people making them.
I get that non-expiring tokens are a Bad Idea™, but it's complete bullshit that this is a groundbreaking security flaw. Any service that uses Bearer tokens for request authorization is "vulnerable" under these terms -- regardless of whether or not tokens are invalidated on "logout." What's to say a malicious MITM isn't going to hijack your account while you're still logged in?
Secure infrastructure isn't the one and only solution, but it certainly means that "vulnerabilities" like this are pointless unless your malicious attacker either has the remote server certs or has cracked TLS.
Just spent more time than I would like to admit making those voices say all matter of inappropriate things and giggling to myself.
1) Have an EC2 instance with a role-specific IAM Role
2) Create a S3 bucket
3) Write a bucket policy that whitelists specific IAM Roles to specific key paths within the bucket.
Nah, don't worry man, nothing troublesome could happen as a result of this!
I was going to say... we were launching it just after I left the team last year!
I would learn to connect more closely with my family and friends. Do some maintenance on your relationships. You may find down the line that the longer you wait to invest the kind of time you have right now, the less effect it might have.
I'm not suggesting that I'm strongly considering the option; I'm merely suggesting that the option exists. I don't like the sound of it either!
I mean, right now I have about 1% equity and I'd jump to near 10%, so in the event of wild success of the company (let's say a 100M exit) I'd be way ahead, but in the meanwhile I don't think it's responsible to sacrifice the financial stability we're just arriving at. I'm in no position to open deep lines of credit and have no savings, so it's not like those are options.
The way I see it, it's really a timing issue more than anything. If I were a homeowner, I could consider an equity line on my home to cover a couple months of expenses (plus I wouldn't be paying rent...), or if I had a longer credit history I could open a big card with the understanding that I would either have a good exit with the company or leave for a well-paying, more stable job at a larger company at some point and be able to repay the debt either way.
It's just the wrong time in my life to take this risk, unfortunately. It's not even the long-term effects of the risk, either, it's the change to the near-term status quo that I don't think I'll be able to handle.
There's definitely a component of saving burn rate for the company and making me more literally dependent on the success of the company. I understand the perspective there and the needs that the company has right now, but I'm leaning on the no side -- if I can't provide for myself and my wife a stable means of living, there's no way I can continue doing the high-quality work that has earned me this offer.
That's where I'm leaning. I want to be part of this in a big way and I want to contribute in every way I can, but if I can't afford to live while doing it then it's not going to fly.
From a circumstantial standpoint we're in a significant pivot that's gotten really good response but we're running short on runway on our first seed round from 1+ year ago (hence the emphasis on lessened salary).
Posted by
ctomaybe on Friday December 11, 2015 @12:09AM
from the ask-hn dept.
Hi all.I'm a little at a loss here. My CEO just offered me to fill our vacant CTO role and become a co founder to the company. I feel up for the challenge and capable of the responsibility, but I'm a little fearful of taking a salary cut (from ~100k to < 50k). I am our only earner between my wife and I, and we are finally reaching "financial equilibrium" (we racked up a ton of debt just...