- Duration: 24 min
- Platform: zoom
- Source: Read.ai 01J5NYBGG481MD89Y3HGGVB3XX (https://app.read.ai/analytics/meetings/01J5NYBGG481MD89Y3HGGVB3XX)
Transcript
[Michael Houck]: yo what’s up guys how you doing pretty well pretty well starting off the new week strong so yeah feeling good Anybody have anything interesting happen this weekend? [MJ]: Lot of work. [Michael Houck]: Just a normal normal weekend. [MJ]: It was not a weekend, it was a weekday. [Michael Houck]: Same with me, same with me. [Michael Houck]: We’re getting ready to launch our new podcast and also our new membership. So we’re launching a lot of stuff over here at the same time. So yeah, a lot of work. Hopefully this week will be a little easier. I know we’ve been pushing hard the last couple of weeks. I appreciate that from you guys. [Michael Houck]: So yeah, I guess we can just jump into it. Sid, I know you’ve jumped in and kind of taken over the database stuff. Can you give me a heads up of, I know you’re just sort of diving kind of figuring out where things are at, but can you give me a heads up of where, um, what you’re seeing so far and anything that might be helpful for this week? [Sid]: Yeah. Yeah. So like, so far, uh, one, I mean, when the fit, like when the fit left off, one third of the work, total work was done by him. So, uh, from what is remaining, uh, currently I’m, I’m, uh, working with the payment APIs. I have finished a few. Of them like recurring deposit and one-time deposit API. And currently I’m starting with the webhooks thing. So the webhook thing is going good. I have set up the ng-rock for the local simulation. So that that is going good. I think this should be done in about tomorrow or by Wednesday, mid day, mid afternoon, they should be completed because from what I’ve seen, there are about seven to eight webhooks. And so yeah, I mean, it should be done by then. And after the payment module is done, I’ll have to go and check with the broadcast thing. So Rafael mentioned that he has just tested one API, which is the create book broadcast, but it is also partially working out of we have a total 17 APIs, but only one has been tested one has been fixed. So once payment one is done, I’ll have to spend some time on some time with the broadcast one, because that is the course at least once these two are done, then we can say about 50 60% the work is done. Then other modules they are just like they are quick ones actually. So those will be finished, like in the remaining two, three days. But let’s I mean, payment and the broadcast they are report, I plan to finish the payment one by Wednesday, Wednesday, and then I’ll switch to the broadcast one from Thursday onwards. [Michael Houck]: Got it. Okay. So in terms of number of APIs that are done, it’s a smaller amount, but in terms of like the ones that I guess Raphael did, and then the initial ones that you’re going to be doing, it’s like the larger one. So we’ll actually be able to make it through the rest of them pretty quickly after that. [Sid]: Yeah. Yeah. Yeah, that’s right. So the payments when, I mean, it’s from scratch, nothing was done in payments. I’m like doing it from beginning. But for the broadcast one, like some API, for example, the create broadcast, that was addressed by Rafael. But we have a couple of more APIs, like getting caster information and checking if they’re able to broadcast or not. So counting each of those APIs, we have about 17 of them. So I’ll have to test one by one, test and update each one of them. So I’ll start from Thursday for the broadcast one. [Michael Houck]: Cool. If you have any questions about business logic and areas of the code base that you’re less familiar with, just let me know. Happy to hop on a call and a huddle and chat and anything like that. [Sid]: Yeah. Yeah. Yeah, sure. So far, I mean, I had the information for the payments from Rafael, but, but, but for broadcast, I think I need to see, I’ll need some help. So I’ll drop you a message once I reach this. [Michael Houck]: Yeah, that’s fine. I’m here. I’m available. I’m, uh, I have a, yeah, I’ll be, I’ll be free on, um, on Wednesday afternoon. So yeah, we can try it. We can chat then. [Adebayo]: Sure, sounds good. [Michael Houck]: Adebayo, how are you doing? [Adebayo]: Yeah, I’m good. So yeah, good progress on the tone adapter over the weekend. Just wrapping up some tests today. And I would then create like the, I have to make a small adjustment to the UI. For testing because now we need to like see the creator and see like some of your previous tweets so that it’s easier to gauge whether the responses and the generation is kind of in line with that. So that’s like the aspect left, but that should be ready by tomorrow morning. So I’ll be sending that through by tomorrow morning. [Michael Houck]: Cool. So this week we’ll be able to do another round of testing with folks. Exactly. Great. Love it. Exciting to see this get to that point. Hopefully we’re in a good spot. Mehul, how about on your side? What’s front end right now? [MJ]: I guess from front end side, whatever API we have till now, I have integrated. I did check the couple of scenario because we have a lot of issue with the current onboarding flow that user was trying. So what I have done is I set up a basic flow till pricing, but before pricing also we have we need to fetch the data from the scaper and we have to decide that whether user based on that that count of that followers we need to show the different screen so for that I am not getting because last time when I connected with Rafael he was telling me that it’s not ready from the res one yet so once it is ready then only you will be able to get the data and you are able to display it. But I did everything, the code, everything, setup is ready. I just need the data about the scaper part, the showing the three add to the network. And about the pricing, I was just trying to connect with SEAD regarding that there was a few API missing on pricing. So once the pricing is done, and then we have one more that side drawer updating the greater information. So I’ve done the UI, I need the API for that as well. I probably need a file already created. I’ll try to integrate it so we can say that the onboarding with the new ABI was finished by the time, once everything is ready. [Michael Houck]: Got it. Okay. I guess just stay in close contact about that over the next few days. The onboarding flow, the more we can get into this release, obviously, the better. But if there are some things that Like we’ve talked about this, if there’s some things we need to wait till the group’s released next month, we can do that too. [MJ]: Yeah. So I’m just like, whenever I see there will be issues, I’m jumping, trying to see if I can just work on the group as well. Apparently both of them, because sometimes what happened, I might get blocked because of that API issue. So I will not able to find that. So I was just trying to barely work on the group as well. But main priority will be that onwarding flow. But if in case if I get some time, I’ll spend on that as well. [Michael Houck]: Yeah, that’s fine. That makes sense. [Adebayo]: Cool. Okay. And then Rizwan, I know you’ve been going back and forth with the accountify guy. Where are we at with those? [Rizwan Hameed]: Yes, I’ll go with step by step. So, first of all, the post-engagement confirmation bots are not processing any events because of an issue in the Kafka event which I believe Sid is working on. So that’s a blocker for the engagement confirmation bot processing. And then there’s another trigger which is related to the followers onboarding. So the scrapper is ready but I’m waiting for the account plus the fail requested some changes like there’s a schema related changes in the Kafka event. So, I am updating the bot accordingly. Initially, it was just to process a single object. Now, it is giving a list of objects. So, updating the flow of the bot accordingly. And other than that, yeah, so these are the two ones which are interrelated. The account verification and that’s the same account is needed for the followers onboarding bot. So these two are interlinked. So that’s from my side so far. [Michael Houck]: Cool, yeah, I guess like my ask to you guys is this week loop me in to any conversation needed and also just keep in close contact with each other so we don’t get information silos slowing us down. I think as much progress as we can make this week, let’s do it. But I know you guys have been working super hard for a couple weeks, so I don’t want to push the push the envelope too hard too many weeks in a row. So yeah, let’s let’s work normal. How far we get is how far we get this week, so. [Michael Houck]: Less. [Sid]: Just one thing, Rizwan, I know about the first point that you mentioned about Kafka event. My plan right now is to address all the broadcast and the payment issues, at least so that we are in a good position to decide a launch date. And once you’re done with that, I’ll come to you and fix the Kafka issues we have. So that could be done by, let’s say, Sunday or Monday. So I’ll reach out to you about that time. [Rizwan Hameed]: Okay. If it’s fine in the waiting, then yes, I’m good with it. [Sid]: Yeah. I mean, the plan, I mean, the first, uh, the first part is for the core of the system broadcast and, uh, payment one. So yeah, sure. [Michael Houck]: Well, all right, guys, we basically just poured in all of the tasks from the last sprint over to this one and linear. So just please, uh, as we, as we work our way through them, please mark them as appropriate. Um, but Oh, excuse me. Got some fun. Okay. Well, I’ll hop off. If you guys want to chat more, feel free. If not, then we’ll chat on Slack. [Sid]: Yeah, sure. All right. Mehul, did you check about that API? By the way, you guys are free to stay, but we can also connect one-to-one if needed, if you guys need anything. [Rizwan Hameed]: Yeah, sure. Thank you guys. Have a good day. [Sid]: Bye-bye. [MJ]: yeah I haven’t checked it probably I’ll check it now itself the you you kickstart create payment method right the sorry if if user create payment method create payment method I haven’t posted it yet. [Sid]: I just want to see the local issue. I have fixed it. I want to see where it is being used in the frontend. I have an idea. If there is any other API, please fix it. It is still coming. It is coming? Which page is it on? I have seen it. Can you show me? [MJ]: I want to make a host. Okay. [MJ]: Just let me call the word. [Sid]: Oh, man. [MJ]: here we get a call so when users come in pricing page when we call here does user has a payment method if it is like this then 404 not wrong ok does user have a payment method right? Yes does user has a payment method ok bro we are not getting api right? Ok there is no api if there is any api in its replacement then I will adjust it Yes, 404 coming. Is it there? It doesn’t look like it’s there. [Sid]: It’s not there. I’ll remove it. I have to make a new one. I have to think about it. I’ll make it. Do one thing. I’ve done it before. This is an API. Replace it with this and see. I’ll change the route. See later. [MJ]: The first response is not like this. [Sid]: Yeah, yeah. [MJ]: Okay, I’ll change it. Just change the endpoint. [Sid]: The rest is the same. Okay, so I’ll change it. [MJ]: But email ID accepted? Find if user has… You can do it. You just have to payload it. [Sid]: Okay, I’ll do it. [MJ]: I am getting a new error. [Sid]: What is it? Oh, I didn’t close it. I didn’t want to ask. Can you just send me the error once? What is the error? New route? Yes. [MJ]: api finance v1 get payment method I don’t think I have it I have the route but I don’t know where it is it says customer not found ok there is the route right? [Sid]: payment method is there in Stripe right? Did you make it? Create it? [MJ]: yes there is a payment method in Stripe for this user No, this is the first time the user is onboarding. They will check it beforehand. If they don’t check it on time, it will break. [Sid]: Okay. One second. [Sid]: Customer is not found, right? [UNKNOWN_SPEAKER]: Hmm. [MJ]: Okay, let’s see. [Sid]: I got another error, so I fixed it. Anyways, let’s see what it is. And there was another API, I showed it to you, you saw it. And it just tells me, update customer payment method. It just sends me a screenshot of where it came from So have you pushed it yet? This new layout and everything. [MJ]: Yes, yes, everything is being pushed. [Sid]: It’s being pushed in V2. So if I want to see it in Dev, or in our host. Give me a link to a branch in Vercel. I’ll give you my tablet in a minute. [MJ]: I’m going to join this. I’m going to add it here. [Sid]: ok, so this is the api? [MJ]: yes, this is the api this is the api that fills the details of the api ok, got it this is the api that creates the account Now there is an error. It is not possible to connect in live. It is not possible to connect in live. [Sid]: It is There is another API called Update Customer Payment Method. [MJ]: If this is successful then you can add it here and submit it. If this is successful then the user can fill in the details and then update it. [Sid]: ok, so you have seen the first customer payment method right? [MJ]: yes, you have to fix it if you don’t want to scan it, you don’t need to do it because if you don’t check it, you won’t be able to process it and where did you get the email from in [Sid]: the query parameter for the get default payment method? [MJ]: mihul test, which starts the onboarding flow can you read the email once? [Sid]: No reproduce going to Marama. [MJ]: No, no, no, no. [Sid]: Anyways, let’s see what happens. My email is up in the chat. [Sid]: I will tell you later. I will tell you later.