Speaker 1: 0:01

hello friends, it's uh yarrow and adrian from the friendly show we are back after visiting all the conferences, after doing so many talks with the different wonderful guests, and now it's just us, and I actually missed talking to you yeah, hey everyone, how's it going?

Speaker 2: 0:21

we actually came back from the conferences and, uh, another bullet point I want to put after the conference on my schedule is chilling out, you know, just being with the family and just you know, uh, going back into a routine, because I kind of miss it after all of the events are you planning any other conferences this year? No, no more this year. Uh, no more conferences, we'll see about next year. I haven't, you know, put anything. I actually have just one in my calendar, uh, but probably we'll do less next year, we'll see.

Speaker 2: 0:54

So before talking to you, I was just checking the rubyconferencesorg website and the next conference is ruby banitsa conference 2024 in sofia bulgaria in december yep, yep, yep, yeah and uh, I had the impression that like hey, I, I've already been there this year yeah, I think it's a smaller kind of conference because they organize they usually organize the user group in in sofia, um and I think they want to make a bigger one, something between a meetup and a full-fledged conference. That's my impression. I'm just paraphrasing. Don't take my word for it.

Speaker 1: 1:37

Yeah, two conferences, two editions of the same conference per year is quite a lot.

Speaker 2: 1:44

Yeah, it's a lot. It's a lot.

Speaker 1: 1:45

It's a lot to do, it's a lot to organize, yeah, and to go so I've been following avu on socials and I see that every week like new blog posts are popping up most recently, I think about the meta tags and I see you're getting the guest authors for the blog posts. Can you tell more about it?

Speaker 2: 2:07

Yeah, sure, so we started. So we are building so many cool stuff and we are, you know, sometimes running into these scenarios where you know, we kind of we figured out some things and we thought, you know, some other people might need it, and we are, you know, some other people might need it, and we are, you know, writing some, some content about it. And, um, we have uh exekiel, uh from south america, who's helping us with uh, with that, and he's writing most of the articles. Uh, he did an amazing series on active storage, actually, like how, like you know, the basic of active storage with S3, and then how to add a CDN, and then how to actually just use a CDN without like impacting your rail server, and now the meta tags, which we've used for a long, long time, and we have a few others that are coming in the next following weeks as well. So, yeah, I think the content is something that we want to give back to the community and something that will help us in the long run as well.

Speaker 1: 3:12

Yeah, talking of the Metatext Jam, one of my favorite moments from the Rails World Conference was when we were riding on a bus and the guy sitting next to me says hey, you look familiar, familiar. Stop, you made a video about my gem, about the metatext gem. Oh that's awesome.

Speaker 2: 3:31

I didn't know he was there. I just dude, I wanted to meet him. I I've been using that gem for a long, long time. It's, uh, one of my go-tos whenever I build a public app.

Speaker 1: 3:39

So that's a nice guy.

Speaker 2: 3:41

I think his name is metrosh tefeluk that's a nice guy, I think his name is metro stefe luke.

Speaker 1: 3:50

Okay, awesome, next time ping me, give me a, give me, tell me about it yeah, um so, uh, I see the as x x, xxl, xxl, xxl, yes, yes made, uh, yeah, a series uh about active storage. I'm'm just looking at their blog right now Friendly ID what's new in Rails 8? Talking of what's new in Rails 8, what excites you the most?

Speaker 2: 4:13

I think that's an interesting question. I think what excites me the most is ownership. I feel that the authors, like DHH and the team, they actually, you know, now they figured out okay, let's make this better because we can. We have a few areas where we can improve, like the team and the community as well, and I think this is part of ownership. You know, solid everything. You know Kamal and all of the new cool additions these, just you know, set a mark that you know Rails is here to stay. It's going to uh, improve, like the defaults is going to help you actually, you know, build a hello world but actually get to a ipo as well. So, um, yeah, I think, uh, you know, there's not one particular feature that I was mostly expecting, but seeing everything that's happening, you know, like Rails 5 to 6 was, eh, 6 to 7 was a little bit better, but 7 to 8, this is a great, freaking release.

Speaker 1: 5:14

Well, no, for me, like Rails 4 to 5, little change. I think they added active storage and action text. Rails 5 to 6, the biggest change was replacing SP Rockets with Webpack, and this was quite awful. My least favorite version of Rails is Rails 6. Rails 7, wonderful, moving back to SP Rockets and having Hotfire. So Rails 7 is my favorite version of rails, and eight I mean it's mostly infrastructure changes. So, uh, like how you deploy your apps or like what the background tooling is like, uh, for processing, for cache. So not so visible in the like daily development process.

