text
stringlengths
9
408
[816.66 --> 819.26] Here is some suggested file sizes.
[819.42 --> 820.66] But you get none of that.
[820.98 --> 822.94] What you get is you upload a picture.
[823.14 --> 824.70] Turns out that picture is too large.
[825.12 --> 826.20] What's the appropriate size?
[827.22 --> 827.58] I don't know.
[827.80 --> 829.34] Just depends on what different people have set.
[829.52 --> 834.06] So, you know, take a good guess and then just find out it doesn't work and then go back
[834.06 --> 834.58] and fix it.
[834.90 --> 838.82] And it's just sort of this unrefined paper cutty experience.
[838.96 --> 840.96] And it's a thousand different examples of that.
[840.96 --> 849.02] And even with a team of moderators, Wes and myself, I still get I get looped into like daily
[849.02 --> 850.58] jobs to take care of.
[850.58 --> 853.30] And some I've been postponing now for weeks because I just don't have time.
[854.30 --> 858.56] Meanwhile, we have three different discord instances out there.
[858.56 --> 860.66] You know, the self-hosted one.
[860.74 --> 861.56] There's a JB one.
[861.62 --> 862.44] There's an unfiltered one.
[862.94 --> 867.68] And I probably I probably have to do two things a year with those instances.
[867.68 --> 867.98] Right.
[868.00 --> 868.84] I mean, the same thing there.
[868.90 --> 872.54] We have some community moderators and folks like yourself, Alex, that are involved.
[872.54 --> 878.72] But in terms of like my involvement, it's like two things a year for each instance, where
[878.72 --> 880.52] with Matrix, it's damn near daily.
[881.24 --> 884.06] And that really just doesn't scale very well.
[884.24 --> 889.64] And it clearly is an ongoing server maintenance task as well, because there's quite a bit of
[889.64 --> 894.24] storage that we're constantly compensating for because we have to store images and videos
[894.24 --> 898.76] and stuff that people upload and chat logs and all of that in storage or whatever it might
[898.76 --> 899.02] be.
[899.48 --> 901.66] The Synapse server itself is under frequent development.
[901.66 --> 903.74] So even like right now, I need an update.
[903.94 --> 905.44] I just updated it last week.
[905.68 --> 907.04] There's an update right now for it.
[907.32 --> 907.76] Right.
[907.96 --> 908.86] Not a big deal.
[909.08 --> 910.48] In fact, it's been really smooth.
[910.58 --> 911.74] It hasn't kicked out any problems.
[911.76 --> 913.52] And we have it all in Docker containers.
[913.52 --> 916.42] And the upgrade has always gone really well to its credit.
[916.60 --> 920.46] And there are server side tools to help minimize the database and whatnot.
[920.84 --> 924.94] But again, you have to go employ those tools yourself on the command line manually.
[925.84 --> 928.66] And it's just disheartening because.
[928.66 --> 932.00] As a self-hosting advocate.
[933.18 --> 937.04] It's so clear to me now that I've been running Matrix for a little while as an app server.
[937.84 --> 943.66] That it is exponentially simpler to just go the Discord or Slack route than it is the Matrix
[943.66 --> 944.00] route.
[944.00 --> 949.82] And when the core functionality of what you're looking for is just an ability for you and
[949.82 --> 951.12] your community to communicate.
[951.64 --> 955.96] It's so much simpler to use something else besides Matrix.
[956.24 --> 960.66] And I hate saying that because I want the free software new standard thing to win.
[960.78 --> 962.92] And I love that you can run your own and it's federated.
[962.92 --> 969.32] So I think what my advice would be for people out there that want to self-host a Matrix instance
[969.32 --> 976.42] is most of the time what you want is something small for your team that uses your domain name.
[976.72 --> 978.22] Don't open it up to the world.
[978.98 --> 983.62] For people that want to participate with you but don't yet have a Matrix account, have them
[983.62 --> 985.00] just sign up at Matrix.org.
[985.20 --> 986.34] That's what I should have done.
[986.34 --> 991.72] I should have set up a Matrix server with a small team, just the JB team, and then all
[991.72 --> 995.56] the rest of the community just went out and got Matrix.org or got accounts anywhere else
[995.56 --> 997.92] they wanted like they could already or their own Matrix server.
[999.60 --> 1002.80] Instead, we opened it up to the world because I wanted to make it easier for the audience.
[1002.94 --> 1008.70] And in doing so, we created something that has nearly daily maintenance tasks required.
[1010.40 --> 1013.26] I mean, just not everybody wants to sign up for that.
[1013.26 --> 1016.32] Thankfully, we are willing to participate in that because, again,
[1016.34 --> 1017.70] I think this is an important thing.
[1018.12 --> 1021.66] And I really think it's something like some projects could manage or companies could easily
[1021.66 --> 1022.04] manage.
[1022.16 --> 1024.34] And there are hosted solutions out there as well.
[1024.48 --> 1027.28] But I do regret the way we deployed it.
[1027.46 --> 1032.74] Looking back at it, the jupiterbroadcasting.com Matrix server should have just been for jupiterbroadcasting.com
[1032.74 --> 1033.22] staff.
[1033.64 --> 1038.58] And then we would just connect using the federation system and have everybody else participate.
[1038.58 --> 1043.40] Because we already have people from all different kinds of servers, their own, self-hosted,
[1043.40 --> 1046.54] or hosted, and they're participating in our chat room.
[1046.94 --> 1048.38] And I could have just done that for everything.
[1048.78 --> 1050.24] I'm not going to reverse course now.
[1050.62 --> 1052.96] And I still appreciate the ability to learn from it.
[1053.50 --> 1055.88] But I do have some regrets.
[1055.88 --> 1060.82] I think you just highlighted the exact reason why I went with Discord.
[1061.24 --> 1067.96] You know, it was a bit of a dictatorship-style decision that we took to say, right, this is
[1067.96 --> 1071.88] the self-hosted podcast, and yet we're going to make that compromise and go for Discord.
[1072.80 --> 1078.28] But I think you've just articulated very, very clearly that we made the right call with that
[1078.28 --> 1078.94] server, you know.
[1078.94 --> 1084.20] As I mentioned at the beginning of the show, we had an outage with some of our production
[1084.20 --> 1086.24] infrastructure that we used to make the shows this week.
[1086.54 --> 1090.58] And the last thing I really want to be doing is futzing around with that stuff when it's
[1090.58 --> 1092.74] not a planned situation.
[1093.14 --> 1095.14] You know, an outage or something like that.
[1095.22 --> 1101.66] And if JB's primary audience communication community platform for the show is down, shows
[1101.66 --> 1105.08] are down, then who's got to get out of bed and fix it?
[1105.18 --> 1105.92] You know, it'd be one of us.
[1105.92 --> 1108.60] You know, me, you, Wes, somebody like that, you know.
[1108.80 --> 1110.50] There's nobody else to do that work.
[1110.80 --> 1116.08] So I just, you know, at the end of the day, we are making podcasts.
[1116.28 --> 1119.30] We aren't necessarily system admins.
[1120.10 --> 1121.68] And it's just a compromise.
[1121.94 --> 1123.24] It's not a perfect situation.
[1123.24 --> 1124.80] And I think you've just hit the nail on the head.
[1125.34 --> 1132.84] But on a happier note, Linux Unplugged 4.33, you, Wes, and Brent covered Jellyfin.
[1132.84 --> 1135.88] And I'm sorry I couldn't make it that day.