Nick-Craver

7 ms·

1.
by Nick-Craver 5y ago
For pub/sub yes that's correct. For full info though: Redis later added streams (in 5.x) for the don't-wan't-to-miss case: https://redis.io/topics/streams-intro
2.
by Nick-Craver 6y ago
Clarification there: I have a US-8 behind each TV, taking 802.11af loads to power. For the TV with an AP or something else PoE behind it, those switches can take in 802.11at and output 802.11af on port 8. The TVs themselves aren’t PoE...I’m
3.
by Nick-Craver 7y ago
I’m very interested and very serious. Email sent.
4.
by Nick-Craver 7y ago
I don’t know. I am so very much trying to find out and push to make things better.
5.
by Nick-Craver 7y ago
I just wanted to chime in from Stack Overflow here and let people know: we are aware of the issue. And we're NOT okay with it. We're trying to sort out how to kill the audio behavior now. It's not very straightforward to find
6.
Stack Overflow: How We Do Monitoring – 2018 Edition(nickcraver.com)
3 points by Nick-Craver 8y ago|0 comments
7.
by Nick-Craver 9y ago
12,095,709 questions have an answer, 7,506,004 of those have an accepted answer, and 1,813,270 aren't yet answered. I'd say your 1:20 ratio is just a little bit off :)
8.
by Nick-Craver 9y ago
We could - but the network side isn't the problem. There's a lot of logging, user banning, etc. pieces that need IPv6 love first. We just haven't had the time yet. There are network bits we'd have to evaluate heavily as
9.
by Nick-Craver 9y ago
Split horizon would point you at the same data center, rather than the writeable one. So that's more of a .local than a .internal. We discussed this, but ultimately the AD version we're on (pre-2016 Geo-DNS) it's not actually
10.
by Nick-Craver 9y ago
Well, yes and no - it depends on the length. Let's take 3 common examples. Here's GitHub's relevant headers (that we don't have): Content-Security-Policy:default-src 'none'; base-uri 'self'; block-all
11.
by Nick-Craver 9y ago
Well if it wasn't for someone buying <star>.com back in the day, we probably could have them. Oh and then buying <star>.<star>.com after browsers banned that one, which led to RFC 6125 rule clarifications and restrict
12.
by Nick-Craver 9y ago
Yep - we're aware. I thought about putting in our Content-Security-Policy-Report-Only findings about what all would break, but the post was already a tad long. It's quite a long list of crazy things people do. As the headers go, h
13.
HTTPS on Stack Overflow: The End of a Long Road(nickcraver.com)
574 points by Nick-Craver 9y ago|174 comments
14.
by Nick-Craver 10y ago
If curious, I did a post on that a while back. I'm settling into a new house and will pick this series back up soon. https://nickcraver.com/blog/2016/02/17/stack-overflow-the-ar...
15.
by Nick-Craver 10y ago
Stack Overflow employee here. This is just my view, but: I wouldn't want to work for Google r Facebook over Stack Overflow. Happiness is part of the compensation and is has real value in choosing where to work. Would I make more dollar
16.
by Nick-Craver 10y ago
In the US at least (I can't speak for elsewhere), preventing this is illegal. Companies discourage it through various ways and it's practically an embedded culture thing at this point throughout the country. But: you cannot legall
17.
by Nick-Craver 10y ago
Correct. I'll be adding this functionality into Opserver so that we can override the health check in HAProxy when we know better.
18.
by Nick-Craver 10y ago
Correct. 10 minutes was from checkin to all servers built out, including a dev and staging tier.
19.
by Nick-Craver 10y ago
We have an internal tool where we can dump stack traces almost instantly by attaching to a running process. We can't open source it due to using Microsoft lab code which was never licensed itself. However, clrmd ( https://git
20.
by Nick-Craver 10y ago
Yep.
21.
by Nick-Craver 10y ago
Yep...for the on-premise reasons listed in the article. Once upon a time a lot of projects were on Mercurial, hosted by Kiln. The Stack Overflow repo specifically has always been on an internal Mercurial and then Git server. Originally this
22.
by Nick-Craver 10y ago
I don't believe your assessment is correct. I very specifically said built-in. This remains true. If curious, we're on CentOS 7 specifically. I didn't say there aren't any options, only that there aren't any bui
23.
by Nick-Craver 10y ago
> With the foreign key table, performance would suffer, but probably not enough to matter for most use cases. Citation needed :) That's going to really depend. I'm not for or against NoSQL (or any platform). Use what's b
24.
by Nick-Craver 10y ago
It only deploys to our development/CI environment automatically. Deploying out to the production tier is a button press still. So yes, it will build to dev, but we're using this in situations where we're very confident the
25.
by Nick-Craver 10y ago
If you did different tables, that's even more complicated by making every query dynamic. It also makes backups, etc. far more complicated as well. Multiple databases is simply the simplest solution for multiple things that need a dat
26.
by Nick-Craver 10y ago
If you mean pinbot - that's literally all it does. It takes a message and pins it, knocking the old one off the pins. The build messages build...that's also literally all it does. It simply puts handy notices in the chatroom. Wh
27.
by Nick-Craver 10y ago
Not that I think it's an invalid argument, but almost all of our outages have been either a database issue or (far more often) CloudFlare's inability to reach us (the origin) across the internet. Deploying code rapidly very, very
28.
by Nick-Craver 10y ago
Webhooks didn't used to work well for many builds off a single repo, but I think this changed very recently in TeamCity. Thanks for the reminder - I'll take another look this week at adding web hooks. We'd still want the
29.
by Nick-Craver 10y ago
Yeah! What's wi...wait, what?
30.
by Nick-Craver 10y ago
It's not for localhost, it's for the server name. While Gitlab and Teamcity normally are on the same box, they can operate on different boxes or in different data centers. It's looking up a DNS name which happens to point a

More ›