Speaker 2: 6:11

Yeah, no, I agree, I agree. I like the solid frameworks, like solid cache especially. It solves so many problems. Like you can just use your, you know, sqlite or even Postgres database if you want to. So that's amazing. And Solid Q another great, great release. It really solves a lot of problems that many people had over the years.

Speaker 1: 6:35

Yeah, and having all the Solid frameworks, you kind of don't need Redis anymore. And you can have just one database and I've already been playing with it with Super Rails, so I kind of did not include Redis at all. I just did all the job processing everything in Postgres and I was using like gem good job kind of background jobs for Postgres and yeah, the app works well without the redis that's awesome.

Speaker 2: 7:09

Did you ever, did you also use a solid cable? Do you also use that?

Speaker 1: 7:14

uh, no, I think I put the postgres as the cable processor okay, okay, that's awesome yeah yeah, definitely, definitely.

Speaker 2: 7:26

What's your favorite? What do you think about authentication?

Speaker 1: 7:30

uh. So I recently made a video about authentication zero, a gem by lazario nixon, where he basically built everything uh rails authentication generator could want to have included. So maybe I mean there's quite a long way to go, I think, for Rails 8 authentication to have all the same features, but it's still a long way to go to be able to use Rails 8 authentication generator in production. It's still a long way to go to be able to use Rails 8 Authentication Generator in production.

Speaker 1: 8:07

Let's say this way so, for now I'm going to prefer other tools, but what I really like about Rails 8 Authentication Generator is that it is kind of session-based, so a user has many sessions and you have the current session and you deduce the current user through the current session, so it is easy to see, like all the places where you are logged in and log out remotely. I think it's a good approach.

Speaker 2: 8:36

I agree, I agree, I love that as well. Um, so recently we changed the registration flow on on avo HQ and, uh, that io and we are using device there and it was kind of a pain. I, you know, we we spoke a little bit about it but you know, I I kind of I probably approached it the wrong way initially. But one thing that I wanted to say is, like I heard DHH in one podcast say, like you know, the registration is something for the reader to exercise and you know, I kind of like I would love to have something out of the box. You know some simple, you know email and user authentication registration. But it's so true, once you want to get into something a little bit more custom, it just takes, you know, so much effort. You know I have to think on so many things. So it's good to have like training wheels, but once you want to get off of them, it's not an easy task to do. That's what I wanted to say.

Speaker 1: 9:42

So I just tried creating a new account on Av and I see that first of all you just ask for the email and the user should confirm his email to proceed yeah, yeah, and then and then, after you confirm the email, you go through what we call like the regular registration.

Speaker 2: 9:58

You know, it's kind of like an onboarding session where you know we ask for your name and a few other things and then we create the account and, you know, redirect it to the dashboard or something and did you override the device controllers or did you go another approach?

Speaker 2: 10:14

that was the initial you know idea. It was just, you know, just ignore this here, just ignore this. There. I was telling device like, okay, now switch it like this and then redirect there. But you know, um, hold this param into memory like, oh my god, that was so freaking difficult. And then we had to talk and you said like no, no, just use a different flow. And then, like you, you, you build your own, you know email registration form, and then you, then you send the email, you set up the confirmation and everything and then let the user go through the regular registration, the regular device registration process, which was actually the way to go from the start.

Speaker 1: 10:54

Yeah, so from my experience it's better not to override the default registration flow in device. And if you want to have something before, just do it in a separate model. And, uh yeah, don't try to override the device controllers themselves too much yes, yes.

Speaker 2: 11:12

Well, you know when once you get to into something more custom, then you know you just can't help it like I. I know that you know most apps need something and that's it. Like you know user and password and the regular you know uh stuff. But sometimes you want a little bit more. But I understand why it's difficult to override. I understand that, you know.

Speaker 1: 11:33

I accept that it's not like I don't really understand. So you first made it so that the user just submits his email and he has to confirm to continue. Why don't you just use a device confirmable that the user kind of creates his account but he cannot log in until he confirms his email?

Speaker 2: 11:52

