text
stringlengths
9
408
[621.06 --> 621.74] My apologies.
[622.36 --> 627.00] And it's a very, very super simple, like, if you just create some text and then click save.
[627.28 --> 629.40] Oh, that's what I'm seeing.
[629.70 --> 630.48] Oh, my gosh.
[630.48 --> 634.20] It's a full screen, not a terminal per se, but it looks kind of like one.
[634.64 --> 635.70] This is just a write space.
[636.38 --> 636.98] It's neat.
[637.38 --> 642.40] You know, like, Docker containers come up with fake names if you don't name them, like Angry Torvalds or something.
[643.66 --> 644.02] Yeah.
[644.02 --> 646.48] It's funny my mind went to Angry Torvalds, isn't it?
[646.52 --> 646.86] It's funny.
[647.02 --> 647.42] Funny that.
[647.42 --> 656.74] So the one I've just created for you was termpad.com slash awful wide eyed napkin, which is a really strange, random generated name.
[656.84 --> 662.84] But it does code syntax highlighting as well, just for super simple, you know, paste bin stuff.
[663.00 --> 663.64] There's no database.
[663.90 --> 665.48] It's all just open.
[665.82 --> 668.90] So termpad.com is a hosted version, free.
[669.02 --> 670.50] I don't know what happens to the data on that one.
[670.72 --> 672.34] But you can self host it as well.
[672.34 --> 675.10] There is a container, which we'll put a link to in the show notes.
[675.10 --> 677.36] Kind of surprisingly useful.
[677.60 --> 678.02] I love it.
[678.60 --> 680.90] Okay, let's see if you are two for two here, Alex.
[680.98 --> 682.12] Tell me about TinyPin.
[682.52 --> 684.12] We're going to be redoing our bathroom soon.
[684.24 --> 687.40] So I was looking across Pinterest the other day and it's just garbage.
[687.54 --> 691.48] They make you sign in and do all this kind of nonsense about tracking what you're looking at.
[691.66 --> 695.96] And I mean, it's kind of okay from a discovery point of view, but it's also just garbage.
[696.72 --> 697.36] I hate Pinterest.
[697.36 --> 703.06] So I went on the look for something, you know, minimal to just share like a mood board almost.
[703.14 --> 704.42] And I came across TinyPin.
[704.72 --> 706.08] I'll put a link in the show notes, of course.
[706.36 --> 709.88] And this is a self hosted minimalistic image collection board.
[710.66 --> 711.40] Super simple.
[711.58 --> 715.06] You can run it in a container and there isn't a lot else to say.
[715.20 --> 718.72] It just does the job it's supposed to do, which I suppose is the praise that you want.
[719.20 --> 720.98] And it's nice to see that they have Chrome extensions.
[721.50 --> 725.78] And through iOS shortcuts, there's a way you could add it to your share sheet as well.
[725.78 --> 726.84] It seems that's handy.
[727.16 --> 732.16] I don't see necessarily something in here for Android, but there probably is a means if you can think it up.
[732.76 --> 743.54] I had a quick look at TinyPin just before the show and it is very minimal, but it does a good job of laying images out in different sizes in a very dynamically scalable way.
[743.60 --> 747.88] So you can have a tablet size, you can have a full web page version, or it can be on your phone.
[748.06 --> 753.44] And it actually manages to sort of present the images in a unique way while also letting you get in there at full screen.
[753.44 --> 756.20] So I kind of, I think this is a nice little find.
[756.26 --> 760.28] I don't quite grok how it's, okay, can you explain to me how it's sucking the images in and storing them?
[760.32 --> 761.88] Because that's the part I don't quite grok.
[762.18 --> 763.14] No, I'm not sure.
[764.02 --> 766.94] It stores in the backend, it stores stuff in a data directory.
[767.08 --> 769.10] So it's just a volume bind mount on the file system.
[769.36 --> 771.86] Nothing too crazy, no database needed or anything like that.
[772.14 --> 775.10] And you could go sniffing through there and back them up pretty easily if you needed to.
[775.26 --> 775.58] Mm-hmm.
[775.98 --> 777.10] Okay, well, we're two for two.
[777.18 --> 778.22] I think that's a pretty good find.
[778.34 --> 780.18] I think also the wifey would really love that one.
[780.26 --> 783.04] That'd be a good one to add to the home server to impress her, I think.
[783.70 --> 786.32] Now I want to see if you can be three for three on this one, Alex.
[786.42 --> 788.80] Tell me about OpenSense 21.1.
[789.16 --> 791.36] I vicariously OpenSense threw you.
[792.56 --> 797.00] Well, PFSense made a bit of a stink the other week by adding WireGuard support finally.
[797.56 --> 805.80] And not to be outdone, the OpenSense project released 21.1, which is nicknamed Marvelous Meerkat.
[806.20 --> 806.54] Hmm.
[806.54 --> 813.32] They say that it has new and improved firewall rules, NAT categories, better traffic graphs, all that kind of stuff.
[813.76 --> 819.44] And they have a really small dig in their release notes at PFSense, which I really enjoyed, which says,
[819.88 --> 828.00] for those wondering, the WireGuard plugin has been available on OpenSense since 2019 and receives continuous improvements by its maintainer.
[828.00 --> 830.34] And that feature is unlikely to change.
[830.34 --> 834.76] My eyes were immediately drawn to that in their release notes.
[835.58 --> 838.24] I didn't realize PFSense had added WireGuard, but this is really good now.
[838.32 --> 840.40] We have it in both OpenSense and PFSense.
[840.84 --> 842.92] Our WireGuard future has arrived.
[842.92 --> 848.92] I'm just sad that it didn't make it into in 2020 because my prediction was that PFSense would ship WireGuard.
[849.62 --> 853.20] But I guess those BSD guys just shit when they're ready.
[853.72 --> 855.52] No plans for you to go back, I assume?
[855.72 --> 858.32] You're going to stick with the old OpenSense, I would imagine?
[859.86 --> 861.58] OpenSense is kind of driving me crazy.
[861.82 --> 862.06] Oh.
[862.32 --> 863.18] There's a few reasons.
[863.64 --> 865.74] Mostly to do with WireGuard, if I'm honest.
[866.06 --> 867.92] I just think the implementation is...
[868.72 --> 870.48] Maybe it's user error.
[870.48 --> 886.22] Okay, I will fully admit that I am not a network guy, but I spent, from the hospital, at least two or three weeks for maybe half an hour to an hour at a time, most days, trying to get WireGuard fully working.
[886.54 --> 889.48] So I can connect in remotely just fine.
[890.00 --> 893.84] I can ping the firewall just fine.
[893.92 --> 896.34] I can connect to the web UI of the firewall itself just fine.
[896.58 --> 899.60] I can route traffic through my home internet connection just fine.
[899.60 --> 904.84] But I can't access any hosts on my LAN, which kind of defeats the purpose for me.
[904.92 --> 910.36] I mean, I don't necessarily really want to route my traffic through my house, but it's a nice benefit of WireGuard.
[910.60 --> 917.70] What I wanted was to be able to access Proxmox or ESXi remotely and continue rebuilding my servers, which I've been doing for the last couple of months.
[917.70 --> 925.40] And I've wasted, I don't even know how many hours, trying to make this effing thing work.
[925.52 --> 930.96] And I wrote the man page on WireGuard for OpenSense, and I feel like a fraud because I just can't make it work.
[932.36 --> 933.50] I wrote the book.
[933.72 --> 936.70] I'm convinced at this point that there is a bug that I can't find.
[936.70 --> 947.12] So I'm probably going to NukemPave my OpenSense install, which is, I don't want to do it, but I've wasted so much time and I'm convinced I've got all the firewall rules set up correctly.
[947.68 --> 949.54] I don't see that I'm left with any other option.
[950.30 --> 961.32] And so that then makes me think, well, if I'm going to NukemPave OpenSense, why don't I try ViOS or some other, I don't know, there's a million different options to try out there.
[961.32 --> 966.26] Or I could just go whole hog and run, you know, CentOS streams and IP tables.
[967.50 --> 969.42] Go full West Payne on it is what you could do there.
[969.56 --> 970.26] He does it home.
[971.00 --> 973.04] Yeah, that WireGuard routing issue is tricky.
[973.16 --> 976.38] He and I had to do some troubleshooting to get that working here at the studio.