text stringlengths 0 1.8k |
|---|
**Adam Stacoviak:** This show is really bad at this point then, because we have problems with the show... |
**Jerod Santo:** Yeah. Everyone's trying to unsubscribe, we just won't let them. Like, when they hit Unsubscribe, it just errors out; they're like, "Dang it! I'll try again next time they email me." \[laughter\] No, these are all within hours of each other... So this is the same IP, same exact user agent, hitting the s... |
**Adam Stacoviak:** Send them through an infinite loop if they're a robot. Sent them to a -- crash their machine. |
**Jerod Santo:** \[48:00\] Okay. |
**Adam Stacoviak:** Instead of 404-ing it. That's too obvious. |
**Jerod Santo:** Whenever anybody tries to unsubscribe from Founders Talk we just crash their machine? |
**Adam Stacoviak:** Well, if they have this bot-like behavior, yeah. |
**Jerod Santo:** So now I need a throttling library... This is too much work for a troll. |
**Adam Stacoviak:** \[laughs\] |
**Gerhard Lazu:** No, because I think we can see details. In Sentry, if you click the links, by the way -- and I can't add it in the show notes, but we can see the IP address which it's coming from; we can see the Chrome version, and we can see that it's using Windows 10. So if you're trying to unsubscribe and you're a... |
**Adam Stacoviak:** I would recommend emailing editors@changelog.com and just saying "Please unsubscribe me manually." |
**Gerhard Lazu:** Yeah, that's a good one. |
**Jerod Santo:** This could be like a really MacGyver-style listener, who's like "I wanna unsubscribe. I realize they have a bug. I'm just gonna write a script that hits it every couple hours until it works, and then I'll be unsubscribed." Maybe that's what's going on here. |
**Gerhard Lazu:** Apparently there's like a single user, and it's been happening 695 times in the last four days. Someone is really persistent. |
**Adam Stacoviak:** What did we do to you? Gosh... |
**Gerhard Lazu:** But one thing which I've wanted to say is that Getsentry made it easy. We get those weekly emails, we can see whether the arrows are going up or down... They have some nice things. I don't go there that often, but they have a performance feature which we don't even use; that's an interesting one. Also... |
**Jerod Santo:** Yeah. What they don't do - and this is probably a config; I just haven't got it set up right - that Rollbar would do is the first time a new issue comes in, I would still get an email every time. And now with Sentry I get the weekly email, and I just don't get the "Hey, new error detected" email, which... |
**Adam Stacoviak:** I'm only getting the weekly updates... |
**Gerhard Lazu:** No, only the weekly ones. So one thing that I can see on this issue - it's on the right-hand side, just underneath the number of events - is ownership rules. Import GitHub or GitLab code owners files to automatically sign issues to the right people. Maybe that would help? I don't know. |
**Jerod Santo:** I don't know. I'll look into it more. Not interesting for this conversation, but just something that we have to figure out. I mean, we would be the owner -- just set yourself the owner of all new issues, maybe. And then maybe you'll get emailed. I don't know. |
**Adam Stacoviak:** What is odd too, at least in this last report, was that Monday through Friday was low errors. It was Saturday and Sunday that was the error dates... Which is the exact opposite of -- at least WebTraffic. I'm not sure about ListenTraffic, if they happen a lot more on weekends... But I would suspect t... |
**Gerhard Lazu:** Yeah. That is an interesting one. |
**Jerod Santo:** Well, the weekends, when you finally listen to that Founders Talk episode and you're like "I've gotta get off of this train..." \[laughter\] Unsubscribe, 695 times. I guess for the listeners' sake, Founders Talk is Adam's show. He does it all by himself, so we're picking on him at this point. |
**Gerhard Lazu:** Yes, we are. Sorry. That was a really bad. |
**Jerod Santo:** \[laughs\] |
**Gerhard Lazu:** I apologize. I apologize. |
**Jerod Santo:** It's a great podcast; you should totally subscribe, and I'm not saying that facetiously. |
**Gerhard Lazu:** You should, yes. |
**Jerod Santo:** Okay. |
**Gerhard Lazu:** So what happens next? Next steps between episode 20 and episode 30. What is the first thing that you would like to see happen, Jerod? Let's go around. Or Adam, if you have one already queued up... |
**Adam Stacoviak:** \[51:50\] Well, I know we've been talking about exploring more... I'm all about 1% improvements; I would say let's make progress on the front, not so much accomplish the front... But let's explore what it might be to consider something like Fly, considering their new hire recently, and their focus o... |
**Gerhard Lazu:** Yeah, that's a good one. So the person that Adam is talking about is Chris McCord, creator of the Phoenix framework. It's exactly what changelog.com the app is using... And he joined -- |
**Adam Stacoviak:** It was about two weeks ago, I think. |
**Gerhard Lazu:** So a few weeks ago he joined the Fly team; I think that's great. There's a big commitment from Fly to Phoenix to Elixir to this ecosystem, which makes us very excited, because our app is using exactly the same stack, so that's great. |
**Adam Stacoviak:** And I'll plug too, since we're dogging Founders Talk - I'll plug episode 80, with one of the co-founders and the CEO, Kurt Mackey, whom I think is a super-awesome dude. I think he's super-smart. He has great intentions, he's a developer at heart... He is a developer, obviously, but he's been iterati... |
**Gerhard Lazu:** In Ship It episode 18, in the show notes, there's a link to "Firecracker VMs on Metal, Oh, My!" This is Kurt Mackey's talk in March, earlier this year... |
**Adam Stacoviak:** At Proximity, yeah. |
**Gerhard Lazu:** The Proximity one. That was a really good talk. I've really, really enjoyed it... So if you wanna check it out -- that got me really excited about Fly and the infrastructure which they run... And I'm sure Kurt will be joining Ship It very soon. |
**Adam Stacoviak:** Yeah. I think we barely scratched the surface of the ideas he has, so I think he's due a conversation with you at a deeper level on the tech side. |
**Gerhard Lazu:** What about you, Jerod? Would you like to go next, your top thing? |
**Jerod Santo:** Well, it's time to get our uploads over to cloud, but that one's on me... On you, Gerhard - I wanna see that Honeycomb test out integration sometime here real soon, because I did enjoy what Charity had to say on your episode with her, and I think that it sounds like a good place to hop in and try out H... |
**Gerhard Lazu:** Yeah, that's actually a good one. So this is one of the problems that I've been having since episode ten. I've had so many great conversations on Ship It, and I want to try so many things, and I do a little bit of this and a little bit of that... |
**Jerod Santo:** Right. |
**Gerhard Lazu:** ...but nothing long enough to land it. And that's something which I would like to be doing more of. |
**Jerod Santo:** Focus. |
**Gerhard Lazu:** Yeah, exactly. But there's so many exciting things, like - I wanna try Fly, and I wanna try Honeycomb, and I do, and I set it up, and CockroachDB, and I've set things up... But I haven't taken it all the way. So that's something which I would like to get better at. |
So my top of the list - I really like what you've mentioned, Jerod and Adam, and I think this basically is more towards Adam... Is experimenting more, for sure; there is debugging the Kubernetes issue that we've been having since -- actually, since we've enabled Grafana Cloud and we've had more visibility into Ingress ... |
What we see - and this is, by the way, in a Rawkode livestream which is coming up, and it will be out, by the way, by the time you listen to this; I can add it to the show notes... It's that the tail latencies -- this is Ingress NGINX, our tail latencies to the app are really high. |
\[55:54\] So our 90th percentile - this is Ingress NGINX to Phoenix, to PostgreSQL, the request coming back to NGINX, the maximum 90th percentile is 286 milliseconds. It's fairly high, but it's okay, not that high. The 95th one is 841 milliseconds, so almost a second. So some requests can take almost a second to come b... |
**Adam Stacoviak:** Oh, my gosh... That's a long time, a minute... I mean, a full second is a long time. A minute is 60 times that. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.