evanosaurus

4 ms·

1.
by evanosaurus 9y ago
These three things (plus your addendum of working together to solve stupidly hard problems) are basically why I love going to work every day. (I work at Epic on Team Online, aka the team that this whole PM is about.)
2.
by evanosaurus 9y ago
We’d love to, but have been told that our providers don’t yet have enough capacity for us to flip our entire fleet over to c5’s just yet.
3.
by evanosaurus 9y ago
We don’t tick at 30Hz. Somewhat slower than that. Working on making that better, though. And we do indeed take advantage of reserved instances. We’re also looking at other options along these lines.
4.
by evanosaurus 9y ago
Nope. No creative counting. Those are our real numbers.
5.
by evanosaurus 9y ago
Hi. Guy who does the autoscaling code here at Epic. It's really fun to watch the graphs of how many server sessions we have in a region at any given time over the course of a day.
6.
by evanosaurus 9y ago
We run 16 game servers per c4.8xl instance for Battle Royale. We run more than that (on a different instance type) for StW.
7.
by evanosaurus 9y ago
Our account service went down for a brief period this morning. Sorry about that.
8.
by evanosaurus 9y ago
This is why we’re mostly stuck in Perforce hell in the games industry.
9.
by evanosaurus 10y ago
>Do not show alerts in the Touch Bar, and do not use the Touch Bar for widgets. It's interesting, then, that they explicitly showed the Touch Bar being used for alerts in the design video (when the user received a FaceTime call).
10.
by evanosaurus 10y ago
You can't flash the firmware yourself, as the keys are discarded as soon as they're generated per device. What you could do, however, is read the bits off of the firmware and make sure they're identical to the bits you make
11.
by evanosaurus 10y ago
Seriously. Gandi is the only registrar I use anymore.
12.
by evanosaurus 11y ago
That's the current state of affairs. I know of no baseband manufacturer who has ever offered (nor seemed open to the idea of releasing) source for their chips. Basebands aside, the rest of the device is somewhat feasible to see being o
13.
by evanosaurus 11y ago
Unless there is a bug in their hardware implementation of AES-CCM or ( shudder ) some sort of crazy disclosure vulnerability in the APIs they provide, there is (presumably) no way to get at the UID. Even if you were to decap the chip and ge
14.
by evanosaurus 11y ago
Not necessarily. Despite the openness of Android/AOSP, there are still, unfortunately, things like binary blobs for certain graphics chips and closed-source firmware for things like Wi-Fi chipsets. Given what we've seen agencies l
15.
by evanosaurus 11y ago
That's essentially what Let's Encrypt aims to be: https://letsencrypt.org/
16.
by evanosaurus 11y ago
A number of developers from RedHat were once very involved in the project. However, these developers had a very arrogant attitude towards Docker: They wanted docker changed so that it would follow their design ideas for RHEL and systemd. T