SudoAlex

Joined 14 years ago

Karma
415
Submissions
50
Member since
Jul 20
[ my public key: https://keybase.io/tomkins; my proof: https://keybase.io/tomkins/sigs/PkJkr084f4r0s3LM91zfhVtz-HlgoldIm7cKgExEfjY ]
View on Hacker News

Recent submissions

Comment · 3 years ago
Comment · 3 years ago
They already do something - the oil patterns they use on the lanes is considerably different for open/league bowlers compared to competitive bowlers.

However the professional bowlers will have the skill, experience and equipment to deal with all the different oil patterns.

Comment · 3 years ago
Sony ZV-1, Elgato Cam Link 4K, and a few other minor accessories (eg. lighting).

A huge amount of time is spent on video calls these days, and although there are more advanced webcams out there these days - a camera which is geared towards video (the ZV-1 is aimed at vlogging) will produce significantly better video for any calls you're on.

Spending a little bit of time optimising your setup so that you're the one in the call with good quality video/audio is worth it. Get a decent camera, get a good microphone, improve your background lighting.

Comment · 4 years ago
Technically CloudFront requests to the origin server are IPv4 only, so there's still IPv4 in the stack even if the distribution has IPv6 enabled.

Personally this is one area I'd like AWS to focus on, along with load balancers listening on IPv6 only (currently it's dual stack). Every load balancer we deploy takes up at least 3 IP addresses - I'd quite happily switch them to being IPv6 only if CloudFront could access them over IPv6.

Comment · 5 years ago
Comment · 5 years ago
Same here - a price increase makes you reconsider the relationship you've got with the service you're using. Companies should strongly consider leaving existing customers alone with legacy plans rather than aiming to extract as much revenue as possible.

For me Dropbox didn't do that, so instead of happily leaving our existing business account for most team members - we re-evaluated our usage of it, limited it to just a few accounts with the aim of getting rid of it entirely.

At that point it's not something you'd consider recommending it in passing to other people.

Comment · 9 years ago
Or you do nothing wrong on your server, but another user using your mail server ends up with a compromised password, or reuses the same username/password from elsewhere as their mail login. You wake up and see thousands of outgoing emails in your mail queue, all from the spammer, followed by other users who can't send outgoing emails.

You could attempt to limit the outgoing emails per account per hour, however if that's set too low then you end up with other users who can't send out emails to their "mailing lists" consisting of hundreds of contacts, instead of using a real mailing list to manage it.

The effort just isn't worth it.

Comment · 10 years ago
The correlation could also be the fact that you've blocked the attack, they can see that their previous attack is no longer working by testing it themselves - so they'll switch anyway, regardless of a status page update.
Comment · 11 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton