WEBVTT NOTE This file was generated by Descript 00:00:00.450 --> 00:00:00.990 Alan: So, hello. 00:00:01.020 --> 00:00:01.690 Hey, how's it going? 00:00:02.120 --> 00:00:02.500 Mario: hey! 00:00:03.090 --> 00:00:04.410 Today is one of those days. 00:00:04.445 --> 00:00:04.865 Alan: One of those 00:00:04.865 --> 00:00:05.107 days? 00:00:05.107 --> 00:00:05.348 Yeah. 00:00:05.590 --> 00:00:05.832 I know. 00:00:05.832 --> 00:00:06.315 oh man. 00:00:06.315 --> 00:00:06.795 Mario: Yeah. 00:00:06.885 --> 00:00:08.355 Today is been, 00:00:08.355 --> 00:00:10.527 This whole week has been a frustrating week. 00:00:10.617 --> 00:00:11.247 Actually. 00:00:11.247 --> 00:00:12.897 We have a lot going on around 00:00:12.897 --> 00:00:13.377 here. 00:00:13.435 --> 00:00:17.954 My wife and I have some plumbing issues at our place and 00:00:17.936 --> 00:00:18.232 Alan: the word? 00:00:18.232 --> 00:00:19.102 Plumbing is the worst. 00:00:19.102 --> 00:00:19.552 Like 00:00:19.582 --> 00:00:20.182 electricity. 00:00:20.182 --> 00:00:21.292 You're like, oh, we haven't got light. 00:00:21.322 --> 00:00:22.072 Water is 00:00:22.072 --> 00:00:22.852 like a nightmare. 00:00:23.092 --> 00:00:23.572 Mario: Yeah. 00:00:23.722 --> 00:00:24.292 Yeah. 00:00:24.532 --> 00:00:25.062 So we 00:00:25.062 --> 00:00:25.962 we had a 00:00:25.972 --> 00:00:32.081 leak from one of our bathrooms upstairs and they came and they fixed. 00:00:32.081 --> 00:00:36.281 They found that there were two different problems and they fixed a one of them. 00:00:36.261 --> 00:00:40.778 The simpler one, and then they found the other one that's more complicated. 00:00:41.708 --> 00:00:43.328 So they haven't fixed that one yet. 00:00:43.358 --> 00:00:47.908 Meanwhile, we can't use all of the bathroom upstairs. 00:00:47.938 --> 00:00:50.278 Luckily we have another bathroom downstairs. 00:00:51.055 --> 00:00:57.265 and so the reason It's taking forever is because they found asbestos in 00:00:57.475 --> 00:00:58.355 Oh, no. 00:00:58.355 --> 00:00:58.795 in 00:00:58.838 --> 00:01:03.548 Mario: the dry wall in the area that they need to access to fix the plumbing issue. 00:01:04.208 --> 00:01:05.078 So, and that is. 00:01:05.338 --> 00:01:07.168 Alan: to a standstill until they can deal with that, 00:01:07.168 --> 00:01:07.408 right? 00:01:07.443 --> 00:01:08.223 Mario: Exactly. 00:01:08.223 --> 00:01:08.913 So 00:01:09.183 --> 00:01:10.773 this, this home was built in 00:01:10.773 --> 00:01:12.393 the seventies, I think. 00:01:12.393 --> 00:01:16.593 So it has some as, 00:01:16.593 --> 00:01:17.203 Alan: throw asbestos on 00:01:17.228 --> 00:01:17.588 everything 00:01:17.733 --> 00:01:18.633 Mario: Yeah. 00:01:18.693 --> 00:01:19.113 Yeah. 00:01:19.113 --> 00:01:20.853 So, so the 00:01:21.063 --> 00:01:26.553 area they need to access is downstairs in the ceiling below, 00:01:27.183 --> 00:01:31.083 you know, where the bathroom is upstairs and it's a utility closet. 00:01:31.083 --> 00:01:33.083 So luckily is pretty isolated. 00:01:33.263 --> 00:01:38.153 You know, it's inside a utility closet where we have the water heater and, and 00:01:38.204 --> 00:01:40.804 there's a central air unit there as well. 00:01:41.464 --> 00:01:45.882 And so we're waiting for just got word today that they are going to be 00:01:45.882 --> 00:01:50.442 here tomorrow to continue because the test results came back and, you know, 00:01:50.452 --> 00:01:53.502 they have, now they know what they're dealing with and they're going to come 00:01:53.502 --> 00:01:56.892 in and, and start the abatement process. 00:01:57.522 --> 00:01:58.512 So we're dealing with that. 00:01:58.512 --> 00:02:02.657 And then at the same time we're reconfiguring some rooms in the house. 00:02:02.657 --> 00:02:06.947 My wife is setting up her office space somewhere else. 00:02:06.947 --> 00:02:10.337 So we've moved furniture and all kinds of stuff around and 00:02:10.637 --> 00:02:12.077 everything is upside down. 00:02:12.077 --> 00:02:12.527 It's like, 00:02:14.797 --> 00:02:16.627 Alan: I know that feeling well, and I hate it. 00:02:16.787 --> 00:02:17.627 Mario: yeah. 00:02:18.047 --> 00:02:18.167 And 00:02:18.307 --> 00:02:22.147 Alan: It makes you appreciate the, when things are back to normal again, so, 00:02:22.147 --> 00:02:22.687 much more though, 00:02:23.037 --> 00:02:23.547 Mario: yeah. 00:02:23.607 --> 00:02:24.207 Yeah. 00:02:24.237 --> 00:02:29.140 And as part of that process, we sold this huge cabinet that we had, you 00:02:29.140 --> 00:02:33.120 know, kinda like a dresser, you know, for clothes and stuff, but it was 00:02:33.120 --> 00:02:35.510 like pretty big and it was too big. 00:02:35.530 --> 00:02:39.710 We've been wanting to get rid of it for a long time and we finally sold it online. 00:02:40.640 --> 00:02:43.833 And that means all of the, all of our stuff that was there 00:02:43.833 --> 00:02:46.173 now is everywhere is out. 00:02:46.173 --> 00:02:48.043 And we're in transition. 00:02:48.073 --> 00:02:50.537 We're buying a smaller piece of furniture. 00:02:50.837 --> 00:02:51.377 Alan: Well, you don't have 00:02:51.377 --> 00:02:51.467 it 00:02:51.622 --> 00:02:52.612 Mario: But we don't have it yet. 00:02:52.612 --> 00:02:54.802 So everything is like, so everything is a 00:02:54.802 --> 00:02:55.222 mess. 00:02:55.222 --> 00:02:56.512 The whole house is a mess. 00:02:58.217 --> 00:03:02.267 Alan: It's it has a, like a big effect on your, just your mental balance. 00:03:02.297 --> 00:03:03.317 It's like, oh God, 00:03:03.782 --> 00:03:04.592 Mario: It does. 00:03:04.757 --> 00:03:05.417 Alan: I just go into my 00:03:05.417 --> 00:03:05.927 laptop. 00:03:06.557 --> 00:03:07.517 It's calmer in there. 00:03:07.517 --> 00:03:07.757 Right. 00:03:08.002 --> 00:03:08.572 Mario: Yeah, 00:03:08.747 --> 00:03:09.437 Alan: maybe it's not, 00:03:09.652 --> 00:03:09.922 Mario: is. 00:03:09.952 --> 00:03:11.272 And see, that's the thing. 00:03:11.322 --> 00:03:11.880 That's on the 00:03:12.000 --> 00:03:16.790 personal end of things, but also on the work side of things, I'm dealing 00:03:16.790 --> 00:03:19.363 with this issue with fusion cast that 00:03:19.363 --> 00:03:21.643 I'm, I still haven't been able to resolve. 00:03:21.673 --> 00:03:25.270 And so even that's not going the way I want it to go. 00:03:26.435 --> 00:03:29.555 Alan: but you don't even have the luxury of going away, going out to the house 00:03:29.585 --> 00:03:31.205 to work and leave the mess behind. 00:03:31.205 --> 00:03:31.355 Right. 00:03:31.355 --> 00:03:31.475 It's 00:03:31.650 --> 00:03:33.450 Mario: No, it's it's right here. 00:03:33.480 --> 00:03:34.350 I'm surrounded by 00:03:34.350 --> 00:03:34.470 it. 00:03:34.470 --> 00:03:35.850 As we speak, everything is a 00:03:35.850 --> 00:03:36.300 mess. 00:03:36.755 --> 00:03:38.315 Alan: I know it well, and it's no 00:03:38.315 --> 00:03:38.525 fun. 00:03:38.730 --> 00:03:39.360 Mario: Yeah. 00:03:39.630 --> 00:03:40.020 Yeah. 00:03:40.055 --> 00:03:40.835 Alan: have my sympathy. 00:03:41.180 --> 00:03:41.560 Mario: Thank you. 00:03:42.960 --> 00:03:44.790 yeah, so this recording issue. 00:03:44.990 --> 00:03:51.110 The recording itself is working, but the problem is with one of the features 00:03:51.110 --> 00:03:55.459 that I introduced, which I, I should have done before from the beginning 00:03:55.471 --> 00:04:00.117 which is remote controlled recording, where the host has control of recording. 00:04:00.777 --> 00:04:05.325 And when the host clicks record, then everyone, everyone in the session 00:04:05.325 --> 00:04:09.825 starts recording automatically remotely, You know, after all, this is a remote 00:04:09.825 --> 00:04:10.980 recording tool, so 00:04:10.980 --> 00:04:11.365 Yeah. 00:04:11.415 --> 00:04:12.105 Mario: have that. 00:04:12.816 --> 00:04:13.296 And 00:04:13.321 --> 00:04:18.883 I introduced that feature and it was working perfectly on my dev environment. 00:04:18.863 --> 00:04:23.194 Then I pushed it to production and it doesn't work there for some reason. 00:04:23.224 --> 00:04:25.684 And I don't understand why there are no errors. 00:04:26.134 --> 00:04:29.434 There's nothing, you know, it's just, it just doesn't do it. 00:04:29.498 --> 00:04:35.069 So it's one of those, and I've been in contact with a certain cloud 00:04:35.069 --> 00:04:39.517 provider that should go without mention th no, they've been great. 00:04:39.517 --> 00:04:41.347 They've been pretty supportive support. 00:04:41.347 --> 00:04:41.977 Hasn't been great. 00:04:41.977 --> 00:04:43.777 The only thing is that, that it takes forever. 00:04:43.777 --> 00:04:48.337 The turnaround time is, you know, I send a message and then I have 00:04:48.337 --> 00:04:54.127 to wait around 20, about 24 hours, you know, before I hear back from them. 00:04:54.877 --> 00:04:55.597 And then. 00:04:55.777 --> 00:04:59.167 Alan: what you're using for basically pushing messages to, from 00:04:59.437 --> 00:05:00.697 the server to the client, right. 00:05:00.727 --> 00:05:01.987 In order to get it to do 00:05:01.987 --> 00:05:02.377 something 00:05:02.422 --> 00:05:03.082 Mario: Yeah. 00:05:03.112 --> 00:05:03.352 Yeah. 00:05:03.352 --> 00:05:06.253 So I'm using a couple of different services for that. 00:05:06.302 --> 00:05:10.202 One of them is that one that we've talked about before and 00:05:10.532 --> 00:05:11.942 that, that seems to, be working. 00:05:11.942 --> 00:05:12.302 Okay. 00:05:12.302 --> 00:05:17.896 But the other one is it's a different kind of API that sends more they're more 00:05:17.896 --> 00:05:24.796 like a UDP type messages, you know, so client to client, kind of thing, no TCP. 00:05:25.006 --> 00:05:26.254 So it's more more 00:05:26.254 --> 00:05:28.984 performant, but the 00:05:28.984 --> 00:05:33.184 Mario: nature of that is that there's no guarantee that it's going to be received. 00:05:33.904 --> 00:05:36.483 So it's like UDP, like you know, 00:05:37.048 --> 00:05:37.288 Alan: Yeah. 00:05:37.309 --> 00:05:39.872 Mario: Protocol messages and 00:05:39.897 --> 00:05:44.905 I don't know quite yet, if that's even the problem, you know, if it's something 00:05:44.905 --> 00:05:47.185 to do with UDP or anything like that 00:05:47.585 --> 00:05:53.165 . So one thing that has been hindering my progress in troubleshooting 00:05:53.165 --> 00:05:56.789 this, is the fact that I don't have up until this point, I don't 00:05:56.789 --> 00:05:58.829 have a working staging environment. 00:05:58.919 --> 00:06:01.889 I just have my dev environment and production. 00:06:02.429 --> 00:06:07.769 And so it kind of, there's certain things that I can't freely do because 00:06:07.769 --> 00:06:09.449 I don't want to break production. 00:06:09.929 --> 00:06:13.889 So I've the past couple of days I've been working on setting 00:06:13.889 --> 00:06:17.662 up a proper staging environment replicating my production environment. 00:06:17.696 --> 00:06:21.669 And that way I can test all kinds of things without fear of breaking 00:06:21.669 --> 00:06:27.219 anything, and I can enable console log and I can enable all kinds of logs and 00:06:27.219 --> 00:06:29.829 I'm not having to be in production. 00:06:30.064 --> 00:06:30.794 Alan: yeah, exactly. 00:06:30.794 --> 00:06:31.904 And just breaking other 00:06:31.904 --> 00:06:32.294 people's 00:06:32.304 --> 00:06:34.794 Mario: Or exposing, you know, logs or 00:06:34.794 --> 00:06:37.014 exposing sensitive information. 00:06:37.014 --> 00:06:43.224 so I'm almost at the end of setting up this staging environment and it's 00:06:43.224 --> 00:06:46.404 time consuming because, you know, I have to set up with all these 00:06:46.434 --> 00:06:49.324 different services and APIs that I 00:06:49.347 --> 00:06:50.179 use, you know? 00:06:50.414 --> 00:06:50.864 Alan: It's not. 00:06:50.864 --> 00:06:54.284 So it's not so much just that you need to get your software deployed. 00:06:54.284 --> 00:06:58.004 It's that you're relying on other API APIs that all need to be up and running, 00:06:58.259 --> 00:06:59.009 Mario: Yeah, yeah. 00:06:59.039 --> 00:07:00.059 So I have to create 00:07:00.509 --> 00:07:05.285 the staging projects, so to speak in each of these services. 00:07:05.315 --> 00:07:05.645 right? 00:07:05.646 --> 00:07:06.216 So, 00:07:07.206 --> 00:07:12.807 and I have to make sure that I faithfully recreate what I have in production, and 00:07:12.932 --> 00:07:15.632 Alan: The worst, the worst thing's going to be, if it works finally staging 00:07:16.747 --> 00:07:17.307 Mario: I know 00:07:17.507 --> 00:07:17.667 that. 00:07:18.932 --> 00:07:19.472 Alan: you're like, oh, 00:07:19.502 --> 00:07:19.802 okay. 00:07:19.982 --> 00:07:22.172 Mario: Yeah, but at least, yeah. 00:07:22.232 --> 00:07:22.832 I don't know. 00:07:22.912 --> 00:07:23.552 Hopefully 00:07:23.582 --> 00:07:23.942 Alan: hope that's 00:07:24.182 --> 00:07:25.892 Mario: I think that's not the case. 00:07:25.922 --> 00:07:27.332 I, you know, it should not 00:07:27.332 --> 00:07:32.912 work and I should be able to see logs and things like that, or enable logs 00:07:32.912 --> 00:07:34.952 and things like that to, to trace it. 00:07:34.991 --> 00:07:37.241 Alan: Of those things that you had that you needed to do this 00:07:37.331 --> 00:07:40.181 eventually, but you'd rather have not had done it right now. 00:07:40.431 --> 00:07:41.091 Mario: Yeah. 00:07:41.151 --> 00:07:41.721 yeah. 00:07:42.531 --> 00:07:43.161 So, 00:07:43.243 --> 00:07:49.384 this thing it's part of the same process that allows me to show if you notice 00:07:49.384 --> 00:07:55.114 now I have indicators that tell you if anybody's mic is muted or the camera's 00:07:55.114 --> 00:07:56.654 turned off or anything like that. 00:07:57.014 --> 00:07:58.304 And so those are 00:07:58.378 --> 00:08:03.118 Messages going across that everyone receives and their 00:08:03.118 --> 00:08:04.888 UI gets updated accordingly. 00:08:04.888 --> 00:08:09.178 And so that same mechanism drives the remote controlled recording. 00:08:09.313 --> 00:08:09.913 Alan: are working. 00:08:09.913 --> 00:08:11.223 Mario: So, it works 00:08:11.253 --> 00:08:15.393 partially the, I mean, the, see here, if I disabled my camera, 00:08:15.393 --> 00:08:15.723 Alan: Okay. 00:08:15.723 --> 00:08:16.143 Yeah, that 00:08:16.278 --> 00:08:19.578 Mario: do you see a little red icon now that works. 00:08:19.578 --> 00:08:20.388 fine, but 00:08:20.388 --> 00:08:22.368 for some reason That part is working. 00:08:22.398 --> 00:08:26.014 But if I enable the remote control recording which 00:08:26.014 --> 00:08:27.514 actually did it through a flag. 00:08:27.514 --> 00:08:31.804 So there a flag now in the podcast that you can turn on or off. 00:08:31.804 --> 00:08:34.354 So right now I turned it off so that we can record. 00:08:34.714 --> 00:08:38.744 So when that flag is on only, I have a record button as a host. 00:08:39.074 --> 00:08:41.654 You as a guest, wouldn't see a record button. 00:08:42.104 --> 00:08:47.170 And but turning that flag off, puts everything back the way it was with 00:08:47.440 --> 00:08:49.300 you having a record button as well. 00:08:49.750 --> 00:08:56.930 And and so when that flag is on in, and the host controls, controls recording, if 00:08:56.930 --> 00:09:02.150 I hit record, then that same mechanism, that's sending data that updates, the 00:09:02.150 --> 00:09:07.640 UI also sends a signal for you to start recording every participant in the session 00:09:07.640 --> 00:09:08.420 starts recording. 00:09:08.420 --> 00:09:10.400 And for some reason that part is not working. 00:09:10.400 --> 00:09:11.120 so it's, I 00:09:11.120 --> 00:09:11.270 don't 00:09:11.355 --> 00:09:12.105 Alan: That's frustrating. 00:09:12.225 --> 00:09:14.025 So Yeah, the, you need to know if it's getting the 00:09:14.025 --> 00:09:17.625 message and if it's is getting the message, why isn't it starting? 00:09:17.625 --> 00:09:19.395 And if it isn't then why not? 00:09:19.690 --> 00:09:20.350 Mario: Exactly. 00:09:20.655 --> 00:09:20.925 Alan: it's 00:09:20.985 --> 00:09:21.185 yeah. 00:09:21.185 --> 00:09:22.725 You don't want to do that in production because you're 00:09:22.725 --> 00:09:24.255 filling around with logs and 00:09:24.345 --> 00:09:24.585 Yeah. 00:09:24.700 --> 00:09:25.120 Mario: Yeah. 00:09:25.150 --> 00:09:26.350 And, the reason I 00:09:26.350 --> 00:09:26.980 found out about it. 00:09:27.285 --> 00:09:31.673 was because one of the people that I onboarded a little while back 00:09:31.673 --> 00:09:36.503 actually used the fusion cast to record, and he ran into some problems 00:09:36.833 --> 00:09:41.403 I'm trying to record, but luckily he noticed that backup recording was on. 00:09:41.403 --> 00:09:46.173 So he was, he still went on and recorded an episode with guests. 00:09:46.233 --> 00:09:49.625 And you know, I'm assuming he knew that backup recording was on. 00:09:49.625 --> 00:09:52.750 So he took his chances and still did it. 00:09:52.759 --> 00:09:56.583 There was no local recording for anybody else, but himself, but 00:09:56.583 --> 00:09:57.783 back our recording was there. 00:09:58.083 --> 00:10:00.453 and so he messaged me later and asked me 00:10:00.453 --> 00:10:02.193 if I could give him the backups. 00:10:02.221 --> 00:10:04.498 And so I did everything was there, 00:10:04.551 --> 00:10:06.141 Alan: I mean, that's good to know as well. 00:10:06.141 --> 00:10:06.381 Right. 00:10:06.481 --> 00:10:07.681 Mario: yeah, yeah, 00:10:08.341 --> 00:10:08.661 yeah. 00:10:08.751 --> 00:10:10.971 Alan: that there is the backup facility and there is 00:10:10.971 --> 00:10:11.361 the, you know, 00:10:11.441 --> 00:10:12.561 that, that recording is there. 00:10:12.561 --> 00:10:13.169 So but 00:10:13.169 --> 00:10:16.019 that, that hopefully, you know, it gives him confidence that, oh, okay. 00:10:16.049 --> 00:10:19.589 Even if things do go wrong, then that's still, you know, that works 00:10:19.589 --> 00:10:19.829 fine. 00:10:19.924 --> 00:10:20.704 Mario: exactly. 00:10:20.764 --> 00:10:25.014 So, so I was able to provide the backups to him and you know, I 00:10:25.014 --> 00:10:29.034 apologized and I, you know, told him I'm, I'm looking into it. 00:10:29.664 --> 00:10:34.014 And I said, hopefully that the rest of the experience wasn't too bad. 00:10:34.014 --> 00:10:36.384 And he said, no, it was great that we actually 00:10:36.384 --> 00:10:36.834 enjoyed it. 00:10:36.834 --> 00:10:41.634 So, so hopefully, you know, that didn't leave a bad flavor, but 00:10:41.614 --> 00:10:46.021 Alan: Well, it's better to find it out now with one person then later with a hundred, 00:10:46.021 --> 00:10:46.261 right. 00:10:46.436 --> 00:10:46.706 Mario: Yeah. 00:10:46.736 --> 00:10:47.516 Very true. 00:10:48.296 --> 00:10:49.016 Alan: Get to the bottom of it. 00:10:49.016 --> 00:10:50.306 Once you got staging up. 00:10:50.396 --> 00:10:52.256 I'm sure it will be one of those obvious 00:10:52.256 --> 00:10:53.996 things that it's like a one character to fix. 00:10:53.996 --> 00:10:54.566 And you'd be like 00:10:54.896 --> 00:10:55.376 all of that. 00:10:57.091 --> 00:10:57.751 Mario: maybe. 00:10:57.751 --> 00:10:58.111 Yeah. 00:10:58.406 --> 00:10:58.736 Alan: I hope 00:10:58.736 --> 00:10:58.976 so. 00:10:59.136 --> 00:11:00.456 Mario: yeah, I hope so, too. 00:11:01.146 --> 00:11:01.356 So. 00:11:01.356 --> 00:11:05.299 after that, I I sent that email to everyone that I have onboarded 00:11:05.329 --> 00:11:06.829 just to give them a heads up. 00:11:07.339 --> 00:11:09.079 And I'm sure you received that email. 00:11:09.084 --> 00:11:09.414 Alan: Yes. 00:11:09.564 --> 00:11:11.874 I was going to say it might be worth clarifying. 00:11:11.874 --> 00:11:14.994 Cause my takeaway with that was our, I can't do local recording. 00:11:15.048 --> 00:11:18.528 Rather than just say, you know, like the, the auto 00:11:18.528 --> 00:11:20.238 recording, just to clarify the 00:11:20.238 --> 00:11:21.678 ultra recording isn't working. 00:11:22.458 --> 00:11:22.938 So 00:11:22.968 --> 00:11:23.408 yeah, 00:11:24.583 --> 00:11:24.943 Mario: I guess. 00:11:24.943 --> 00:11:26.713 Yeah, that's a good, that's a good suggestion. 00:11:26.713 --> 00:11:31.333 I wasn't sure how to handle that because that's a new feature 00:11:31.333 --> 00:11:33.403 that people didn't know about. 00:11:33.403 --> 00:11:37.093 And so I didn't want to convolute the message with, you know, there's 00:11:37.093 --> 00:11:38.773 new features and this and that. 00:11:39.193 --> 00:11:44.482 So I just wanted to keep it kind of straight, but cause I was looking forward 00:11:44.482 --> 00:11:48.802 to sending this email with an update of all the features that I've been working. 00:11:48.802 --> 00:11:52.282 on and all the changes that I've put in based on the feedback that I 00:11:52.282 --> 00:11:54.712 received and then this thing happened. 00:11:54.712 --> 00:11:57.832 And So now I have to deal with this and I, I feel like 00:11:57.832 --> 00:12:03.442 I can't send an update about new features when this thing is not 00:12:03.442 --> 00:12:03.892 working 00:12:03.977 --> 00:12:06.557 Alan: Fundamental basic is kind of having an issue, right? 00:12:06.557 --> 00:12:06.937 Yeah, yeah, 00:12:06.972 --> 00:12:07.542 Mario: Yeah. 00:12:07.542 --> 00:12:09.758 so it's like, kind of frustrating, but. 00:12:10.363 --> 00:12:10.603 Alan: Yeah. 00:12:10.603 --> 00:12:11.803 I it's strange that you said it 00:12:11.803 --> 00:12:12.493 works locally. 00:12:12.493 --> 00:12:13.663 I mean, is it possible 00:12:13.663 --> 00:12:15.463 it's some just permission issue because 00:12:15.463 --> 00:12:17.173 it's accessing camera and microphones. 00:12:17.173 --> 00:12:19.693 So if it may be trying to do 00:12:19.693 --> 00:12:23.323 that, programmatically is just, you know, causing some, 00:12:23.853 --> 00:12:24.993 Mario: It could be. 00:12:25.363 --> 00:12:25.963 Alan: permission issue. 00:12:25.993 --> 00:12:29.448 It sounds like it's me, if it's it's one thing that would probably be my first 00:12:29.448 --> 00:12:30.738 thing I look to is just the fact that 00:12:30.738 --> 00:12:33.822 it's it, it is a permissions, you know, like the fact that the 00:12:33.822 --> 00:12:38.052 browser is triggering the camera without a user interaction. 00:12:38.052 --> 00:12:38.322 Right. 00:12:38.352 --> 00:12:41.736 So programmatically triggering the camera or microphone could 00:12:41.736 --> 00:12:42.936 be something to do with that. 00:12:43.136 --> 00:12:47.040 That that's, that would just be my, I I've never used this stuff, so I'd have no no 00:12:47.040 --> 00:12:48.900 idea, but that would be the, the thing 00:12:48.900 --> 00:12:52.530 which would make me think there's an issue, especially since it works locally. 00:12:53.250 --> 00:12:57.330 Mario: yeah, yeah, That was the only thing is by, by then. 00:12:57.330 --> 00:12:59.580 Camera's already given permission. 00:12:59.572 --> 00:13:03.187 Microphone is already, you know, it's already going and 00:13:03.312 --> 00:13:03.612 Alan: going 00:13:03.612 --> 00:13:03.912 great. 00:13:03.912 --> 00:13:04.332 But yeah. 00:13:04.332 --> 00:13:07.092 I'm wondering if there's some way, you know, it's cause it obviously 00:13:07.092 --> 00:13:08.712 starts capturing it, so I don't know. 00:13:08.892 --> 00:13:09.192 yeah, 00:13:09.282 --> 00:13:09.522 I, 00:13:10.097 --> 00:13:10.427 Mario: Yeah. 00:13:10.457 --> 00:13:10.937 I don't know. 00:13:11.447 --> 00:13:13.637 It's a, it's an interesting one. 00:13:13.937 --> 00:13:14.500 And I, 00:13:14.500 --> 00:13:19.450 hope it's not something that simple because man, that's gonna suck 00:13:20.300 --> 00:13:20.740 if it's 00:13:21.300 --> 00:13:24.985 something super simple that I missed and I've been breaking my 00:13:24.985 --> 00:13:26.635 head, you know, this whole time. 00:13:27.270 --> 00:13:29.370 Alan: But you you've, you've got staging up and running now 00:13:29.370 --> 00:13:29.760 or it's 00:13:29.785 --> 00:13:30.955 Mario: almost, almost 00:13:30.955 --> 00:13:33.994 yeah, I I just need to finish a few, 00:13:34.774 --> 00:13:38.304 a few areas here and there, but yeah, I w I almost. 00:13:38.304 --> 00:13:39.294 have it all up and running 00:13:39.629 --> 00:13:39.929 Alan: Cool. 00:13:40.554 --> 00:13:45.174 Mario: and then I have to do the DNS updates so that I get my staging 00:13:45.174 --> 00:13:46.014 domain going. 00:13:46.604 --> 00:13:46.754 Alan: Yeah. 00:13:47.494 --> 00:13:48.094 Oh, well, good luck. 00:13:48.094 --> 00:13:53.824 That sounds like a nightmare run stressful, especially since you have 00:13:53.824 --> 00:13:55.294 people trying to use it now is like, 00:13:55.354 --> 00:13:55.984 The pressures on 00:13:55.984 --> 00:13:56.254 now, right?. 00:13:56.274 --> 00:13:56.934 Mario: yeah, 00:13:57.064 --> 00:13:59.074 Alan: Feel like you're against the clock, but it's good practice. 00:13:59.274 --> 00:13:59.664 Mario: Yeah. 00:13:59.724 --> 00:14:00.054 Yeah. 00:14:00.084 --> 00:14:00.354 Good. 00:14:00.384 --> 00:14:01.314 Yeah, for sure. 00:14:03.064 --> 00:14:04.144 Alan: It is not optimum. 00:14:04.584 --> 00:14:05.184 Mario: Yeah. 00:14:05.274 --> 00:14:09.174 So needless to say, I haven't really had time to, to put 00:14:09.174 --> 00:14:11.274 together our podcast episode 00:14:11.954 --> 00:14:12.294 Alan: yeah. 00:14:12.444 --> 00:14:13.314 Mario: is so, 00:14:13.744 --> 00:14:14.524 Alan: There's priorities. 00:14:14.524 --> 00:14:15.214 Get this working 00:14:15.214 --> 00:14:15.544 first 00:14:15.594 --> 00:14:16.194 Mario: yeah. 00:14:16.194 --> 00:14:17.184 So I apologize. 00:14:17.184 --> 00:14:21.594 I really want to Get that going, but I have to focus on this for now, 00:14:21.784 --> 00:14:22.084 Alan: Yeah. 00:14:22.254 --> 00:14:23.155 Mario: but Yeah. 00:14:23.905 --> 00:14:25.015 but we'll, we'll get there. 00:14:25.225 --> 00:14:25.855 We'll get there. 00:14:27.745 --> 00:14:33.231 I can't wait to be in a position where we can outsource editing to somebody else. 00:14:33.231 --> 00:14:36.591 And so that way we just record and we don't have to worry about 00:14:36.741 --> 00:14:37.521 Alan: happens right. 00:14:37.791 --> 00:14:41.901 Mario: it just magically appears on the, on the pod catcher. 00:14:42.586 --> 00:14:43.486 Alan: That'd be the best, doesn't it? 00:14:43.486 --> 00:14:43.696 Yeah. 00:14:43.696 --> 00:14:46.396 It's like, especially if, I mean, that's the nice thing, because you have 00:14:46.426 --> 00:14:49.126 a possibility somebody else going in and grabbing the fires, you 00:14:49.126 --> 00:14:50.386 literally don't have to do anything. 00:14:50.386 --> 00:14:50.806 You'd just be 00:14:50.806 --> 00:14:53.626 like, tell them, it's just record it finish. 00:14:54.166 --> 00:14:54.586 And it just 00:14:54.586 --> 00:14:55.126 appears, right. 00:14:55.336 --> 00:14:55.946 That'd be the, the 00:14:56.026 --> 00:14:56.446 ultimate. 00:14:56.521 --> 00:14:56.881 Mario: Yeah. 00:14:57.061 --> 00:14:57.481 Yeah. 00:14:58.216 --> 00:14:58.516 Alan: Nice. 00:14:58.531 --> 00:15:00.031 Mario: That's, that's where I'm working. 00:15:00.061 --> 00:15:01.081 I'm working towards that. 00:15:02.506 --> 00:15:03.076 Alan: that's a goal. 00:15:03.136 --> 00:15:04.186 You got to have a good goal, right? 00:15:04.531 --> 00:15:04.801 Mario: Yeah. 00:15:05.131 --> 00:15:05.521 Yeah. 00:15:05.821 --> 00:15:06.541 So let's see. 00:15:06.541 --> 00:15:08.398 What else what else did I have to update? 00:15:08.437 --> 00:15:11.382 I had I contacted somebody else to onboard. 00:15:11.487 --> 00:15:15.605 And I just noticed today they scheduled a date. 00:15:15.695 --> 00:15:21.155 I think it's next week or so I have to double check, but I have 00:15:21.335 --> 00:15:23.495 another one lined up to do a demo. 00:15:23.549 --> 00:15:27.959 Someone from MicroConf that I, came across on the community there and, I'm 00:15:27.959 --> 00:15:30.889 going to be doing that demo and then somebody else also from MicroConf. 00:15:30.907 --> 00:15:32.947 That I had all already on my list. 00:15:32.991 --> 00:15:34.746 Contacted me about it. 00:15:34.776 --> 00:15:37.347 And I was like, oh yeah, I have You on my list. 00:15:37.347 --> 00:15:42.122 So, I just sent out my Calendly to this other person and hopefully 00:15:42.122 --> 00:15:45.962 we'll get something scheduled and do another demo there as well. 00:15:46.030 --> 00:15:47.620 It's, let's see what else? 00:15:47.600 --> 00:15:53.676 We have yeah, like I mentioned earlier, most of the changes based on feedback 00:15:53.676 --> 00:15:56.226 that I received are already in, 00:15:56.206 --> 00:15:56.525 Except 00:15:56.695 --> 00:15:58.465 Alan: the UI is starting to look very tight. 00:15:58.465 --> 00:16:00.175 It is, let's start into it. 00:16:00.265 --> 00:16:02.695 As I said before, it's, it's amazing how it looks like. 00:16:02.725 --> 00:16:03.625 Oh, everything's fine. 00:16:03.655 --> 00:16:05.005 And then you do some improvements. 00:16:05.015 --> 00:16:05.485 There's that? 00:16:05.545 --> 00:16:06.115 Now it looks better. 00:16:06.295 --> 00:16:08.575 I didn't know it was a problem before, but it looks, it feels better. 00:16:08.845 --> 00:16:12.107 So yeah, I noticed you got your like ellipses thing 00:16:12.107 --> 00:16:13.157 in and Yeah. 00:16:13.157 --> 00:16:15.917 they got these, these status icons and things, and it's looking nice. 00:16:16.257 --> 00:16:16.707 Mario: Yeah. 00:16:16.767 --> 00:16:17.487 yeah, it's getting there. 00:16:17.487 --> 00:16:17.967 Thank you. 00:16:18.567 --> 00:16:18.987 Thanks. 00:16:19.057 --> 00:16:22.537 Oh, notice I implemented the HashIDs library. 00:16:23.037 --> 00:16:24.897 Alan: I noticed that I was going to ask about that. 00:16:24.897 --> 00:16:26.757 So that's, that's kind of fun, isn't it? 00:16:26.757 --> 00:16:27.747 That it's it's handy. 00:16:27.747 --> 00:16:28.017 Think 00:16:28.147 --> 00:16:28.867 Mario: yeah, yeah, 00:16:29.007 --> 00:16:31.167 Alan: Just to be able to throw stuff in and then you 00:16:31.167 --> 00:16:32.097 just decode it? 00:16:32.097 --> 00:16:32.457 and it's done. 00:16:32.947 --> 00:16:33.727 Mario: yeah, yeah. 00:16:33.727 --> 00:16:34.297 It was cool. 00:16:34.311 --> 00:16:39.347 I like it I like the short little hash and I like how it looks now. 00:16:39.347 --> 00:16:40.877 it's a little more, 00:16:41.717 --> 00:16:44.687 I dunno, more professional, so to speak, you know? 00:16:46.227 --> 00:16:47.787 Alan: I mean, it's the same with mine, you know? 00:16:47.787 --> 00:16:49.967 Cause especially if you're looking at like a, you know, 00:16:49.967 --> 00:16:53.877 a check-in and it's in a profile or some type of uses, you know, a particular 00:16:53.877 --> 00:16:56.127 user's check-in so rather than having, 00:16:56.217 --> 00:16:59.847 you know, slash seven slash 13, it's like something, can you like, 00:16:59.877 --> 00:17:00.087 oh, 00:17:00.257 --> 00:17:00.647 Mario: Yeah. 00:17:01.537 --> 00:17:03.477 Alan: Must be it must be secure that. 00:17:04.397 --> 00:17:04.787 Mario: Yeah. 00:17:05.507 --> 00:17:05.957 Yeah. 00:17:06.227 --> 00:17:08.807 And, and I didn't do it for all of it. 00:17:08.837 --> 00:17:11.147 All of the, all of the app just yet. 00:17:11.238 --> 00:17:13.428 Because I have a lot of IDs 00:17:13.428 --> 00:17:13.998 everywhere. 00:17:14.115 --> 00:17:18.225 And so I figured this is the most public facing URL. 00:17:18.255 --> 00:17:18.585 Right. 00:17:18.885 --> 00:17:19.485 And so I just 00:17:19.630 --> 00:17:20.620 Alan: I had to think the same. 00:17:20.620 --> 00:17:23.410 Yeah, it was, it was what's what's the most likely thing that's 00:17:23.410 --> 00:17:26.432 going to be cut and paste is, is really the thing, which yeah. 00:17:26.792 --> 00:17:30.992 Made me decide what to watch twin code like that is, and 00:17:31.082 --> 00:17:32.702 there's a possibility for mine. 00:17:32.702 --> 00:17:36.332 It would be a reference to a particular check-in or particular user. 00:17:36.332 --> 00:17:38.552 So those are the things that I did first and then 00:17:38.942 --> 00:17:42.692 just other things as, as I come across them, I might might change them, but 00:17:43.017 --> 00:17:43.317 Mario: Okay. 00:17:43.317 --> 00:17:46.227 So you didn't, you didn't implement it across the board? 00:17:46.557 --> 00:17:46.887 Yeah. 00:17:47.037 --> 00:17:47.487 Just yet. 00:17:49.262 --> 00:17:50.522 Alan: I think there's a few places where 00:17:50.522 --> 00:17:51.242 it's not using it. 00:17:51.242 --> 00:17:51.482 Yeah. 00:17:51.572 --> 00:17:52.402 I, I didn't 00:17:52.906 --> 00:17:54.866 that, wasn't how I intended to do it. 00:17:54.906 --> 00:17:57.056 That it wasn't how I implemented it. 00:17:57.056 --> 00:17:59.006 It was like, okay, where do I want it implemented? 00:17:59.006 --> 00:18:00.326 And just pick out particular ones. 00:18:00.326 --> 00:18:03.176 And then it's like, well, if I come across one, I'm working on something. 00:18:03.176 --> 00:18:03.536 I think. 00:18:04.571 --> 00:18:05.921 Change that while I'm here. 00:18:05.951 --> 00:18:10.241 And so, as I said, it's not a priority for every single page. 00:18:10.241 --> 00:18:13.601 It's just certain things which are likely to be cut and paste, 00:18:13.601 --> 00:18:18.851 or is an obvious reference to an internal that you really want to 00:18:18.851 --> 00:18:19.391 expose. 00:18:20.111 --> 00:18:22.721 So in particularly user ID, which is, 00:18:23.041 --> 00:18:23.641 Mario: yeah, 00:18:23.951 --> 00:18:27.101 Alan: especially at this stage, let's say when we're talking like tens of numbers 00:18:27.101 --> 00:18:30.311 or single digits, and there's like a little, that's funny because I had, 00:18:30.291 --> 00:18:35.651 So the original photo sharing thing that I did back in 2002 that, that was, you 00:18:35.651 --> 00:18:39.071 know, I was still, you know, it was the first web application I ever built was 00:18:39.071 --> 00:18:39.821 2002. 00:18:39.821 --> 00:18:42.792 It was pretty much, you know an interface to your database. 00:18:43.082 --> 00:18:43.412 Mario: yeah. 00:18:44.262 --> 00:18:48.920 Alan: And so of course IDs were just exposed as numbers and it became a kind of 00:18:48.994 --> 00:18:52.234 Like a badge of pride for people as well, because they were like a, you 00:18:52.234 --> 00:18:57.483 know, I'm not number 100, are those one that was you know, seven and they, 00:18:57.613 --> 00:19:02.033 they, they incorporated seven into their profile image and stuff like that. 00:19:02.033 --> 00:19:06.631 So it's kind of, it became a bit of a badge that that ID number, to be 00:19:06.631 --> 00:19:10.711 honest, even with like Twitter, because I'm number 5,000 or something ID in 00:19:10.711 --> 00:19:14.957 Twitter before they implemented these crazy long digits that that don't 00:19:14.957 --> 00:19:18.947 really mean so much originally they just had, you know, incremental ideas. 00:19:18.977 --> 00:19:20.087 So, yeah, 00:19:20.087 --> 00:19:22.727 it's, it's a little bit of a, a badge of pride. 00:19:22.727 --> 00:19:23.657 It's like, I was, 00:19:24.397 --> 00:19:24.657 Mario: Yeah. 00:19:24.877 --> 00:19:26.737 You were early, early adopter. 00:19:27.517 --> 00:19:27.637 Alan: yeah, 00:19:27.637 --> 00:19:30.414 I didn't get it at first, but yeah, I, I was like, okay, 00:19:30.414 --> 00:19:31.404 this has gotta be interested. 00:19:31.444 --> 00:19:31.644 And then 00:19:34.344 --> 00:19:34.974 I came around, 00:19:35.513 --> 00:19:35.843 Mario: Yeah. 00:19:36.848 --> 00:19:37.328 Alan: so, yeah. 00:19:37.388 --> 00:19:38.918 So I've had an interesting week as well. 00:19:38.995 --> 00:19:39.865 As you may have noticed. 00:19:40.730 --> 00:19:41.450 Mario: Yeah, 00:19:42.140 --> 00:19:47.990 Alan: Not quite as hectic as yours, but interesting, nonetheless, so yeah, I sent 00:19:47.990 --> 00:19:54.200 out a bunch of invitations, so I was quite the, the reasoning or the choice 00:19:54.290 --> 00:19:59.626 of first invitations to send out was people who I knew would be picky 00:19:59.626 --> 00:20:02.206 about or spot things that I've missed. 00:20:02.536 --> 00:20:06.688 So rather than go for someone who's like the, the perfect user, it 00:20:06.688 --> 00:20:09.898 was like, okay, let's, let's get these all these niggles ironed out. 00:20:09.928 --> 00:20:14.008 And so choose, you know, five people who I know are going to be like, that's wrong. 00:20:14.038 --> 00:20:14.728 That looks weird. 00:20:14.728 --> 00:20:14.908 This 00:20:15.828 --> 00:20:16.128 Mario: yeah, 00:20:16.438 --> 00:20:19.798 Alan: pick all the things, which I know I'm blind to now, it's you, you know, 00:20:19.798 --> 00:20:23.158 yourself, you're looking at something and someone says, that's the wrong color. 00:20:23.158 --> 00:20:24.268 And you're like, oh yeah, because of this. 00:20:24.668 --> 00:20:25.178 Mario: yeah. 00:20:25.207 --> 00:20:27.877 Alan: So yeah, I was kind of selective with those. 00:20:27.935 --> 00:20:32.525 And it was perfect for that because all of the feedback I got was interesting. 00:20:33.575 --> 00:20:37.655 Unique and not, not really anything overlapping, so different people 00:20:37.655 --> 00:20:44.255 saw different things and all of them were either immediately actionable or 00:20:44.585 --> 00:20:47.405 things, which are like, okay, that's, that's a really interesting thing 00:20:47.405 --> 00:20:49.415 to consider for the next release. 00:20:49.464 --> 00:20:54.204 So yeah, almost all of them I've been able to incorporate already. 00:20:54.207 --> 00:20:56.639 Some of them, you know as you know, some of them are like five minutes 00:20:56.729 --> 00:20:59.879 that it's feels great just to have now have a list of a to-do list 00:20:59.879 --> 00:21:01.109 to just be able to check through. 00:21:01.201 --> 00:21:04.198 And there was very few which I disagreed with which was nice as well. 00:21:04.198 --> 00:21:08.518 All of the points were things that it's funny, some of them. 00:21:09.808 --> 00:21:14.792 So one of the things when you're editing, if you've added items and 00:21:14.792 --> 00:21:22.172 you're editing them, clicking away, used to leave the form field open 00:21:22.172 --> 00:21:24.533 because when I first added that. 00:21:25.388 --> 00:21:30.908 I couldn't get the blur, the input blur thing, working properly with life 00:21:30.908 --> 00:21:35.678 view, as I wanted it to, it was kind of half working, but it never felt right. 00:21:35.757 --> 00:21:40.587 So therefore I was like, okay, it feels less weird to leave it than it does to 00:21:40.587 --> 00:21:44.157 have this weird state state where it doesn't always do what I wanted it to. 00:21:44.172 --> 00:21:44.407 Which. 00:21:45.307 --> 00:21:48.280 And so someone's feedback was okay. 00:21:48.460 --> 00:21:52.600 The blur feels weird and I'm like, yeah, I know it is. 00:21:53.320 --> 00:21:56.740 I know when I did this, it's just like, oh yeah, I know. 00:21:56.740 --> 00:21:58.732 And I really let, let me have a look. 00:21:59.122 --> 00:22:02.362 And it literally took one minute to, to make it work. 00:22:02.602 --> 00:22:05.272 As I talk about, you know, leaving something and coming back to it, 00:22:05.872 --> 00:22:08.212 looking at it fresh, because I haven't looked at this, you know, 00:22:08.212 --> 00:22:11.332 for probably a few months or months, definitely three or four months. 00:22:11.692 --> 00:22:14.572 And so I was like, ah, this will make it work. 00:22:14.632 --> 00:22:18.232 And I did it and it, it was like two minutes and it, it worked exactly as I 00:22:18.232 --> 00:22:20.122 wanted it to, and it felt perfectly right. 00:22:20.122 --> 00:22:23.842 And I'm like, phew, I'm glad I didn't bother wasting days trying 00:22:23.842 --> 00:22:27.022 to get it working before, because like fixing it now is just so easy. 00:22:27.097 --> 00:22:32.457 So I don't know whether that was me understanding Liveview better LiveView 00:22:32.527 --> 00:22:37.177 fixing something that wasn't working before, or I'm not sure exactly 00:22:37.177 --> 00:22:39.877 what the reason I couldn't get it to work properly before it was. 00:22:39.877 --> 00:22:44.047 I'm going to blame LiveView, you just cause it's easier than blaming myself, 00:22:46.057 --> 00:22:48.247 but it's mostly, probably my fault. 00:22:48.263 --> 00:22:51.773 So that was really nice to be able to just improve it in ways 00:22:51.773 --> 00:22:54.503 that I knew were not great. 00:22:54.683 --> 00:22:58.733 And somebody to point it out and then immediately be able to improve it. 00:22:58.793 --> 00:23:01.943 And it'll add that's exactly how I wanted it to work in the first place that thank 00:23:01.943 --> 00:23:03.893 you for reminding me to re-look at it. 00:23:03.957 --> 00:23:07.126 And yeah, even some of your feedback was, was really helpful. 00:23:07.126 --> 00:23:10.006 Just, you know, like alignments and the button of stuff, some of 00:23:10.006 --> 00:23:15.588 the hover states I improved it, it feels significantly better to 00:23:15.588 --> 00:23:17.268 me now than it did two weeks ago. 00:23:17.268 --> 00:23:20.711 So and that's a direct result of people's feedback. 00:23:20.741 --> 00:23:22.271 And I say it's, it's up in. 00:23:23.246 --> 00:23:27.709 I think there's seven invitations have sent out five who have given 00:23:28.039 --> 00:23:32.749 good feedback, two who I think are on, have been on Easter vacation. 00:23:32.749 --> 00:23:35.363 So I'm going to poke again and probably under this week, give 00:23:35.363 --> 00:23:37.332 them a week to recover coming back. 00:23:37.403 --> 00:23:39.803 So it's been really helpful. 00:23:39.893 --> 00:23:41.723 So that, that has been kind of fun. 00:23:41.731 --> 00:23:46.561 So the next step now is to introduce the people who I think could actually 00:23:46.561 --> 00:23:52.951 be the, kind of like the ideal use cases of the specifically around teams. 00:23:53.161 --> 00:23:55.711 So all of the people I picked right now are either, 00:23:55.697 --> 00:23:57.980 Basically using it by themselves. 00:23:58.095 --> 00:23:58.395 Mario: yeah. 00:23:58.515 --> 00:23:58.935 yeah. 00:23:59.325 --> 00:24:00.075 That's how I've been 00:24:00.075 --> 00:24:00.375 using 00:24:00.375 --> 00:24:00.585 it 00:24:01.100 --> 00:24:01.340 Alan: right. 00:24:01.785 --> 00:24:05.746 Mario: And but you know, it surprisingly it works well. 00:24:05.746 --> 00:24:10.134 I mean, yes, it's designed for teams and it's it's you, you know, teams 00:24:10.134 --> 00:24:15.370 could take a better advantage of it, but but it surprisingly works. 00:24:15.730 --> 00:24:19.930 I mean, so PR surprisingly in terms of, you know, Because your main 00:24:19.930 --> 00:24:25.660 focus is for teams, but it works really well with, you know, with a solo 00:24:25.900 --> 00:24:26.800 Alan: Well, that's the thing. 00:24:26.800 --> 00:24:27.670 I mean, I use it 00:24:27.670 --> 00:24:28.810 myself every day, right. 00:24:28.810 --> 00:24:30.490 So this is, this is my own 00:24:30.520 --> 00:24:33.760 thing and it it's, I know how useful it is just for me. 00:24:33.760 --> 00:24:35.740 So I, that doesn't surprise. 00:24:35.800 --> 00:24:37.900 It's surprising that other people have picked up on it, 00:24:37.900 --> 00:24:40.240 but it doesn't surprise me that much because it's like, yeah, 00:24:40.270 --> 00:24:41.590 I know, I know it's actually 00:24:41.590 --> 00:24:41.950 useful. 00:24:42.105 --> 00:24:42.525 Mario: Yeah. 00:24:42.670 --> 00:24:43.810 Alan: so let's, that's good to hear. 00:24:43.830 --> 00:24:46.723 But at the same, because it's not optimized for that. 00:24:46.723 --> 00:24:48.613 There's a lot of things that could be done 00:24:48.613 --> 00:24:50.353 better if it was just for you. 00:24:50.353 --> 00:24:50.653 Right. 00:24:50.694 --> 00:24:55.621 So that is definitely something that I'm thinking more about simply because 00:24:56.461 --> 00:25:00.991 it's easier to convince one person to use it then to convince five, right. 00:25:01.531 --> 00:25:04.370 So, you know, someone will try it out for themselves and then 00:25:04.370 --> 00:25:05.720 potentially invite other people. 00:25:06.835 --> 00:25:10.825 The single person use cases, something I want to think about a little bit 00:25:10.825 --> 00:25:15.870 more in the reasonable, close future as well, just cause I think it's 00:25:15.870 --> 00:25:20.277 actually has a lot of use I think it'd be good to spend a bit of time on. 00:25:20.297 --> 00:25:24.667 I just haven't really given it much as much thought as I have the team side. 00:25:24.697 --> 00:25:28.780 So so the it, it's funny because you're not the only person that said that either. 00:25:28.780 --> 00:25:29.530 I've had a few of 00:25:29.530 --> 00:25:31.900 the people say, ah, this is actually really useful just for me. 00:25:31.960 --> 00:25:32.140 And I'm 00:25:32.140 --> 00:25:32.830 like, ah, okay, 00:25:32.950 --> 00:25:33.370 Mario: Yeah. 00:25:33.730 --> 00:25:35.380 So I've been, I've been using it, 00:25:35.509 --> 00:25:36.439 You know, here and there. 00:25:37.369 --> 00:25:41.659 I want to get more into it and use it even more, but I have, I have been using 00:25:41.659 --> 00:25:45.759 it occasionally just to, you know, get a feel for it and and give you feedback. 00:25:45.789 --> 00:25:47.103 But I like it a lot. 00:25:47.103 --> 00:25:50.943 I like the, the, the interface is playful. 00:25:50.943 --> 00:25:54.678 It's you know, pretty modern and, and it just feels good. 00:25:55.268 --> 00:25:56.778 I like what you've done with that. 00:25:56.882 --> 00:25:57.452 Yeah. 00:25:57.482 --> 00:25:57.992 Yeah. 00:25:58.322 --> 00:26:03.272 Sometimes I, I, I think some interfaces. 00:26:03.982 --> 00:26:10.282 Tend to be kind of rigid, you know, or utilitarian, you know, even, even 00:26:10.282 --> 00:26:15.749 Fusioncast, you know, sometimes I question some of my choices and just the structure, 00:26:15.749 --> 00:26:21.113 you know, cause I made it very structured and, you know just to try to give it give 00:26:21.113 --> 00:26:23.811 it a sense of order I guess, or, you know, 00:26:23.811 --> 00:26:26.391 But I like how you accomplish that. 00:26:26.421 --> 00:26:28.031 I mean, it looks, it makes sense. 00:26:28.031 --> 00:26:29.051 It looks intuitive. 00:26:29.531 --> 00:26:32.470 And at the same time it's playful. 00:26:32.470 --> 00:26:35.481 And, and I guess what I mean by playful is just that it it's you 00:26:35.481 --> 00:26:41.031 know, it, it, it doesn't have this utilitarian feel to it where, you 00:26:41.031 --> 00:26:45.859 know, everything is rows and columns, you know, it's, you know what I mean? 00:26:46.204 --> 00:26:46.534 Alan: Yes. 00:26:46.639 --> 00:26:47.269 Mario: Yeah, It 00:26:47.464 --> 00:26:48.334 Alan: it does. 00:26:48.544 --> 00:26:51.304 It's funny because somebody else gave me the feedback. 00:26:51.334 --> 00:26:51.484 Yeah. 00:26:51.494 --> 00:26:54.604 It feels in one way, kind of old school web, even though it's 00:26:54.604 --> 00:26:56.374 using modern technologies 00:26:56.434 --> 00:27:02.314 and it feels a little bit more retro in the way that it isn't regimented. 00:27:02.314 --> 00:27:02.494 And 00:27:02.704 --> 00:27:06.514 I guess that's my personal preferences coming out strongly, 00:27:06.669 --> 00:27:07.359 Mario: Yes. 00:27:07.359 --> 00:27:07.959 Yes. 00:27:08.154 --> 00:27:09.004 Alan: but I know that 00:27:09.004 --> 00:27:09.304 I 00:27:09.339 --> 00:27:11.289 Mario: that's a good, that's a good way to describe it. 00:27:11.619 --> 00:27:12.099 It's like, 00:27:12.159 --> 00:27:15.279 like old school, but with a modern touch, you know the. 00:27:15.279 --> 00:27:16.509 modern UI, you know, 00:27:16.684 --> 00:27:16.954 Alan: Cool. 00:27:17.254 --> 00:27:20.384 That's really good to hear that that's very reassuring because that's, that's 00:27:20.404 --> 00:27:24.844 something that bugs the hell of hell out of me about the current state of the web 00:27:24.844 --> 00:27:31.701 is just, everything's becoming very, to feels culprit, even when it's a you know, 00:27:31.711 --> 00:27:35.631 an indie project, it still feels like things are coming from a corporation. 00:27:35.631 --> 00:27:38.961 It's like, I, you know, I want your personality to come through too. 00:27:38.961 --> 00:27:42.411 So I tried to, and this is something I'm trying hard with 00:27:42.411 --> 00:27:43.881 the copy and things as well. 00:27:43.881 --> 00:27:47.631 So I'm, so I've started playing with copy.ai. 00:27:47.631 --> 00:27:48.351 Have you seen it? 00:27:48.381 --> 00:27:49.071 Have you played with 00:27:49.071 --> 00:27:49.221 it? 00:27:49.316 --> 00:27:50.386 Mario: No, No, 00:27:51.171 --> 00:27:51.561 Alan: cool. 00:27:51.561 --> 00:27:54.321 It's an indie hacker project is two guys, I think. 00:27:54.651 --> 00:27:59.493 And it uses the GPT three machine learning data prediction, text 00:27:59.493 --> 00:28:00.811 prediction rewriting thing. 00:28:00.823 --> 00:28:04.177 So you give it a description or some copy. 00:28:04.177 --> 00:28:05.047 You basically tell it 00:28:05.047 --> 00:28:05.317 what. 00:28:06.887 --> 00:28:10.787 What you want or what you want to say, and it will rephrase 00:28:10.787 --> 00:28:13.097 it in multiple different ways. 00:28:13.307 --> 00:28:18.767 So for instance, you can use it for say a landing page, like hero texts. 00:28:18.788 --> 00:28:21.655 You, you describe your project and it gives you like 10 different 00:28:21.655 --> 00:28:25.885 examples of copy that you could use as hero, text for your project. 00:28:25.975 --> 00:28:32.815 And it's not using it too directly, but as a way of like unblocking your mind. 00:28:32.815 --> 00:28:35.815 Cause you know, when you think about something, you get stuck in a rot, right? 00:28:36.205 --> 00:28:40.465 So even just like the copy on my homepage, where you. 00:28:41.140 --> 00:28:43.690 As in, after you've logged in, there's kind of a dashboard page that shows 00:28:43.690 --> 00:28:44.800 you, other people have logged in. 00:28:45.190 --> 00:28:49.058 So the text says like, you know, good morning you know, other people have done 00:28:49.058 --> 00:28:50.528 things, you know, have you finished this? 00:28:50.678 --> 00:28:53.528 So I write it as how I'd want to say it first. 00:28:53.858 --> 00:28:56.498 And then once you've done that, you kind of get stuck in that you 00:28:56.498 --> 00:28:57.938 can't see other ways of writing it. 00:28:57.938 --> 00:28:58.178 Right. 00:28:58.388 --> 00:28:59.888 So you throw it in copy AI. 00:29:00.338 --> 00:29:02.048 And it says, how about these? 00:29:02.078 --> 00:29:04.928 And you're like, Okay, that wasn't thinking of that, but that 00:29:05.198 --> 00:29:08.798 some part of that wording would sounds better than my wording. 00:29:09.038 --> 00:29:13.269 So, so it kind of just a way of getting your brain out of that groove 00:29:13.359 --> 00:29:14.769 and just trying different things. 00:29:14.949 --> 00:29:16.209 So I highly recommend it. 00:29:16.239 --> 00:29:19.359 It's a, it, then there's a seven day free, completely free trial. 00:29:19.389 --> 00:29:23.949 And then it's like $30 a month and it's, so it's got a thing for like 00:29:23.961 --> 00:29:26.069 email subject that are catchy. 00:29:26.069 --> 00:29:28.799 So again, you say what your email is, and it says, how 00:29:28.799 --> 00:29:30.389 about these as email subjects? 00:29:30.419 --> 00:29:34.079 And you're like that one, that's the tone that I want. 00:29:34.143 --> 00:29:35.833 It's got to think for like blog ideas. 00:29:35.833 --> 00:29:38.743 So you tell it what your blogs about, and it says, how about these? 00:29:39.073 --> 00:29:40.393 And they're all AI generated. 00:29:40.393 --> 00:29:45.313 So they kind of coming from a, a reasonably sensible place, but 00:29:45.463 --> 00:29:49.843 some of them are way out, but the general mix is quite quite fun. 00:29:49.843 --> 00:29:52.873 So that's really helping me improve my. 00:29:53.743 --> 00:29:57.733 Simply because it's making me try different things 00:29:57.733 --> 00:29:59.683 that I wouldn't necessarily 00:29:59.773 --> 00:30:00.613 come up with myself. 00:30:00.643 --> 00:30:00.973 So 00:30:01.178 --> 00:30:01.988 Mario: nice. 00:30:02.378 --> 00:30:02.738 What, 00:30:02.773 --> 00:30:05.133 Alan: playing with.ai. 00:30:05.893 --> 00:30:08.093 Mario: dot AI. 00:30:09.113 --> 00:30:11.498 How did you find out about this one. 00:30:12.323 --> 00:30:13.933 Alan: I don't know it, I, I, 00:30:13.953 --> 00:30:14.393 Twitter 00:30:15.413 --> 00:30:17.423 pretty much everything I know comes from Twitter these 00:30:17.423 --> 00:30:17.693 days. 00:30:17.808 --> 00:30:18.168 Mario: right? 00:30:18.168 --> 00:30:18.438 Yeah. 00:30:18.953 --> 00:30:20.693 Alan: So the two founders are on Twitter. 00:30:20.693 --> 00:30:22.613 They're there, they're doing a building in public. 00:30:22.613 --> 00:30:22.973 I think 00:30:23.233 --> 00:30:25.343 that their revenue is 00:30:25.343 --> 00:30:27.323 starting to go significantly. 00:30:27.323 --> 00:30:32.753 They were like I mean that tens of thousands, I think a month, but they, they 00:30:32.753 --> 00:30:35.783 give updates on their MRR, MRR regularly. 00:30:35.783 --> 00:30:38.483 So they seem to be onto something quite good. 00:30:38.513 --> 00:30:40.613 And it is a really simple web app. 00:30:40.613 --> 00:30:44.750 It's just an interface to TP T3, but with specific contexts. 00:30:44.780 --> 00:30:49.090 So you say, you know, I want this type of thing. 00:30:49.090 --> 00:30:50.980 It just like sentence rewriting, things like that. 00:30:50.980 --> 00:30:55.150 So it's well worth playing with, if you want landing page copy 00:30:55.150 --> 00:30:56.500 or email copy, things like that. 00:30:56.500 --> 00:31:00.520 Just you like your landing page is already pretty good as 00:31:00.520 --> 00:31:02.980 well, but it could be a way of 00:31:02.980 --> 00:31:05.650 just trying to get different ideas. 00:31:05.850 --> 00:31:06.420 Mario: Yeah. 00:31:06.540 --> 00:31:07.680 Yeah, totally. 00:31:07.680 --> 00:31:07.830 Yeah. 00:31:07.830 --> 00:31:09.470 I'm looking at their website site. 00:31:09.470 --> 00:31:10.590 Site looks cool too. 00:31:11.670 --> 00:31:11.970 Alan: Cool. 00:31:12.390 --> 00:31:12.780 Mario: Yeah. 00:31:13.200 --> 00:31:13.410 Alan: Yeah. 00:31:13.410 --> 00:31:15.088 So that's that that's really good to hear. 00:31:15.112 --> 00:31:20.505 I'm very happy to hear that that it's it feels like it's, you know, there's a 00:31:20.505 --> 00:31:25.545 million things that I really wanted to do, and I've been desperate to just not 00:31:26.025 --> 00:31:28.275 get too bogged down in doing everything. 00:31:28.275 --> 00:31:33.524 So hopefully this the functionality provides right now has a use and it is 00:31:33.524 --> 00:31:35.474 useful and now a consult to build on 00:31:35.474 --> 00:31:35.894 top of that. 00:31:35.894 --> 00:31:36.254 So, 00:31:36.346 --> 00:31:37.846 That's, that's the hope. 00:31:38.476 --> 00:31:38.926 Mario: Yeah. 00:31:38.986 --> 00:31:40.936 Yeah, It's looking good. 00:31:40.936 --> 00:31:41.836 It's looking really good. 00:31:41.886 --> 00:31:42.816 I like using it. 00:31:43.026 --> 00:31:44.346 I'm going to be using it more. 00:31:44.426 --> 00:31:49.526 I started using it for Fusioncast related tasks, So, to speak. 00:31:49.648 --> 00:31:54.160 And so As I, as I get more into it, I'll give you more feedback, 00:31:54.160 --> 00:31:55.480 you know, whatever I come across. 00:31:55.543 --> 00:31:56.362 But Yeah. 00:31:56.362 --> 00:31:57.562 it's, it's looking really good. 00:31:57.562 --> 00:31:58.132 I like it. 00:31:58.837 --> 00:31:59.047 Alan: Good. 00:31:59.047 --> 00:31:59.377 Thank you. 00:31:59.647 --> 00:32:03.727 So I think that the thing which I find it's helpful with, so I, 00:32:03.817 --> 00:32:06.397 especially on a solo project, you. 00:32:06.397 --> 00:32:11.626 know using like an issue tracker just feels like completely way too heavy. 00:32:11.657 --> 00:32:15.617 Even though, you know, it might probably be a good idea it's 00:32:15.947 --> 00:32:17.927 right now, it just feels too much. 00:32:17.927 --> 00:32:19.187 But at the same time, having a. 00:32:20.067 --> 00:32:23.397 I kind of a notepad of like, yeah, these are the things I need to do. 00:32:23.697 --> 00:32:27.357 This is the thing I need to do next and I've done it. 00:32:27.537 --> 00:32:32.230 So having that kind of way of organizing it and recording it, it 00:32:32.230 --> 00:32:34.507 just seems it works well for, for me. 00:32:34.511 --> 00:32:36.670 Hopefully others find the same thing too. 00:32:36.670 --> 00:32:41.170 So just having that, having that list of, yeah, I need to think about those things. 00:32:41.170 --> 00:32:43.630 Moving that to, this is my thing. 00:32:43.660 --> 00:32:45.460 These are the three things I'm going to do next. 00:32:45.532 --> 00:32:51.212 I mean, I've even almost, there's lots of things that I thought about trying 00:32:51.212 --> 00:32:57.392 to like codify and recommend, but I kind of want people to figure those 00:32:57.392 --> 00:32:59.912 things out for themselves as well, figure out what works best for them. 00:32:59.912 --> 00:33:02.282 So I'm trying not to be too heavy handed with like, you 00:33:02.282 --> 00:33:03.452 know, what is your main thing? 00:33:04.082 --> 00:33:04.862 Choose three things. 00:33:04.862 --> 00:33:06.362 And it's like, ah, they're adults. 00:33:06.392 --> 00:33:07.142 They can figure it out. 00:33:07.142 --> 00:33:07.382 Right. 00:33:07.617 --> 00:33:08.007 Mario: Yeah. 00:33:08.037 --> 00:33:08.577 Yeah, 00:33:08.637 --> 00:33:09.597 no, I'm glad. 00:33:09.597 --> 00:33:11.487 I'm glad you're going in that direction. 00:33:11.487 --> 00:33:12.507 It's a little more, 00:33:12.553 --> 00:33:19.036 It just gives freedom to people to use it the best way it fits for them. 00:33:19.036 --> 00:33:19.156 You 00:33:19.216 --> 00:33:22.786 Alan: mean, so, yeah, I mean, one of the things that's, I, again, I guess this 00:33:22.786 --> 00:33:28.036 is a product, a byproduct of me being a, an old school web user and fan of 00:33:28.096 --> 00:33:33.835 like my favorite web apps that I've I've I still feel I learnt a lot from under 00:33:33.895 --> 00:33:35.845 my kind of favorite types of web apps. 00:33:35.845 --> 00:33:39.445 I think it's like the original delicious before it became something 00:33:39.565 --> 00:33:44.325 that the original flicker when, and all of them are still, they have 00:33:44.325 --> 00:33:47.655 this aspect of like human hacking. 00:33:47.655 --> 00:33:51.645 So they give you a re loads of features and they say, you figure it out. 00:33:51.645 --> 00:33:58.155 So communities naturally form around like flicker tags or, you 00:33:58.155 --> 00:33:59.415 know, like albums and things. 00:33:59.426 --> 00:34:02.366 And same with delicious, you know, people come up with different ways 00:34:02.366 --> 00:34:05.765 of using it that weren't necessarily on their original roadmap or, you 00:34:05.765 --> 00:34:07.145 know, it wasn't the original design. 00:34:07.145 --> 00:34:07.355 They. 00:34:07.381 --> 00:34:08.535 Created by the users. 00:34:08.535 --> 00:34:13.725 I mean, like Twitter's hashtags and at the same rate, they weren't originally part of 00:34:13.725 --> 00:34:19.245 the original design, but they came out of people finding ways to use it that weren't 00:34:19.245 --> 00:34:21.645 necessarily conceived by the original app. 00:34:21.637 --> 00:34:26.036 So my hope is to create something that, that has a similar kind of ethos, 00:34:26.036 --> 00:34:30.266 something that is, here's a bunch of tools you figure out the best way of using them. 00:34:30.286 --> 00:34:30.676 Mario: Yeah. 00:34:31.106 --> 00:34:34.916 Alan: And then as things as people use it, then you see patterns 00:34:34.946 --> 00:34:38.906 then maybe make those, you know, more first older features. 00:34:38.906 --> 00:34:43.215 But yeah, I don't want to force those down people's throats, which again 00:34:43.425 --> 00:34:47.325 is certain, you know, newer apps tend to be like, this is how you use it. 00:34:47.325 --> 00:34:47.715 And you're like, 00:34:48.825 --> 00:34:49.665 don't feel like it. 00:34:50.005 --> 00:34:51.075 Mario: yeah, yeah, 00:34:52.305 --> 00:34:52.665 Alan: that's 00:34:52.665 --> 00:34:53.385 just really good to know. 00:34:53.445 --> 00:34:54.742 I I'm I 00:34:54.742 --> 00:34:56.172 appreciate the comment 00:34:56.172 --> 00:34:58.332 that I hope that's come through. 00:34:59.162 --> 00:34:59.702 Mario: Yeah. 00:34:59.712 --> 00:35:00.272 Yeah. 00:35:01.122 --> 00:35:06.507 Alan: it's been nice also to see no bugs as in no, 00:35:06.536 --> 00:35:08.930 Sentry things appear on my email, which is nice. 00:35:09.695 --> 00:35:10.175 Mario: Yeah. 00:35:10.550 --> 00:35:12.920 Alan: That's, that's one of the best things is like, oh, it seems 00:35:12.920 --> 00:35:13.790 to be working for everybody. 00:35:14.655 --> 00:35:14.925 Mario: Yeah. 00:35:14.925 --> 00:35:19.785 So far everything that I've, you know, the things that I shared with you have been 00:35:19.785 --> 00:35:22.677 just really cosmetic and, you know kind of 00:35:23.517 --> 00:35:25.017 superficial you know, like, 00:35:25.006 --> 00:35:26.086 Not, not any errors. 00:35:26.086 --> 00:35:27.676 I haven't come across any errors. 00:35:27.812 --> 00:35:28.262 Alan: I'm curious. 00:35:28.262 --> 00:35:30.784 Cause you're, you're in you're in us west, right? 00:35:30.904 --> 00:35:33.409 So this is obviously how it's done AWS US west. 00:35:33.409 --> 00:35:35.929 So I guess that's Oregon is that I'm not sure. 00:35:36.234 --> 00:35:36.614 Mario: Oregon. 00:35:36.664 --> 00:35:36.894 Yeah. 00:35:36.894 --> 00:35:37.314 It's west 00:35:37.669 --> 00:35:39.079 Alan: so that's reasonably close to you, right? 00:35:39.289 --> 00:35:39.799 So 00:35:40.069 --> 00:35:42.409 since this is using live view, this. 00:35:43.909 --> 00:35:47.179 A more latency for me, a lot more latency for me 00:35:47.179 --> 00:35:47.569 than you. 00:35:47.779 --> 00:35:49.429 And it still feels okay for me. 00:35:49.429 --> 00:35:51.979 It's, I mean, there's a, an 80 millisecond. 00:35:52.189 --> 00:35:54.319 You can't get faster than that. 00:35:55.129 --> 00:35:57.289 So that's like the best case scenario. 00:35:57.283 --> 00:36:01.495 So because a lot of the, so there's two types of interaction on. 00:36:02.710 --> 00:36:06.400 On the site, there's ones which are using Alpine, which are like dropdown menus 00:36:06.400 --> 00:36:08.500 and hotter states, things like that. 00:36:08.494 --> 00:36:14.913 And then there's life view actions, which are basically it triggers a uses the web 00:36:14.913 --> 00:36:19.233 socket to basically tell the server what's happened in the server responds where they 00:36:19.233 --> 00:36:21.273 chunk of HTML that's replaced on the page. 00:36:21.633 --> 00:36:25.683 So anything as far as your plan, in terms of checking off something, 00:36:25.683 --> 00:36:30.694 moving something, editing something you know, clicking on a a plan item 00:36:31.024 --> 00:36:32.344 and changing it to an eight state. 00:36:32.344 --> 00:36:35.164 All of those are actually responses from the server. 00:36:35.194 --> 00:36:37.474 The HTML cluster is given back by the server. 00:36:37.714 --> 00:36:40.804 So I'm curious how responsive it feels like when you're close by is 00:36:40.804 --> 00:36:43.894 it feels pretty like almost instantaneous. 00:36:44.204 --> 00:36:46.984 Mario: it feels pretty instantaneous to me. 00:36:46.984 --> 00:36:50.944 It, it, yeah, there's really not any, 00:36:50.972 --> 00:36:53.797 noticeable latency at all. 00:36:53.857 --> 00:36:56.317 It's just, yeah, it's very snappy. 00:36:57.287 --> 00:36:57.767 Yeah. 00:36:58.117 --> 00:36:59.647 Alan: I mean, my, it does. 00:36:59.947 --> 00:37:01.507 I don't wanna say it's noticeable. 00:37:01.507 --> 00:37:05.227 I I, notice it because I know what I'm looking for when I'm doing it 00:37:05.227 --> 00:37:05.377 here. 00:37:06.007 --> 00:37:10.782 I notice it because it's like, ah, it's, I mean, there's an 18 mil probably 00:37:10.782 --> 00:37:11.922 a hundred milliseconds, you know, 00:37:11.952 --> 00:37:15.185 rounded up between clicking on a plan and it becoming editable. 00:37:15.231 --> 00:37:17.241 There's ways I could change that. 00:37:17.241 --> 00:37:20.690 So, you know, happens on the client first, but using just straight 00:37:20.780 --> 00:37:22.280 forward roll live view to do it. 00:37:22.310 --> 00:37:23.660 There's, that's how he does it. 00:37:23.660 --> 00:37:28.509 So yeah, that's kind of, I wish I was a bit closer to the service, but 00:37:28.569 --> 00:37:30.309 I, I it's nice being the worst case. 00:37:30.309 --> 00:37:30.519 Right. 00:37:30.519 --> 00:37:32.079 Or I guess Australia would be a worst case. 00:37:32.133 --> 00:37:33.573 It's but it still 00:37:33.573 --> 00:37:37.353 feels absolutely good enough from here, so yeah, I can imagine 00:37:37.353 --> 00:37:37.533 it. 00:37:37.743 --> 00:37:39.483 Mario: So your, your server is in Oregon. 00:37:39.483 --> 00:37:39.633 You 00:37:39.633 --> 00:37:39.933 said. 00:37:40.223 --> 00:37:41.453 Alan: Yeah, yeah, 00:37:41.748 --> 00:37:42.198 Mario: Okay. 00:37:42.198 --> 00:37:44.448 So is that a AWS? 00:37:44.658 --> 00:37:45.558 Can you share or, 00:37:45.588 --> 00:37:45.948 okay. 00:37:46.113 --> 00:37:46.713 Alan: Yes they do. 00:37:46.743 --> 00:37:46.953 Yes. 00:37:47.103 --> 00:37:49.123 So I'm using a service called a Gigalixir, 00:37:49.143 --> 00:37:51.783 which is kind of Heroku for Elixir. 00:37:51.775 --> 00:37:55.807 And they have the option of going through Google or Amazon. 00:37:55.807 --> 00:37:59.977 You can choose that they've got set up, I think on four or to Amazon, to 00:37:59.977 --> 00:38:01.927 Google data centers that you can choose. 00:38:01.922 --> 00:38:07.559 And U S west one is, is the optimum for me because it's the closest to me. 00:38:07.589 --> 00:38:11.459 And it's, it's kind of the, I guess if you're in the U S you'd probably 00:38:11.459 --> 00:38:14.609 choose, you know, us central on Google is probably a best case, but for 00:38:14.609 --> 00:38:20.720 me, it's, it's closest to personal request to, and also it's, it feels 00:38:20.720 --> 00:38:21.950 like a good balance for everybody. 00:38:21.950 --> 00:38:22.520 So 00:38:22.580 --> 00:38:26.690 it's, if it works for me, then it should be fine for what else was, was my thinking 00:38:26.690 --> 00:38:26.840 then. 00:38:27.000 --> 00:38:27.690 Mario: yeah. 00:38:27.690 --> 00:38:28.350 exactly. 00:38:28.770 --> 00:38:30.150 I did the same thing. 00:38:30.180 --> 00:38:31.710 My servers are in Oregon too. 00:38:32.130 --> 00:38:37.823 And I figured it doesn't re nowadays it doesn't really with with the internet. 00:38:37.823 --> 00:38:42.083 It doesn't really matter because you're going to have people connecting 00:38:42.083 --> 00:38:43.583 from the other side of the world. 00:38:43.583 --> 00:38:50.423 So even if I were to go with a data center, you know, in the middle of the, 00:38:50.423 --> 00:38:57.023 of the U S it it doesn't really matter because people connecting from Japan or 00:38:57.023 --> 00:39:01.920 Asia or some, you know, anywhere it's still gonna be around the world, you know? 00:39:02.195 --> 00:39:02.645 Alan: Right, right. 00:39:02.675 --> 00:39:03.185 Exactly. 00:39:03.395 --> 00:39:06.978 I mean, so I've someone has recommended CloudFlare Argo to me, 00:39:07.218 --> 00:39:10.899 which is Cloudflare's per perf. 00:39:10.989 --> 00:39:12.789 It basically optimizes the path from. 00:39:13.564 --> 00:39:14.674 Client to the server. 00:39:14.884 --> 00:39:16.714 So it would say you're going from Australia. 00:39:17.014 --> 00:39:20.794 You know, you might end up with, you know, multiple routes, which is some 00:39:20.794 --> 00:39:23.084 of them far from optimum using Argo. 00:39:23.104 --> 00:39:24.394 It's expensive. 00:39:24.408 --> 00:39:29.936 As in it's, when you look at the but apparently it does significantly minimize 00:39:29.936 --> 00:39:31.968 that that route or optimize the route. 00:39:31.968 --> 00:39:36.468 So you basically get like preferred route from wherever to the server, but 00:39:36.588 --> 00:39:38.388 I'm hoping I don't have to pay for that. 00:39:38.388 --> 00:39:38.628 So 00:39:39.093 --> 00:39:39.483 Mario: Yeah. 00:39:40.563 --> 00:39:40.833 That's 00:39:40.833 --> 00:39:41.253 a, 00:39:41.348 --> 00:39:45.498 Alan: the server is an elixir a quick enough that the response from 00:39:45.498 --> 00:39:49.128 the server is so quick that I'm basically dealing with latency. 00:39:49.128 --> 00:39:53.628 That's the only expense, you know, it's, it's, it's a millisecond or two for the 00:39:53.628 --> 00:39:55.248 server to create their response. 00:39:55.278 --> 00:39:56.448 And then you just got latency. 00:39:56.898 --> 00:39:57.318 So. 00:39:57.983 --> 00:39:58.313 Mario: yeah. 00:39:58.313 --> 00:40:04.080 And I wonder if it's more cost-effective to, before going that route of, you know, 00:40:04.080 --> 00:40:06.918 CloudFlare enhanced features or whatever. 00:40:06.940 --> 00:40:11.588 I wonder if it's more cost-effective to just up the server you know, 00:40:11.618 --> 00:40:16.762 first, if you need a boosting in performance, just up the caliber of 00:40:16.762 --> 00:40:18.292 the server that you're running on. 00:40:18.292 --> 00:40:19.912 And until you exhaust, 00:40:20.482 --> 00:40:21.652 you know, That that 00:40:21.727 --> 00:40:25.717 Alan: mean, for, for, in, in my case, especially, you know, the, the slowest bit 00:40:25.747 --> 00:40:31.627 is, is always going to be the, the latency because the, the database is on RDS. 00:40:31.657 --> 00:40:36.619 And so I did this founder's life thing a month or so ago. 00:40:36.619 --> 00:40:36.859 Right. 00:40:36.919 --> 00:40:41.389 So I got a bunch of AWS credits for that like $5,000 worth of 00:40:41.389 --> 00:40:42.259 AWS credits. 00:40:42.259 --> 00:40:42.439 Good. 00:40:42.439 --> 00:40:43.069 For two years. 00:40:43.069 --> 00:40:45.169 So I'm like, yeah, big database. 00:40:45.259 --> 00:40:45.499 So 00:40:45.694 --> 00:40:46.354 Mario: Nice. 00:40:47.159 --> 00:40:50.689 Alan: basically spending way more than I ever would personally 00:40:50.786 --> 00:40:52.736 on a, an RDS configuration. 00:40:52.736 --> 00:40:55.659 But because of that, the database is now not the issue. 00:40:55.643 --> 00:41:01.793 So the, the actual CPU bound tasks are very minimal right now because 00:41:01.805 --> 00:41:05.900 elixirs pretty damn quick and the database is right next to it. 00:41:05.900 --> 00:41:06.710 And that's really quick. 00:41:06.710 --> 00:41:09.290 So it's, it's all latency pretty much. 00:41:09.314 --> 00:41:14.499 So I hope hopefully, you know, That will be able to maintain that 00:41:14.499 --> 00:41:15.939 kind of balance that, you know, 00:41:16.569 --> 00:41:17.289 we'll see how that goes. 00:41:17.674 --> 00:41:18.574 Mario: Yeah. 00:41:18.699 --> 00:41:20.229 Alan: require users for that to change. 00:41:20.229 --> 00:41:20.439 Right. 00:41:20.964 --> 00:41:21.334 Mario: Yeah. 00:41:22.384 --> 00:41:22.744 True. 00:41:23.709 --> 00:41:25.449 Alan: So that's, that's been a yeah. 00:41:25.479 --> 00:41:28.329 A fun week or a week and a half 00:41:28.359 --> 00:41:34.345 of responding to that and just seeing how people have using it setting up some I set 00:41:34.345 --> 00:41:37.410 up mixed panels, basic response tracking. 00:41:37.410 --> 00:41:40.425 So I'm trying to use this to two ways. 00:41:40.425 --> 00:41:42.855 I'm trying to record how people are using it. 00:41:42.928 --> 00:41:47.788 So I'm using a service called Bento, which is made by somebody local, for. 00:41:48.778 --> 00:41:52.133 Being able to trigger like email drips and things like that. 00:41:52.133 --> 00:41:55.523 So that's the thing I'm trying to design right now is like, you know, 00:41:55.523 --> 00:41:58.823 what do I, when do I want to do things and what do I want them to do? 00:41:58.823 --> 00:42:02.243 So I want to start thinking about that process of like, okay, they've logged 00:42:02.243 --> 00:42:06.443 in, they've created an organization, but they haven't checked in yet. 00:42:06.443 --> 00:42:08.993 Well, in that case, if they haven't done that for a day, maybe send them 00:42:08.993 --> 00:42:11.153 an email to say, why don't you do this? 00:42:11.153 --> 00:42:13.913 Or if they've checked in, but they haven't invited somebody then, you 00:42:13.913 --> 00:42:15.983 know, maybe recommend them to do that. 00:42:15.983 --> 00:42:19.133 So I'm setting up that service to do that. 00:42:19.193 --> 00:42:20.393 And I need to figure out 00:42:20.423 --> 00:42:22.150 the, the flow of emails for that. 00:42:22.870 --> 00:42:23.080 But 00:42:23.159 --> 00:42:23.849 Mario: do you do that. 00:42:24.149 --> 00:42:25.499 programmatically with an 00:42:25.499 --> 00:42:26.099 API 00:42:26.644 --> 00:42:27.004 Alan: so 00:42:27.004 --> 00:42:27.514 it's a. 00:42:27.539 --> 00:42:28.769 Mario: with your, with your code? 00:42:29.079 --> 00:42:30.689 Alan: So he has a two things. 00:42:30.689 --> 00:42:33.629 There's either a JavaScript API, which will basically just trigger pace 00:42:33.659 --> 00:42:38.354 changes or the, but they also have a an a, an API, which I'm actually 00:42:38.354 --> 00:42:41.830 writing an Alexa module for to be able to do that programmatically. 00:42:41.830 --> 00:42:45.190 But basically just say, they've done this, they've done this. 00:42:45.700 --> 00:42:46.690 So you just send events. 00:42:46.840 --> 00:42:49.480 So it makes panel has exactly the same thing in terms of 00:42:49.480 --> 00:42:51.175 triggering recording events. 00:42:51.505 --> 00:42:55.306 You basically just say this user you know, just give them a number. 00:42:55.336 --> 00:42:58.739 This user did this, this user did this, and you just send strings of you 00:42:58.739 --> 00:43:03.610 know, created an account signed up, created organization, invited user. 00:43:03.610 --> 00:43:06.400 So you just, I'm Jason, just sending a bunch of events down to 00:43:06.400 --> 00:43:08.660 Mixpanel, and then on Mixpanel. 00:43:08.680 --> 00:43:09.130 You can create. 00:43:09.166 --> 00:43:11.626 Basically queries to make a dashboard of those things. 00:43:11.626 --> 00:43:14.536 So I say, so right now I've got a thing, a graph, which 00:43:14.536 --> 00:43:16.156 says number of signups per day. 00:43:16.606 --> 00:43:22.366 And so every time you, you basically can say show the number of times 00:43:22.366 --> 00:43:25.756 we get that event uniquely per day. 00:43:25.996 --> 00:43:29.356 And so you get a graph of signups per day, same with number of check-ins 00:43:29.356 --> 00:43:31.249 are like number of plans created. 00:43:31.249 --> 00:43:34.399 So I have a little graph of a little bar chart of how many 00:43:34.399 --> 00:43:35.959 plans have been created today. 00:43:36.024 --> 00:43:41.214 How many check-ins have been created so you can see how the usage patterns are. 00:43:41.214 --> 00:43:46.807 So without getting all you know, nosy about who did what, this just 00:43:46.807 --> 00:43:51.277 gives me an overview of like, some people did this thing this many times 00:43:51.517 --> 00:43:53.931 without being too I effecting people. 00:43:53.931 --> 00:43:54.651 Yeah, exactly. 00:43:54.651 --> 00:43:55.881 I mean, I don't care. 00:43:55.881 --> 00:43:58.971 I don't, I don't want to see, I don't want to know anything that anybody's doing. 00:43:59.050 --> 00:44:03.220 But it's useful to me to know how often people are checking in. 00:44:03.280 --> 00:44:07.000 So how often, how many people have made plans today or how many people 00:44:07.000 --> 00:44:07.990 have checked off plans today? 00:44:07.990 --> 00:44:12.040 So just by triggering, like telemetry events of when someone's done 00:44:12.040 --> 00:44:15.970 something I can just say again, it's, it's a, it's a hashed user 00:44:15.970 --> 00:44:17.320 ID, so I don't know who did it. 00:44:17.376 --> 00:44:22.266 All I know is that at this point in time, a user and it's unique 00:44:22.266 --> 00:44:24.006 because it's hashed did this thing. 00:44:24.426 --> 00:44:29.439 So and again, mixed panel have like this, this space, I guess, is highly 00:44:29.439 --> 00:44:34.179 competitive for like, I guess there's a hundred different people trying to 00:44:34.509 --> 00:44:38.902 be the, the one provider, I guess, like segment.io Mixpanel data. 00:44:39.637 --> 00:44:41.137 Box there's, there's a bunch of these. 00:44:41.497 --> 00:44:44.287 So, Mixpanel have a thing where you just say you're a startup. 00:44:44.302 --> 00:44:47.122 I I've literally new customers start up and they give you 00:44:47.122 --> 00:44:48.772 $50,000 worth of credits. 00:44:49.012 --> 00:44:50.002 And I'm like, okay. 00:44:50.062 --> 00:44:52.233 So I mean, it's, it's fake money, right. 00:44:52.233 --> 00:44:54.483 But at the same time means it means I can use a service for free 00:44:54.483 --> 00:44:55.863 for a year, as much as I want. 00:44:55.863 --> 00:44:59.693 So I guess after that, they'll get you and I'll decide, you know, either I'm in 00:44:59.703 --> 00:45:04.781 a position where I can afford to continue or I can't and don't need to because, 00:45:04.956 --> 00:45:05.256 Mario: Yeah. 00:45:06.141 --> 00:45:09.801 Alan: so at least it gives you a year to figure out what to do with it. 00:45:09.801 --> 00:45:10.576 So yeah. 00:45:10.616 --> 00:45:11.546 Recommend doing that. 00:45:11.546 --> 00:45:14.186 If you want to get an idea, I mean, in your case, you know, you 00:45:14.186 --> 00:45:16.769 could literally say, you know, somebody you know, created a. 00:45:17.744 --> 00:45:20.144 It created a scheduled on a, a call. 00:45:20.324 --> 00:45:23.864 Somebody started a call, someone joined a call, someone started recording. 00:45:23.894 --> 00:45:28.264 You could basically just see, can trigger either via JS or via serverside. 00:45:28.664 --> 00:45:33.153 And again, as long as it's just hash the user ID in a specific way you can 00:45:33.153 --> 00:45:37.593 just get a, a dashboard of those events and just knowing, I mean, I literally 00:45:37.623 --> 00:45:41.643 just have a dashboard then I just can see that one person signed up today. 00:45:41.673 --> 00:45:44.253 You know, some accepted an invite, somebody, you know, five 00:45:44.643 --> 00:45:46.833 plans have been created, you know, to have been checked off. 00:45:47.133 --> 00:45:49.881 So it's just gives me an idea of that's the usage patterns 00:45:49.881 --> 00:45:51.321 without getting too invasive or, 00:45:51.371 --> 00:45:52.301 Mario: That sounds awesome. 00:45:52.361 --> 00:45:52.751 Yeah. 00:45:52.781 --> 00:45:55.451 I, I would like to do that, something like that 00:45:55.961 --> 00:45:56.681 at some point. 00:45:57.206 --> 00:45:57.566 Alan: yes. 00:45:57.575 --> 00:46:00.608 Highly recommend just, just to get that idea and say then the next 00:46:00.608 --> 00:46:04.688 thing for me is, is looking at Bento to, to, get the same thing going 00:46:04.718 --> 00:46:06.548 with like email trips, because. 00:46:07.963 --> 00:46:10.873 Somebody signs up, you know, right now I've just got, you know, the 00:46:10.903 --> 00:46:13.723 welcome email goes out and they've got the invitation email goes out. 00:46:13.750 --> 00:46:19.273 But I then want to separate the kind of like the sales emails from that. 00:46:19.273 --> 00:46:23.566 So something, you know, that goes out at when people do particular things. 00:46:23.626 --> 00:46:23.836 Yeah. 00:46:23.896 --> 00:46:26.446 I'm like, I want to manage that outside of my application. 00:46:26.446 --> 00:46:27.916 I don't want to write that in my code. 00:46:27.946 --> 00:46:28.906 That's like, and 00:46:30.646 --> 00:46:32.996 so also, I don't know if you've noticed, but I also have email 00:46:32.996 --> 00:46:36.176 reminders that you can create from within the application as well. 00:46:36.176 --> 00:46:38.411 So you can say like email me at 6:00 00:46:38.411 --> 00:46:40.466 PM every day to do a check in. 00:46:40.466 --> 00:46:40.766 So, 00:46:41.266 --> 00:46:41.846 Mario: Oh, okay. 00:46:41.846 --> 00:46:43.286 I didn't know that, 00:46:43.746 --> 00:46:48.026 Alan: I, I, well, that's the thing nobody else has created apart from me. 00:46:48.356 --> 00:46:49.856 So I'm like, okay. 00:46:49.976 --> 00:46:50.156 But 00:46:50.156 --> 00:46:55.286 because I can see that on Mixpanel, I'm like, okay, I need to prioritize that. 00:46:55.316 --> 00:46:59.284 Like was so I'm doing it now after you've created a basically creates an 00:46:59.284 --> 00:47:02.074 organization or joined an organization. 00:47:02.704 --> 00:47:05.104 I'm going to come up with a, like an info banner. 00:47:05.134 --> 00:47:08.914 So I'm thinking of putting it in like the top right of the dashboard page. 00:47:08.973 --> 00:47:13.170 Kind of put a box around it to say you know, did you know, you can set a, a daily 00:47:13.170 --> 00:47:16.261 reminder or something and then close it if you want, if you don't want it to go away. 00:47:16.471 --> 00:47:19.130 But I'm thinking of using that space as like a like a 00:47:19.130 --> 00:47:21.740 recommendation of what to do kind of 00:47:21.740 --> 00:47:21.950 thing. 00:47:21.960 --> 00:47:25.840 So if you haven't invited somebody, then you know, why don't you invite 00:47:25.850 --> 00:47:30.108 a teammate if they haven't created a, a a reminder, maybe remind them 00:47:30.108 --> 00:47:32.688 to do that, or otherwise just, you know, use it for something 00:47:32.688 --> 00:47:34.728 fun if there's nothing to tell them. 00:47:34.728 --> 00:47:38.508 So kind of a space that is that the top right. 00:47:38.508 --> 00:47:41.598 Of the, at the dashboard page use that for something 00:47:41.928 --> 00:47:45.468 informative or like a, did you know that kind of space? 00:47:45.888 --> 00:47:46.158 So. 00:47:46.363 --> 00:47:47.143 Mario: that sounds good. 00:47:47.203 --> 00:47:48.853 That sounds like a really good idea. 00:47:49.143 --> 00:47:51.303 Alan: But again, but mixed panel is showing me that no one has 00:47:51.303 --> 00:47:53.237 created a reminder is like ah, 00:47:54.497 --> 00:47:54.997 Mario: Yeah. 00:47:55.127 --> 00:47:57.377 Alan: should do something about that Cause right now it's just in the settings page. 00:47:57.377 --> 00:47:58.787 If you go to settings as reminders. 00:47:58.787 --> 00:48:00.474 And so I'm curious about that as well, 00:48:00.474 --> 00:48:03.654 because that's, that was a nightmare to write from a time zone point of view. 00:48:04.664 --> 00:48:05.174 Mario: Oh Yeah. 00:48:05.174 --> 00:48:07.640 I I can only imagine time-zones such 00:48:07.640 --> 00:48:09.170 in such a pain. 00:48:09.530 --> 00:48:09.680 Alan: Yeah. 00:48:10.020 --> 00:48:13.170 So yeah, obviously if you say you want it to go out at 6:00 PM and 00:48:13.170 --> 00:48:15.840 I say, I want it to, go out at 6:00 PM there, different things. 00:48:16.730 --> 00:48:17.040 Mario: Yeah. 00:48:17.400 --> 00:48:21.360 Alan: So I want to, the next thing I want to add is say, I want to 00:48:21.360 --> 00:48:23.190 send it at 6:00 PM on weekdays. 00:48:23.184 --> 00:48:24.549 Right now it just sends it every day. 00:48:24.633 --> 00:48:27.903 I want it, so you can say, send it at five 30 every weekday. 00:48:27.889 --> 00:48:32.899 So then I've got to basically check anybody who's, you know, needs a reminder. 00:48:32.929 --> 00:48:34.159 Well, what, what days? 00:48:34.159 --> 00:48:36.709 It not just, what time is it for them, but what day is it for them? 00:48:36.829 --> 00:48:37.279 And 00:48:37.344 --> 00:48:37.884 Mario: Yeah, 00:48:38.464 --> 00:48:42.694 Alan: And that changes, obviously, if I suddenly go back to the UK for a 00:48:42.694 --> 00:48:44.745 week I want that kind of to follow me. 00:48:45.735 --> 00:48:46.125 Right? 00:48:46.635 --> 00:48:50.025 So, because it updates the user's time zone when you log in. 00:48:50.385 --> 00:48:54.495 So anytime you go to the dashboard, it basically records your current 00:48:54.495 --> 00:48:55.755 time zone via the browser. 00:48:56.295 --> 00:49:01.665 So that those reminders will actually then automatically reshare module 00:49:01.665 --> 00:49:03.885 because it just uses UTC to store. 00:49:04.005 --> 00:49:08.152 So those from that point on will then be 5:00 PM in the UK 00:49:08.152 --> 00:49:09.322 rather than 5:00 PM Japan. 00:49:09.952 --> 00:49:11.722 So that should work 00:49:12.607 --> 00:49:13.417 Mario: Yeah, it 00:49:13.432 --> 00:49:14.932 Alan: all my tests, have it work. 00:49:14.999 --> 00:49:18.149 But I'm curious to know, to have some other people in different 00:49:18.149 --> 00:49:19.469 times on use it to see how it 00:49:19.769 --> 00:49:20.249 makes sure it 00:49:20.249 --> 00:49:22.019 works, confirmed that I'm not going crazy. 00:49:22.019 --> 00:49:23.849 And my tests are actually useful. 00:49:24.544 --> 00:49:24.934 Mario: okay. 00:49:24.964 --> 00:49:26.764 I'm going to, I'm going to try, I'm going 00:49:26.764 --> 00:49:27.784 to use that I'm going 00:49:27.784 --> 00:49:30.484 to do something with it then I'll report back. 00:49:31.964 --> 00:49:32.354 Yeah. 00:49:33.164 --> 00:49:38.474 Alan: So, yeah, so this, my plan for this weekend is to basically invite some teams. 00:49:38.564 --> 00:49:39.434 I've say 00:49:39.434 --> 00:49:39.674 I've 00:49:39.718 --> 00:49:45.857 I've improved the invitation system page a little bit as well, to give a little bit 00:49:45.857 --> 00:49:47.649 of information as to what you're doing. 00:49:47.641 --> 00:49:50.922 As you mentioned, a lot of the UI is some of it's good. 00:49:50.922 --> 00:49:54.372 Some of it is very utilitarian and the invitation page has one of them. 00:49:54.372 --> 00:49:54.972 It worked. 00:49:55.032 --> 00:49:59.682 And then I was like, I don't, I wasn't in the mindset to, to figure out 00:49:59.682 --> 00:50:02.007 how to fix that how to display it. 00:50:02.007 --> 00:50:03.980 So I spent a bit of time with that last night. 00:50:04.096 --> 00:50:05.836 So it now has like a description. 00:50:05.836 --> 00:50:06.826 You can add a message. 00:50:06.826 --> 00:50:10.607 There's like a default message that you can send as part of your your invitation. 00:50:10.607 --> 00:50:11.687 You can change that. 00:50:11.747 --> 00:50:14.567 And so that's all that's improved somewhat. 00:50:15.017 --> 00:50:20.672 So now as that's working I'm going to try and add this little information 00:50:20.672 --> 00:50:24.722 box in the, on the dashboard and then send out to some teams at the 00:50:24.722 --> 00:50:28.622 weekend and cross my fingers and hope for somebody wants to use it. 00:50:31.562 --> 00:50:34.502 so so it's been a, it's been good. 00:50:34.612 --> 00:50:38.202 It's it's simultaneously like, 00:50:38.912 --> 00:50:39.677 oh, this is great. 00:50:39.737 --> 00:50:43.067 I've got some users and also like, oh crap, I've got users now. 00:50:43.067 --> 00:50:44.387 Like what if nobody wants it? 00:50:44.417 --> 00:50:45.527 What if nobody uses it? 00:50:46.217 --> 00:50:50.387 So it w it's like, before that point it's anything's possible. 00:50:50.387 --> 00:50:50.687 Right. 00:50:50.717 --> 00:50:52.157 And then you're like, oh crap. 00:50:52.157 --> 00:50:53.027 No, one's logged in today. 00:50:53.057 --> 00:50:53.747 Like, why not? 00:50:55.397 --> 00:50:56.147 It's Sunday. 00:50:56.357 --> 00:50:56.657 Oh yeah. 00:50:56.657 --> 00:50:56.987 That's why, 00:50:58.307 --> 00:51:00.096 but you get a little bit I say, I 00:51:00.096 --> 00:51:04.116 don't, you know, right now it's still very early learning 00:51:04.116 --> 00:51:05.556 days and because of the people 00:51:05.556 --> 00:51:08.616 I've invited, I don't expect massive 00:51:09.396 --> 00:51:09.696 like 00:51:09.906 --> 00:51:10.566 use. 00:51:10.656 --> 00:51:10.896 Yeah. 00:51:10.926 --> 00:51:11.376 exactly. 00:51:11.511 --> 00:51:14.301 It's going to be trying things dipping into the Panetta was into it. 00:51:14.368 --> 00:51:14.638 But. 00:51:15.503 --> 00:51:16.613 Mario: And that's the way it goes. 00:51:16.703 --> 00:51:17.613 I, I 00:51:17.787 --> 00:51:21.977 find myself in a similar situation, I've onboarded a few people and 00:51:21.977 --> 00:51:27.781 I'm only a couple of people have logged on and tried it, you know 00:51:27.779 --> 00:51:30.142 I think I, I'm only aware of one 00:51:30.142 --> 00:51:35.282 person who actually recorded an episode and which I talk, I 00:51:35.282 --> 00:51:37.062 mentioned earlier in a, had a 00:51:37.167 --> 00:51:38.577 Alan: Wasn't it didn't go perfectly, right? 00:51:38.612 --> 00:51:38.882 Mario: yeah, it. 00:51:38.882 --> 00:51:40.250 didn't go perfectly, but but. 00:51:40.250 --> 00:51:40.640 he was able 00:51:40.640 --> 00:51:40.760 to 00:51:40.760 --> 00:51:42.080 record and. 00:51:43.290 --> 00:51:43.680 Yeah. 00:51:43.680 --> 00:51:48.340 So you know, in my case, I have to understand that some of these people, 00:51:48.340 --> 00:51:54.160 they already have a solution and they're just, you know, kind enough to be willing 00:51:54.160 --> 00:51:59.050 to give my product a try and just, they're interested in checking it out. 00:51:59.086 --> 00:52:03.916 And they might schedule a session here and there at some point or they might 00:52:03.916 --> 00:52:08.975 be waiting for a chance to give it a try without it being like a critical 00:52:08.975 --> 00:52:13.885 recording session that they want to do, because after all this is still beta. 00:52:13.935 --> 00:52:18.825 So I totally, you know, understand if it takes them a while to get to it, 00:52:18.885 --> 00:52:21.525 Alan: and plus, you know, it's not something well, unless you're a 00:52:21.525 --> 00:52:25.505 professional, full-time podcaster is not something that you're going to have. 00:52:25.745 --> 00:52:27.005 Okay, I'm going to use this right now. 00:52:27.005 --> 00:52:29.405 It's like, no, I'll have a, you know, there's a recording that 00:52:29.405 --> 00:52:30.905 I need to do next Wednesday. 00:52:30.905 --> 00:52:34.574 And you know, the usage patterns are going to be not necessarily 00:52:34.574 --> 00:52:36.494 predictable, regular, like, 00:52:36.592 --> 00:52:38.002 Maybe regular, but not frequent. 00:52:38.412 --> 00:52:38.922 Mario: Totally. 00:52:39.072 --> 00:52:39.893 And yeah. 00:52:39.923 --> 00:52:41.013 And we'll see. 00:52:41.070 --> 00:52:46.710 One thing I wanted to mention before we wrap it up, the problem that we had 00:52:46.710 --> 00:52:51.303 with your recording last time which, you know, today you were not able to, 00:52:51.393 --> 00:52:57.043 to get in without the recovery mode popping up was because in the, and 00:52:57.043 --> 00:52:59.023 I I've addressed this issue already. 00:52:59.037 --> 00:53:01.481 But before the leave button. 00:53:01.792 --> 00:53:03.382 When I, as a host 00:53:03.382 --> 00:53:06.952 select to leave the session, it ends the session for everybody 00:53:06.952 --> 00:53:08.602 else Well, it wasn't checking 00:53:08.602 --> 00:53:11.932 for the state of, others in the session. 00:53:11.962 --> 00:53:15.222 And so if you were still uploading it'll kick you out. 00:53:15.222 --> 00:53:16.422 so I changed that. 00:53:16.422 --> 00:53:22.422 So that now as the host, if you select to end the session won't let you, unless 00:53:22.422 --> 00:53:24.792 everyone in the session is done uploading. 00:53:25.142 --> 00:53:25.412 Alan: Yup, 00:53:25.562 --> 00:53:25.922 Gotcha. 00:53:26.112 --> 00:53:27.402 Mario: it checks for that now. 00:53:27.398 --> 00:53:32.858 And before it was only checking for my, for the local, you know, the local state. 00:53:33.458 --> 00:53:35.569 And and so that's what happened last time when I 00:53:35.569 --> 00:53:39.289 ended the session, you were still uploading and it kicked you out and 00:53:39.289 --> 00:53:40.699 it didn't get a chance to finish. 00:53:40.799 --> 00:53:41.849 Alan: Say, this is why we're doing it. 00:53:42.779 --> 00:53:45.839 This is why we're making these help you a debug, all this stuff. 00:53:46.039 --> 00:53:46.549 Mario: Yeah. 00:53:46.609 --> 00:53:47.029 Yeah. 00:53:48.679 --> 00:53:49.309 So, 00:53:49.339 --> 00:53:50.229 Alan: It's, difficult. 00:53:50.229 --> 00:53:50.589 This stuff. 00:53:50.619 --> 00:53:55.509 I mean, especially asynchronous, synchronous and asynchronous, because yet 00:53:55.509 --> 00:53:58.719 you need these things to happen, but you don't know when they're going to happen. 00:53:58.719 --> 00:53:59.019 Right. 00:53:59.019 --> 00:53:59.689 So it's 00:54:00.479 --> 00:54:00.629 Mario: Yeah. 00:54:00.629 --> 00:54:01.259 That's crazy. 00:54:01.629 --> 00:54:02.349 Alan: It's tricky, man. 00:54:02.909 --> 00:54:03.299 Mario: Yup. 00:54:03.519 --> 00:54:04.119 Alan: It's close. 00:54:04.119 --> 00:54:05.169 You just get this 00:54:05.229 --> 00:54:06.599 recording bug salted and you begin, 00:54:07.069 --> 00:54:07.549 Mario: I know. 00:54:09.469 --> 00:54:09.889 Cool. 00:54:10.189 --> 00:54:10.639 All right. 00:54:10.639 --> 00:54:12.649 So maybe it's a good time to wrap it. 00:54:12.649 --> 00:54:12.889 up 00:54:13.013 --> 00:54:13.583 Alan: It sounds like it. 00:54:13.685 --> 00:54:15.605 So if I hit stop recording now, 00:54:16.340 --> 00:54:16.760 Mario: Okay. 00:54:17.135 --> 00:54:19.685 Alan: and then, so I'm just thinking, give it time to finish 00:54:19.685 --> 00:54:19.835 up. 00:54:20.020 --> 00:54:20.410 Mario: Yeah. 00:54:20.650 --> 00:54:20.890 Yeah. 00:54:20.890 --> 00:54:21.250 That sounds 00:54:21.250 --> 00:54:21.420 good.