- Duration: 30 min
- Platform: zoom
- Source: Read.ai 01JBA620FFM09KK17TVPPKH278 (https://app.read.ai/analytics/meetings/01JBA620FFM09KK17TVPPKH278)
Transcript
[Ben Ornstein]: Happy Monday. How was your weekend? [Michael Houck]: It was nice. [Ben Ornstein]: Um, went home with my, God, it’s still weird to say my fiance, um, would to see my family for the weekend. [Rafael Bruno]: So, uh, it was, uh, it was really nice. [Michael Houck]: Hey guys. Hey, give me one second. All right. We got to sit here. Coming in, I think everyone’s here. Sweet, OK. So I guess good progress last week. We got a lot of stuff done, just a couple bugs that are going to linger into this sprint, but I think the most urgent ones are either done or Rafael’s wrapping up. One or two of them today. So overall, we can start to kind of look ahead at November. And November, number one goal is get groups live. That is our goal for the month. It should happen. The remaining work, I believe, is not crazy in terms of how much there is to do or how complicated it is, since we’re just doing the MVP, which is just inner circle. So super simple. There’s some UI work. There’s some backend work, and then there’s also the referrals stuff that we wanna get live in tandem with this. So I think it’s doable. And yeah, that’s our focus for the month. Mahul’s also gonna be working on some SEO optimization stuff for our site, since we’re starting to think about growth and wanna start ranking for SEO. But that’s lower priority than any work, Mehul, that you’re gonna do for the group. Groups launch. So, okay. With that, I guess, Rafael, I’ll throw it to you to start us off. Where are we at on, and let me actually share my screen so we can pull up your stuff here. UNKNOWN_SPEAKER: Where’s linear? [Rafael Bruno]: There it is. Okay. Go ahead. Okay. Regarding my work, right now I’m finishing the task of adjusting the scraper to run for engagement verification. To be one hour. I just need to wrap up some stuff here. After that, I will solve some small issues that I saw here on Slack regarding some accounts. And then I will jump into the task of solving issues. Solving issues regarding the payment notification. Fix any issues around selecting notifications for payments. I should do that and wrap up any other issues that we might have with Stripe and then move to other priorities. UNKNOWN_SPEAKER: Cool. [Michael Houck]: One thing to note, it looks like there are some additional ones relating to notifications and payments and stuff like that. So if you’re already in the that part of the code might make sense to take a look at these two and just knock them all out. OK. Um? Cool, yeah, I think the only thing Rafael for groups that you’re going to have to do this sprint is. Probably some stuff around WhatsApp and Telegram. I know we haven’t set up SMS yet. Will probably want to set up SMS in the next sprint before we launch groups, but it’s not necessary to blocker for launch. It’s just like an ideal. Case and then also. Just make sure that our referral tracking is set up. This might actually be something for mobile to do. I’m not totally sure, but we can talk about that later. UNKNOWN_SPEAKER: It’s lower priority for this week. [Michael Houck]: Probably something for next week. OK. OK. Cool, well you wanna go next. [Mehul Jariwala]: Yeah, so for my side I was continuing working on because today I was most of the time I was. Dealing with the bug that we have it with a specific account so that I resolved everything and all good on that side. And I, I mean, yesterday also I was to deal, I was just trying to look into it, like how we can optimize the way the, the, the CSS that we are loading it. So probably I’m on track as of now, I don’t have anything such that needs to be a priority, but yeah, I’ll, I’ll just try to finish the SEO one that we have, which is like a lot of ticket is there. So I’ll just try to pick up one by one and then we can get that going. [Michael Houck]: Well, yeah, I think that they’re mostly small or even extra small. I’m not totally sure. So like you get in there, you let me know. I think also it’s a new area for us to be working on. So the first couple might take a bit longer. I don’t know. But Yeah, overall, I think if we don’t get to all these this sprint, it’s not the end of the world. We should just make some progress on the SEO project though, and then the big thing is making sure that we get. Making sure that we make these high priority, making sure that we get all these groups and referral things done. That’s probably top priority for the sprint. [Mehul Jariwala]: Perfect, that makes sense. And one more thing, right? So is there any estimate from when we got the referral? Page will be ready from backend side. So I just need to have the cross testing and we’re good. [Michael Houck]: Yeah, that won’t be probably until next sprint. [Mehul Jariwala]: So no need to worry about that yet. Okay. UNKNOWN_SPEAKER: Cool. [Michael Houck]: Makes sense. Cool. Okay. Sid, take us away. You’re leading the majority of this group’s project. So give me some context here. [Sid]: Yeah, so I’m working on the scripts thing, which is 9.40 right now. That’s a bug which was causing like, which was which came in the last trend. I’m working on two things here. There are two things happening. One is the data which has a duplicate like incorrect data for multiple dates. And the second thing is I shared with this one that sometimes the count is incorrect. For example, for three days, the count will be in sequence one, two, three, and then on the fourth day, again, it goes back to one or zero or something. So this is an issue on this paper. Side. And I fixed that issue. I’m working on the first one, which was sometimes like we have for 28th October, we have 10 records. So that should not be the case. That’s what I’m working on. We I’ll just keep the last record instead of all the 10 records. [Michael Houck]: So whatever was inserted at the last timestamp, for example, on 28th October, maybe something which was inserted at 12 dot dot one because remember we talked about this over over slack sometimes the last one is like very low or very high for some reason it’s like incorrect but we want to do is take the 75th percentile of the group so if they’re like you know 10 results on yesterday’s date just take like the 7th or 8th result. [Sid]: Okay 7th or 8th record 7th record of those 10 same goes for like anything like all the records. [Michael Houck]: Yeah, because because we can’t necessarily trust like you should rank them by how many followers it says there are and then take the 75th percentile. Fine. [Sid]: So yeah, that’s what I will be working on for this one. And once that is done, I guess we can test the data on there and call this as done after finishing this on production. And yeah, after this, I’ll be working on the inner circle. Group, which is the priority for the next feature. So that one I’ll take up. I started it last time, but then had to move to bugs. But this time I’ll make sure that we complete this within the specified timeline. And launch it. [Michael Houck]: Yeah, I mean, when you get to it, let’s chat just to make sure everything’s covered by these tasks. I think that the majority, if not all of it, is covered by these. I will probably have some more we want to do sprint two. But I think we should be in a good place. And I know we’ve talked about it. So let’s just touch base when you’re ready to move on from 940 to these. [Sid]: Yeah, sure. Noted. I’ll give you like I’ll send you a message when I start. [Michael Houck]: And then Rizwan’s not here. He has something he needs to attend to today. But he gave me a heads up. He’s working on two things at once right now. One is the engagement URL logging. So that’ll finally And then the other is more robust Kafka logs, which I think will help us with debugging and is probably just a good thing for us to have. So he’s working on those. And then, excuse me, after that, he has some like, well, he has one bug from the v2 launch, but once that’s done, he’s moving on to these kind of older tasks. These are things that lingered from a while ago. And once these are done, the sort of entire scraper process for X and LinkedIn is set up and we’re good to go. And then he’s going to start moving on next sprint to work on to work on a new platform. So we’ll need to make a strategic decision about do we want to expand to Instagram, TikTok, YouTube threads, something else, probably one of those four. So that’s something that we’ll need to figure out probably next week. But exciting times, because it’ll mean we have a lot of creators and users who are asking for these things and more opportunities to work together. So very, very exciting to be getting ahead of that. And we should be able to launch at least one new platform before the end of the year. I think that’s it. I also have a couple of things. One is I need to write an FAQ stuff for the referrals page. That’s like the content that’s currently missing that we have put placeholders in for. And then for our new SEO blog, I need to set up a page for the FAQ so we can move that over as well. As part of this sort of SEO optimization project, we’re moving from Strapi, which is expensive and also just a little hard to use, to this notion-friendly, kind of user-friendly tool called Feather that my friend runs, and he is the one who’s creating the SEO content for us. So it kind of makes sense to do it all in one place. It’s also much cheaper. So we’ll do that later this sprint too. Anything else big that we want to talk through? Or if not, I’ll give you guys the time to jam on stuff yourselves. I think the one thing I would flag is we seem to have a lot of issues still with people onboarding. So probably over 50% of the people who have signed up over the past week or two are having some sort of issue. The issues vary, of course, but just the hit rate of issues is very high. So it’s a bad first experience for them and it also really slows us down. So I think, let’s just think about why that’s happening and if there’s anything we can do to sort of plug the holes of the boat, so to speak. Because otherwise Ben is gonna be sending a million messages in Slack to you guys and disrupting your workflows. So yeah, I guess just let’s put some thought into that and see if we can improve anything on the onboarding side easily. Cool. Okay, I will leave you guys to it. If there’s anything else you wanna talk through, but I’m gonna head off. [Sid]: So see you guys on Slack. [Rafael Bruno]: See you, Hauke. See you. Ben, getting this topic that Hauke commented, could you please write us a topic, a list of topics of common problems that users faced while they are trying to onboard? [Ben Ornstein]: Yeah, I mean, it’s mostly, the problem is I don’t fully always know what it is, because it’s always different issues. Like one guy was, oh, well, I just want to close the loop there. So thanks for all your work on all this, guys. I really appreciate it. I hope you don’t see my messages and be like, oh, another one from Ben, damn. No, no. I hate sending them and I hate disrupting your workdays, but because these are the users that are about to onboard or have just onboarded, it is important that we go ahead and get them live. Again, when I send these messages, I hope I’m not bothering you. [Rafael Bruno]: Although we totally understand people are trying to pay for the platform that pay us, so it’s important that That’s a good way of thinking about it. [Ben Ornstein]: Um, but so for this guy that was trying to be the amplifier, um, move, move. Are he, is he set? UNKNOWN_SPEAKER: Is he ready to go? [Mehul Jariwala]: Yeah. The one, the one with you, uh, uh, I guess it’s all good. I tested the account. Uh, but Rafael, can you also just check once you remember? I will check and I’ll let Ben know. Yes. Yeah, make sure we confirm both end. UNKNOWN_SPEAKER: Got it. [Ben Ornstein]: Yeah, so that guy’s been waiting for a little while. So we’ll hopefully get him live. And then, yeah, the latest one I sent you guys was the new one that I think it was towards Sid. But yeah, so yeah, Rafael, whenever you can get a chance to look at that and let me know, please do. OK. But yeah, I’ll leave you guys to it, just other than thanking you for all the help and quick responses. It does me a lot of good. [Rafael Bruno]: I appreciate it. Sure. Now about another topic. Do you guys have any issues that you want to discuss? [Sid]: Just one question, and I think this might be the right place to ask. So this guy, the issue that this guy reported recently about URL does not contain information. So I see Rafael, we are calling this function URL belongs to Gasterk account. If his name is not there in the URL, we will throw in, like we intend to throw in as an example. [Rafael Bruno]: Basically we do, we do two things. Let’s say that the user has a profile on X that is X If that user tries to share a post with x.com slash seed123 slash post title, it will not work because that belongs to another account. The same goes for LinkedIn. But for LinkedIn, we have some URLs that they do not contain the profile name. The account name. So on the code, we go on another path. We scrape the link that the user is trying to send to try to find the account that is sharing that information. If that account is not the account that the user is trying to share the broadcast, then we block. [Sid]: But isn’t this bad approach because I may use any username on my Twitter account in the URL, whatever I want, I may use s.i.d, right? But when I use megaphone, then as a user, it will block my posts from going through. Because that’s what the problem is right now that user, he has the same like he has the Twitter URL, but because the name is not present in the URL or it’s broken into two pieces and separated by underscore the From x. Yeah, yeah, then you the URL is because that’s why x has one specific URL that they share. [Rafael Bruno]: They’re not like LinkedIn where they could have like two URLs. If the URL that the user is trying to share does not contain the information of the account of the user on X, it means that that’s from a different account. [Sid]: And we should not allow the user to move forward. The link is pretty much simple, x.com slash the username. What? The link is pretty much straightforward. It’s x.com, like https.x.com, and then followed by their username. So, this should go through ideally. Can I see the task? [Rafael Bruno]: Could you please tag me on the thread? I think it will be easier for me to examine. It’s the latest. [Mehul Jariwala]: If you go to the megaphone, generally the last message, it’s about Ravi. So, that is the one. [Sid]: My whole point is that whatever approach you are taking, it seems that we may run into issues again in the future. [Rafael Bruno]: Okay, what is the URL that he was trying to share? [Sid]: This is their account, this thing URL. Let me see what payload did they pass. [Rafael Bruno]: You want the broadcast URL, right? UNKNOWN_SPEAKER: Yes. I think I’ll have to find it. Give me some time. [Sid]: I’ll send you over Slack. [Rafael Bruno]: But I was just trying to convey the message that whatever, if they have something else in the URL, then it will not, then we may have- Basically, if the URL does not contain the account information, we should not let the person share that URL because that person could be sharing from another account that the user is not paying. UNKNOWN_SPEAKER: Yeah, agreed. [Sid]: I get your point. But I’m just saying that we may get something we may get these errors again and again if we go this route of validating whether the account belongs to them there may be some other approach which may help us to [Rafael Bruno]: validate if the account actually belongs to them or not because this way I so this is something you can only validate if the account belongs to the user to that specific account that the user is paying if we validate validate the URL. There is no other way that we can validate that. [Sid]: Because I myself do this on many platforms. I have that username, something else, and my account name is something else, right? So from that experience, I’m saying. Maybe I don’t, I don’t understand you. I said that in my experience, I have done this. For example, on Facebook, my name was something, my name was said but the username in the URL, right? I modified that to be something else long, like six to seven years ago, because I just changed it to be… Oh, you’re telling me that you changed your account name to another thing. In the URL, not my name, like in the URL. [Rafael Bruno]: So let’s say your username was seed123, and you changed your username to seed456 that’s what you’re saying no no the name remains seed123 the name in the url right facebook I think that they had this feature uh they allowed [Sid]: you to customize your url in the the username in the url long long time I think facebook had it and I think it’s called permalink or something even instagram has it uh I’m not sure if they like if they actively have it but at least from what they do, they did have it sometime ago. So it’s called permalink or something. So you can modify whatever name you want in the URL. And when the visitor on your profile, they copies the link, they’ll see some, they’ll get that thing. And then they can just access your, your LinkedIn account or Twitter, whatever social media. [Rafael Bruno]: Okay. If we investigate and we see that this user did that, then we need two approaches. We either need to change something on the database or ask him to try to find another link. I don’t know. But right now, we don’t have a way to deal on the back end with that kind of situation where the user has one account with one username, but the links that the user shares has another username. Or another alias or something. [Sid]: I’ll give you the name. I mean the URL which they shared and then I think that will help us to decide what to do with this error. I can give you that on chat. [Rafael Bruno]: Oh, please just tag me on the thread that you found. And I will be able to check. [Ben Ornstein]: Yeah, I’m looking for it. All right, guys, I’m gonna head out, but please let me know if I can help out with anything and appreciate all the help. Okay, sure, Ben. UNKNOWN_SPEAKER: See you. Oh, yes. [Rafael Bruno]: Oh, interesting. I’m looking for it. I found the issue here. The user didn’t pass the URL. And the other payload that he sent has the correct URL. There is no issue with that user. [Sid]: So he passed wrong, no URL, is it? UNKNOWN_SPEAKER: Yeah. [Rafael Bruno]: Already tagged middle on the situation. UNKNOWN_SPEAKER: Yeah, yeah. [Sid]: Then we could have front-end validation for this. [Rafael Bruno]: Okay, fine. Okay. Do you have anything else to discuss? No, that’s it. [Sid]: Thanks Rafael. Okay. See you soon.