Yeah, we want to make it as frictionless as possible. So you have to, in order to confirm to use confirmable, you would have to. The user would have to use order to confirm to use confirmable, you would have to. The user would have to use a password and enter their name and then other things. And we want to capture that after the actual email registration process, so after we capture the email. So the user is, you know it's a little bit more invested and they will want to go through the full onboarding flow yeah, and also with the requiring like email confirmations.

Speaker 1: 12:22

I've had some uh problems that uh, it can be in the spam folder of the user and he can not access the email in an obvious way, so he might not be able to even log into the app we understand that.

Speaker 2: 12:39

Well it's. I think it's a little bit more obvious this way, because the user just entered their email, so the only thing that they can do, so the page tells them like go into your inbox and click that link, because otherwise, you won't.

Speaker 1: 12:54

And don't forget to check the spam folder.

Speaker 2: 12:55

And don't forget to check the spam. But login works in the usual way with uh email and password, so you know. You know that I hate magic log links. I don't like them. They just they're just so freaking disruptive. That's how I feel about it, so I don't want to do that.

Speaker 1: 13:12

So the users can still log in with the email and password and uh, I also see that you keep posting links to the other office hours and I think I watched one of these videos um, how's it going in general? Like are you getting value from it? Are the people that join getting value?

Speaker 2: 13:33

yeah, it's so cool, uh, it's and it's so fun, um, so I think we're one of those projects that we like to communicate what we do a lot with, uh, our users and you know our customer base. So, uh, every time we do a release, you know, I go to that video where we talk about what changed, what was fixed, what was broken, what was added and so on, and then we, we are transparent, we have like our roadmap public and everything else. But we wanted to do a little bit more and we wanted to, like, actually talk to the users a little bit more and we added these office hour sessions. We just said, okay, let's see what happens. We'll do an office hours. We put up like a Google form or something and people I know 10 people signed up and what we do there it's generally like once every two months maybe it's not very regular and we talk a little bit more about what we're working on right now and we show people a little bit, a little bit more of what's behind the scenes, and sometimes I show like quick tips and then we do this.

Speaker 2: 14:38

Then we have a conversation. We ask people okay, what's your feedback? Would you use this? Would you use that. Do you have other problems, other issues, other things that you'd see improved? You'd like to see improved with Avvo? And we have this conversation that we generally it's a little bit difficult to have on Twitter or on GitHub repos or on Discord server. It's face-to-face. We talk about things, we show things, we have access, I can share my screen and I can show them. Okay, this is what happens. So I think, overall, it's a very positive feedback. I think that people are getting value as well. We are getting value as well, and we love being in touch with, uh, with our users and and customers. So, yeah, I know you were thinking about doing some office hours yeah.

Speaker 1: 15:28

So last week I asked uh in socials like would people be interested in joining superl's office hours? And uh, my idea was that we could just talk about any Ruby on Rails related problems people that join have. So they can just ask any question or we can discuss anything. I might also have some specific topics, like today we are going to talk about multi-tenancy, or today we are going to talk about Hotwire Native multi-tenancy, or today we're going to talk about hotwire native. But I think I'm going to start with just like open questions and see how it goes that's awesome.

Speaker 2: 16:07

You know what you could do. You could do something like okay, what? What did I release in this all in all this period? Like you know you you talked about turbo native or you know authentication and like you can start with start with that if people have any questions about that, because that information is still fresh in their heads and they're still thinking about it. So that could be a good start. But I think this is a cool thing you're doing for everyone, for your community.

Speaker 1: 16:33

Yeah, I'm thinking of announcing the first workshop. No, I think not workshop, but meetup or office hours this week. That's awesome.

Speaker 2: 16:45

That's awesome. You should do that. Speaking of Super Rails, how is Super Rails Pro going? Yeah, I've been seeing some changes there.

Speaker 1: 16:54

Yeah, so I've been doing Super Rails for like four years now. So I've been doing Super Rails for like four years now, and just this summer I launched Super Rails Pro. So some videos are available only to paid subscribers and these are usually videos that I spend the most effort on like researching for, so like how to do something specific to like french legal stuff, like french banking apis or invoice apis or hotwire native, so like more unique topics that require a lot of research. Yeah, yeah, I've got a few subscribers that I'm very thankful and grateful to. They keep me really motivated. That's awesome that's I.

Speaker 2: 17:48

I bet that's a great feeling to know that people you know um, I don't want to say appreciate the work is I? I'm sure that everybody, of most a lot of people, appreciate your work, but you know they are, you know, basically paying for it and I think that feels really nice, right, yeah?

