HN user

telgareith

149 karma
Posts0
Comments122
View on HN
No posts found.

Yes- AWS calculator: 1) S3- cost for how much you're storing in glacier and then the cost for its metadata to he in a S3 hot/warm tier. 2) Glacier retrieval cost- can be minimized by letting AWS pull it on their schedule. 3) BANDWIDTH- this is the vast majority of the cost at $0.09/GB. There may be ways to lower this, but I haven't tried them.

I'm not saying its a bad deal, I very much wish I'd gone with deep archive (especially with the recent addition of "update if different" to the API)

Worst case, it's $90/TB of bandwidth, the retrieval fee, and GB-seconds for a hot S3 tier while waiting to he downloaded and then deleted, plus pocket change for API calls.

With 10TB drives being available for $80-ish... I expect a lot of semi savy people to upload tens of terabytes then cry when they see the bill.

Numbers rounded a bit for simplicity.

DKMS solved these "licensing issues." Dell is mum on official motivation- but it provides a licensing demarcation point, and a way for kernels to update without breaking modules- so it's easier for companies to develop for Linux.

_Windows Drivers work the same way and nobody huffs and puffs about that_

I'd love to have an intelligent discussion on how one person's opinion on licensing issues stacks up against the legal teams of half the fortune 50's. Licensing doesn't work on "well, I didn't mean it THAT way."

The two scenarios: 1) handing a business your life savings to manage, a 2) authorizing a company to manage your finances so they're in FDIC insured accounts

Are completely different. There's no laws to update, and the FDIC isn't skittering out of paying on a technicality.

And, frankly, if anybody reading this is looking at option #2- do yourself a favor and get an accountant and a wealth manager that both have fiduciary duties. Might as well find a lawyer as well.

Any comment on what issues there are with paying somebody to open accounts for you with, I assume- a power of attorney allowing them to do explicitly that?

At that point the only thing at risk is fraudulent use of said POA, and whatever funds are held outside of actual accounts.

Or just enable "WPA-enterprise" and have it rotate keys. Then you not only have device certificates, you also have per user authentication. And if somebody missed it- rotating keys. They can change faster than they can be cracked. Then you can also layer VPNs ontop of that...

All of which are standard, well known, and proven solutions.

What does that repo offer? With 400 stars, I doubt anybody has given it serious attention.

Server side session state for more than authentication is way worse than "code smell."

It requires a ping to a shared data source on every request. And, the same one for all of them. No sharding, No split domains... That gets expensive fast!