Recent submissions

Comment · 7 years ago
Regarding 2), you could just make healthcare insurance mandatory. We have that in The Netherlands.
Comment · 8 years ago
Comment · 9 years ago
Comment · 9 years ago
I think the rough IPv6 equivalent of a single IPv4 ban would be to ban a /64 subnet. This bans all users in that subnet which is the same as banning an IPv4 subnet hiding behind a single NAT address.
Comment · 10 years ago
Comment · 10 years ago
Not really although you probably need to use quite a bit of traffic before it becomes a problem. Your example of personal use only seems fine.

There was a post here a while ago (that I cannot find anymore) about the devs of a package manager of sorts who were asked kindly by Github to do something about their excessive data usage. So it's probably not a good idea to build a company on it.

Comment · 10 years ago
They do, yes. Rounded up to the nearest 100ms, scaled for chosen RAM capacity: https://aws.amazon.com/lambda/pricing/ Note that this doesn't measure actual RAM use, although they do display it after lambda runs.

Data traffic is already measured and priced accordingly in AWS so that's not something new for Lambda.

Comment · 10 years ago
Comment · 10 years ago
I thought that too but I successfully raised our limit after they made it a soft limit, so give it a shot!
Comment · 10 years ago
Comment · 10 years ago
This just shows we really do need a step towards an 'appstore-like' permissions model for desktop operating systems. There is just no reason for all these software packages to have full write access to everything in your user account.
Comment · 11 years ago
Comment · 11 years ago
Like passwords, sharing API keys is usually a bad thing. For some sites it is overkill or simply not possible but for something like AWS there is no excuse not to make individual IAM users with their own passwords and keys.
Comment · 11 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton