jnazario

maybe i could have shoehorned it into a KV store and done range queries, but again this was stuff like "timestamp, srcip, srccc, srcasn, eventid". the main vector is a timestamp, and every query has a timestamp range associated with it. these are written once, never updated. other data stores don't optimize for those parameters.

i concur.

while it's likely i've implemented my SQL horribly, i can say that after a few days of millions of hits per day in my time series database, searches became horribly slow and interactive became unresponsive. in my case it was a set of botnet sinkholes that i was recording.

so yes you can, but on the high volume side of things (for some cutoff of "high volume") it falls over pretty dramatically and continues to degrade.

time series data has a few unique properties that a full SQL solution doesn't optimize around, like write-once/read-many. a purpose-built TSDB solution is built for this.

github has a lot of constraints due to their size and services, most startups don't have those same issues.

cloudflare is a good way to do it on the cheap. as revenue comes in, you can either do internal, self-hosted mitigations and the like, or you can go with cloud mitigation providers. both cost a bunch and require significant IT/operations spending and staffing (self-hosted more so) to afford it and make it possible.

once your at a sizable pipe to your upstream provider(s), talk to them to find out where to call BEFORE an attack occurs, figure out how to navigate their offers as needed QUICKLY and efficiently to keep your service outage minimized, and see what it will cost you. almost every big ISP does this.

if all you do is buy a firewall, so what - your pipe will still fill up. that's why you need the upstream ISP.

in short, it's not cheap or easy but do this NOW before you need to.

if you're cloud hosted - e.g. DO, AWS, Azure, etc - look at your terms of service and call your account manager and find out what they can do for you and what it costs. again, do it before hand.

from the phrasing i would have expected the code itself had been changed.

i thought the same thing, and recall thinking that about the taliban back when they destroyed what were then the largest buddha statues.

while it sickens me too, the main justification i can think of for it is that these artifacts represent the human story much more than any one person can. they are the collective achievement of thousands of years of progress and invention, and in seeing them destroyed we see our very history and future threatened more so than any one person's death can.

while i can't say i feel fully comfortable with a human life being worth less than a thing, this is one way of thinking about it.

kodachrome was my favorite film to shoot. it always made even average pictures feel like NatGeo. just the right about of saturation, of fade, of crispness. the color balance was very unique.

that show of Nürburgring is great :)

OP, i'm going to add another comment here to what i said earlier. before you quit, go in and talk to someone in senior management.

ask for a meeting with someone senior, let them knows it's important. when you get the fifteen minutes you asked for, raise you concern. it undermines trust between sales and senior management, it's a big stress, etc. give them a chance to respond. there may be a perfectly sound reason for it - the money may piss you off but it may also mean the business can stay around longer for everyone.

if you don't like what you hear, pull out your short letter of resignation, sign it, and hand it over. don't make a stink, just say, "i'm sorry, i don't think i can do this. i have to resign."

but you gave them a chance, you were heard, and you made an opportunity. they'll connect the dots, but no harsh words should be spoken (no "get bent you jerk!"). don't burn any bridges, but this will be a way to be clear about what happened, and it may create an opportunity, in fact (who knows).

i hope that helps.

you do not, you never put something like this in writing. it can and will come back to hurt you.

what a3n said.

[update - i read the back story elsewhere and the reason is less boneheaded than i had assumed. still, i think the community needs to focus on higher priority needs and gaps]

this is the sort of thing that makes me happy i'm no longer involved in the OpenBSD world. httpd & previously smtpd are two replacements that (in my opinion) have little additive value beyond existing, community-adopted solutions (e.g. nginx and postfix), diluting effort where it is needed.

does the world need a new httpd? maybe. but the world needs other replacement software to be done first because it'll have a greater impact.

for example, OpenBSD could invest time and effort in maturing static code analyzers to assist in code audits (especially of ports).

i suspect this new httpd was done less because it was needed and more because it could be done. that's the attitude i disagree with.

in a nutshell, close the skills/talent gap. not enough people qualified for the million or so open roles. close that gap somehow.