Speaker 1: 18:06

uh, it's a wonderful feeling and uh like I'm kind of trying to direct uh more visitors to super railscom than to youtube, so I release all the videos uh on super rails much earlier than I do on youtube that's awesome.

Speaker 2: 18:24

I didn't know that. I didn't know you should have that on the banner or somewhere. I don't know if you have it or not. Like you know, check super railscom for early, early. Do you have any any release schedule, like new video every monday or something?

Speaker 1: 18:37

or you just uh wing it and and whenever you have something you put it up yeah, I know uh, others have uh regular release schedules, like one video per week, like one pro one regular video. Uh, I don't have a release schedule. I uh record something and I put, put it straight out to super rails and on youtube. I do it like every few days. So, like on youtube, I try to have some distance between the videos that's awesome.

Speaker 2: 19:09

That's really good. Tell me a little bit about hotwire native, because it's super hot right now.

Speaker 1: 19:14

I know it's you know why is hot.

Speaker 2: 19:17

Yes, exactly exactly. It's very, you know, sexy to talk about, but I feel like because I've been trying it out a little bit and I feel like there are still some unknowns there and this really feels like something that you put a lot of research into it have you used it also professionally?

Speaker 1: 19:33

oh, yeah, so, uh, the whole point was that, uh, around the may, a client that I was working with said that I need a mobile app for my FinTech platform and Yaro find a way. So the obvious approach was to go with Hotwire Native and I basically had an app in test flight. It's like the pre-release uh version of an app that people can already download and use on their phone and test it out. So I had this in like three weeks since I started and then took the most time to just make the app look good on a small screen.

Speaker 1: 20:27

So you need to write responsive CSS, because the whole app was just built for giant screens of the developers that were working on it, so I put a lot of effort into make it need the like the app itself mobile responsive, but otherwise the hotwire native part wasn't that hard. Um, the app review part was more complicated so we had the authentication with the email and with google and they, like AppReview, said that they also require authentication with Apple and also they said that you got a paid version of the app so you won't be able to pay us. The app store cut and I was debating that it is impossible to subscribe on mobile. It is a reader app so people can subscribe only on the web but on the mobile. That it is impossible to subscribe on mobile. It is a reader app so people can subscribe only on the web but on the mobile they can only log in.

Speaker 1: 21:25

They cannot even create an account.

Speaker 2: 21:27

And I think Basecamp does the?

Speaker 1: 21:29

same with their apps, so you can only log into an existing account on mobile. But you can create an account or you can pay on the web.

Speaker 2: 21:40

Yeah, it's the age-old story.

Speaker 1: 21:44

Yeah, but with Hotwire Native, the barrier has never been lower to create mobile apps as a Rails developer and, frankly speaking, you don't really need to know swift. Yeah, to release an ios app that's great.

Speaker 2: 22:04

That's that's great news. Um. Do you have this covered in your hotwire native slash, turbo, native now um series or videos yeah, so I've got like around 15 videos so far.

Speaker 1: 22:18

The first like seven of them, I guess are about Turbo Native, so I would kind of disregard the iOS part of these videos. But the Rails part is still valid, and my latest videos are all about Hotfire Native.

Speaker 1: 22:35

So the difference between Turbo Native and Hotfire Native is that Hotfire Native has a lot more boilerplate already included in it so the setup of a new iOS app or Android app is much easier, so getting started is easier and the main time consuming part will be on making your rails app look good on mobile and maybe use some native components so my last few videos about are about like using different types of native rich components previously strata components yeah, yeah.

Speaker 2: 23:13

So basically, if you have the app responsive, it's, uh, it's.

Speaker 1: 23:17

If it's already responsive, half of the work is done, more than half you then just add some behaviors that, like this is visible only on the web, or this is visible only on mobile then you add the like tab navigation on mobile so you select which tabs you want to, what are the names of the tabs going to be and where they're going to lead. And, yeah, you basically push this app to test flight. You test it on your phone, you go through app review and you launch the app.

Speaker 2: 23:57

The barrier has never been smaller I remember, I remember in toronto one, one night after we came from the conference we used you put avon on native and that was so cool. You know it's to see it in the simulator and work and you, you, you know that was awesome, that was awesome. Yeah, it looks really cool. But there's another thing I want to ask you what's the deal with money gun, because I've seen you talk about it and I think it's something sweet yeah, so most of the consulting clients I've worked with over the years they kind of have multi-tenancy applications.

