text
stringlengths
9
408
[504.88 --> 509.06] And I was trying to do it all on like Juice SSH, trying to do all these, you know, extends
[509.06 --> 510.60] FS, blah, blah, blah, blah, blah.
[510.78 --> 515.04] And, you know, in the end, I sat down with a real keyboard at home and 15 minutes later,
[515.08 --> 516.06] the problem was solved.
[516.06 --> 518.56] But let that be a lesson, kids.
[518.66 --> 522.50] You've got to set up monitoring, alerting, but also monitor your monitoring.
[522.98 --> 528.66] Because if that ain't working, if your alerting isn't working, then you're going to get a
[528.66 --> 529.68] text from an angry Chris.
[530.36 --> 534.66] It's funny that like a couple of outages that we've talked about on the show, both were like
[534.66 --> 535.70] Google account related.
[536.08 --> 537.36] That's not lost on me.
[537.52 --> 538.40] That's kind of interesting.
[539.44 --> 544.14] But the other thing that I've been thinking is like, I wonder if we could convert the backend
[544.14 --> 546.04] storage for HedgeDoc to object storage.
[546.24 --> 548.74] That's what we've done with a couple of other things like NextCloud.
[549.34 --> 556.78] And the only downside is you got to watch your disk usage because it'll just grow and
[556.78 --> 558.24] grow and grow.
[558.64 --> 561.34] And the great thing is object storage will just grow and grow with it.
[561.40 --> 564.74] But you don't want it to get out of control because that could raise the cost.
[564.74 --> 568.58] So there's, but you know, we're talking markdown documents when it comes to HedgeDoc.
[569.34 --> 571.74] So you wonder there a little bit, but yeah.
[571.82 --> 574.14] And, and we do kind of take note.
[574.22 --> 574.60] Oh, okay.
[574.66 --> 574.86] Yep.
[574.86 --> 576.98] That's one more thing we need to add to the monitoring setup.
[577.12 --> 577.38] Okay.
[577.52 --> 577.70] Yeah.
[577.70 --> 578.64] We missed that one.
[580.94 --> 584.92] And, you know, we were, we were able to actually scramble and just use the public instance
[584.92 --> 585.42] of HedgeDoc.
[585.52 --> 589.22] I realized like, well, I guess, I guess I could go use that.
[589.22 --> 594.26] Uh, and by the way, if you're not using HedgeDoc and you, you like the collaborative editing
[594.26 --> 599.58] features of Google Docs, but like something that does markdown, man, as a team, do we just
[599.58 --> 600.60] use the crap out of this?
[600.60 --> 601.60] It's so solid as well.
[601.80 --> 603.28] I mean, there was nothing wrong with the app.
[603.32 --> 604.34] It was just out of disk space.
[604.98 --> 605.34] Yeah.
[606.42 --> 608.12] I have been on the other side.
[608.24 --> 610.66] I haven't really had an outage so much.
[610.84 --> 611.86] You know, I mean, you could chalk this up.
[611.88 --> 614.72] This is truly maybe a bit of self-hosting regret.
[614.72 --> 620.06] Like out of all the things I've self-hosted recently, I pretty much feel like they were
[620.06 --> 624.52] all a solid decision except for matrix, specifically the synapse server.
[625.60 --> 635.40] And I think that if I was just setting up a matrix server for the JB team or like my family
[635.40 --> 640.80] or friends or a small project, it would be problem free.
[640.90 --> 644.70] Practically, man, it'd be really easy, but that's not what I did.
[644.72 --> 651.72] I set up with, of course, the help of Wes, a matrix server for the Jupyter Broadcasting
[651.72 --> 654.66] community at colony.jupyterbroadcasting.com.
[655.52 --> 661.00] So matrix is this new open source implementation of.
[662.14 --> 666.84] Well, gosh, it's it's hard to explain because matrix itself is not a chat.
[667.00 --> 669.82] It has chat clients like we have web clients, right?
[669.84 --> 672.66] So there's element, which is a matrix client.
[672.66 --> 676.60] And in the element matrix client, it's a lot like Discord or Slack.
[677.26 --> 683.18] It's if you're familiar with those kinds of group chats or IRC of days gone.
[684.16 --> 689.12] But a little more a little more modern with a lot of the inline chat features that people
[689.12 --> 689.62] expect.
[689.90 --> 694.06] And on top of that, there's other features like VoIP calling and file transfer and all
[694.06 --> 694.52] kinds of things.
[694.60 --> 697.26] Matrix itself is a protocol with a series of functionalities.
[697.92 --> 700.28] I mean, it's big thing, though, isn't it, is that it's decentralized.
[700.28 --> 700.72] Yes.
[701.84 --> 702.60] And it's federated.
[702.82 --> 704.62] So there's a matrix.org server.
[704.92 --> 707.60] We have a colony.jupyterbroadcasting.com server.
[707.70 --> 708.82] There's a Fedora server.
[708.94 --> 710.10] There's a GNOME server.
[710.46 --> 714.94] Much like you'd have your own IRC server, you can run your own matrix server, much like
[714.94 --> 716.54] we have a Discord server, right?
[716.60 --> 720.84] But that Discord server runs on Discord systems and it's managed by Discord.
[721.30 --> 726.34] The difference with matrix is you get all that Discord like functionality, but you host
[726.34 --> 727.60] it, you run it.
[728.32 --> 728.74] But.
[730.28 --> 736.66] A federated chat system like this is no small task because it has to be aware of what the
[736.66 --> 737.96] rest of the federation is doing.
[738.30 --> 741.32] You have to have user accounts that can exist on both systems.
[741.74 --> 746.76] And what ends up getting exposed is a lot of paper cuts for managing the system.
[746.82 --> 748.66] Like, here's an example of just what happened this morning.
[748.78 --> 749.30] And this isn't.
[751.14 --> 752.30] This isn't a big deal.
[753.12 --> 753.52] Right.
[753.52 --> 754.84] But this is just what happened this morning.
[755.22 --> 761.58] I got a message saying, hey, Chris, I noticed that the logo image, the PNG that you're using
[761.58 --> 762.66] for your matrix space.
[762.66 --> 765.86] It's too large for some servers.
[766.34 --> 773.16] And so we're getting reports that your logo isn't displaying for a fair amount of users.
[773.16 --> 779.42] And, you know, that's like, oh, OK, well, I guess I'll upload a smaller image.
[779.42 --> 779.72] Right.
[779.72 --> 782.06] But there's really no standard there.
[782.26 --> 784.12] Different clients have been different restrictions.
[784.34 --> 785.98] Servers have different restrictions.
[787.20 --> 787.40] And.
[787.40 --> 792.88] It's a great example of a daily little task you have to do, like some little small tweak
[792.88 --> 795.80] or adjustment to participate in the wider matrix community.
[796.60 --> 798.42] The problem should just be handled by software.
[798.66 --> 804.98] Like I should be able to upload a five megabyte PNG and server side software resizes it.
[805.04 --> 809.32] And maybe it resizes it into three different sizes that are common sizes.
[809.32 --> 809.70] Right.
[809.76 --> 816.08] Like or it says it kicks back an air message on the client and it says, hey, man, upload a
[816.08 --> 816.66] smaller picture.