Speaker 1: 24:37

Basically, multiple organizations can have people that can log in with different roles and have access to all the data within this organization. So I created a couple of videos about multi-tenancy in the past how you can set it up. There are also a few gems, like Nelia and and apartment is another gem apartment is. If you want to have separate databases for each, why?

Speaker 2: 25:17

I mean not why, but you know there's such a small subset of apps that really need that, right? Yeah? Yeah, I think apartment was the popular approach around 2015 yeah, us engineers, sometimes we jump for these cool stuff, these cool things so fast.

Speaker 1: 25:37

Yeah, yeah, okay, so yeah so I made this first video. It is episode 115 of super rails about creating multi-tendency from zero, and I wanted to go deeper and actually turn it into a boilerplate or an example application how you can have the whole. Like users that can belong to multiple organizations with different roles and inviting users to organizations work. So I cannot build this boilerplate application. I wrote a lot of tests on it and people can now either start new applications based on it or use it as inspiration for how they build their multi-tenancy. There's also like Jumpstart or there's Business Class Kit by Joseph Stibney.

Speaker 2: 26:31

There's a business class kit by Joseph Stibney.

Speaker 1: 26:32

There's a bullet train, all of them, I think are good, but this is kind of a very. Those are kind of SaaS starter kits, but this is like a multi-tenancy starter kit, so it doesn't have anything except multi-tenancy, at least for the moment.

Speaker 2: 26:48

That's awesome. I was thinking about something like that, because not all apps are SaaS apps, right? Some are internal tools, some are, you know, projects that you build like POCs or whatever. Not all, but most of them, you know you'd want multi-tenancy, you'd want, you know, a good registration flow, you'd want some things set up out of the box for you, uh, but they're not all sass. So I think it's a great, freaking idea that you're putting this out there.

Speaker 1: 27:18

We do, we definitely need this, uh, at avon yeah, and a couple of days ago I had the first uh community contribution to money gun. So guy found some test that was passing in the wrong way and fixed it.

Speaker 2: 27:35

That's awesome, like it wasn't even something visible on the screen. It was like I checked out your tests and you know something was broken there. You weren't paying attention. Let me just fix it for you. That was just awesome.

Speaker 1: 27:46

Yeah, that truly made my day. Yeah, that's cool, that's cool.

Speaker 2: 27:50

Yeah, I'll definitely check it out, because we need something like that.

Speaker 1: 27:52

So yeah, thanks for putting this out. There Are you?

Speaker 2: 27:56

thinking about making it a steady release cycle, building it as a product, or are you just winging it for now and just let's have it out there and see what people say about it?

Speaker 1: 28:09

So I have a couple of SaaS ideas I've I wanted to pursue for quite a while, and I'm going to use money gun as a boilerplate based on which I'm going to launch these apps and maybe improve money gun along the way, and people can also use it that's awesome, so like we have uh uh jumpstart. That is a great tool. It's like a premium uh not open source, uh boilerplate, and this is going to be kind of an open source boilerplate that's awesome, that's great yeah, yeah, I'm talking of non-sas apps.

Speaker 1: 28:50

Uh, so I've been playing around with Avvo last week Actually it's a fun story so last week I tried to list all the Ruby on Rails front-end component libraries. Okay, so, I wrote a blog post about them and so far I think I have eight or nine component libraries in my blog post and that's a lot like eight or nine different component libraries in Ruby on Rails.

Speaker 2: 29:18

It's a lot yeah.

Speaker 1: 29:22

So that's kind of a race to build the best one that everybody will use.

Speaker 2: 29:27

I feel the race. I feel the race, yeah.

Speaker 1: 29:30

So okay. I've got like a list of tools. Maybe I should build a directory and this would be like one of the categories in the directory. So I thought, okay, maybe, like I don't want to build the front end or whatever, maybe I just use avo, and avo is going to be not like just an admin part, avo is going to be what people see yeah, that's so.

Speaker 1: 29:53

That's why you were thinking me yeah, so the idea is that you just like the admin, kind of just puts links to the websites and the tool gets all the data about them, takes screenshots or display open graph images, and you can put different tools in different categories. And, yeah, just build a directory based on Abo.

Speaker 2: 30:20

That is awesome. Is that public? I want to see it.

Speaker 1: 30:24

I didn't even push it to GitHub yet, but yeah, I think I'll make it available this week.

Speaker 2: 30:31

That's awesome. That's awesome. Yeah, we can host it on our end if you want to. So yeah, I want to see this up there.

Speaker 1: 30:37

Yeah, yeah. So I kind of like the idea of having, like other MVPs and other directory MVP.

Speaker 2: 30:47

Yep, yep, yep.

Speaker 2: 30:48

We've been playing around with that idea as well. We have a couple of ideas, we have a list of things that we can build Me and Paul and also Lucien, and we're thinking about something like that. We want to build. So we want to rebuild the demo website too, because we have a few of them now. It's not just the one AVO demo website. We have one for ticketing, one for Kanban, one for audit logging, have one for ticketing, one for Kanban, one for audit logging, so multiple things. So you want to build kind of this directory, kind of structure, basically a directory. Where could we find something like that?

Speaker 1: 31:20

My directory can host links to your directory?

Speaker 2: 31:27

Yeah, that makes sense.

Speaker 1: 31:28

Why don't they build a directory of directories?

Speaker 2: 31:31

Directory as a service. Is that a business?

Speaker 1: 31:35

I've actually seen people post on Twitter around like yeah, building directory, builders, so like you can buy their tool and create a directory and build your own directory.

Speaker 2: 31:51

Yeah, that's cool. That's really cool. Tell me whatever you need, whatever I can do to help. That sounds like a super fun project to build yeah, black Friday is coming up.

Speaker 1: 32:05

Is AVO going to do any promotions?

Speaker 2: 32:10

yes, we are. We're just uploading the. I was just working on that today. Uh, we're gonna have 15 off perpetually, which is something that we don't really do that much. It usually we just discount the purchase price, but now it's like 15 off year over year, so that's a pretty good deal. We've had quite a lot of people purchase ava last year, so it seems that people want black friday with ava as well. Are you doing something with uh?

Speaker 1: 32:43

I'm uh thinking okay, uh, I don't really know what the best thing to do is. So if you, the listener, have any ideas of what a Ciprell's promotion can be, let me know.

Speaker 2: 33:01

But I was thinking of making a lifetime subscription option for Black Friday maybe yeah, I think so, and you can have it discounted at, I don't know, maybe 350 or 450 or something like that, then that sounds like a a nice, a nice deal. That sounds like a nice deal to me. Yeah, uh, definitely, yeah, everybody view their listener. Please send in your feedback. Yeah, and for ava as well. If you think about the cool thing I was thinking about, you you could do, like you know, office hours for, like as a service, and you can, you can try and have like you know Black Friday deal, like okay, this is how much, and you can have me, like for a few hours or something to talk to your team, something like that, on like Turbo Native or something. Yeah, maybe, yeah, what's okay. So what are you doing, uh, next? What? What are your plans? What? What are you focusing on next, uh, to this end of the year and starting of the next one?

Speaker 1: 34:08

yeah, so uh talking of personal projects, it's uh like super rails uh, as usual. So just uh releasing videos about uh interesting challenges I have recently uh solved uh. So it's number one. Number two I think this week I will finish with the uh other directory builder. Number three, maybe something on MoneyGum. I mean, I've already released everything I had in my initial vision the multi-tenancy boilerplate and maybe something else will come up.

Speaker 1: 34:46

Otherwise, I am thinking of what my next work should be. So now I'm finishing work with my long-term client that I've been working with for like a year and I'm planning to post on Twitter. Actually, I'm planning to post on Twitter actually after our call that I'm open to opportunities.

Speaker 2: 35:18

That's awesome. So you're available, that's awesome. So, if there's anybody out there that needs a very skilled developer, slash, mentor or educator as well Hotwire native and hotwire in general like you're their man, that's awesome. That's awesome to hear. Uh, yeah, I think you won't be on the market for too long. So, uh, the good thing that you you've mentioned that. Yeah, looking forward to seeing it on on twitter as well yeah, okay, okay, adrian. Cool. Yeah, it was great catching up. I don't know when we'll see each other next time.

Speaker 1: 36:02

We don't have anything else planned. Well, it's definitely going to be on some conference.

Speaker 2: 36:07

Maybe or maybe not, who knows? You never know. Maybe we'll make a trip Looking forward to seeing you a trip.

Speaker 1: 36:13

Yeah, looking forward to seeing you next time.

Speaker 2: 36:15

Cool. Thank you everybody for listening. See you, Bye-bye, Bye.