I Built a Link-in-Bio Platform… Then I Asked: “Why Would Anyone Come Back?”

On July 11, 2026, I started building a project inspired by link-in-bio platforms. The idea was pretty straightforward: Create a profile → customize it → add your links → share it. So I built Rizzzler. And right now, it has 11 users. Yep. 11 😂 Not exactly the kind of number you'd put on a startup pitch deck. But those 11 users actually made me think about the project in a completely different way. The problem I noticed 🤔 I started looking at how people were using Rizzzler. And I noticed something: People would create their profile... Then disappear. Some wouldn't come back for a week. Some wouldn't even check the app for weeks. And eventually I realized something obvious. Why would they? Rizzzler was primarily a profile website. Once you've created your profile and shared your link, what reason do you have to open it again? You don't. That got me thinking: What else can we actually do with a profile? I didn't want Rizzzler to become something people set up once and completely forget about. I wanted the profile to actually do something. And that's where I got a pretty crazy idea. What if Rizzzler became more than a profile? I've used services that let you log into other applications using their account. For example: Sign in with GitHub. That got me thinking: What if Rizzzler could do something similar? Instead of Rizzzler only being a place where you create a profile... What if developers could use Rizzzler as an identity provider? And suddenly I had a new idea: Sign in with Rizzzler That was probably the craziest idea I've had for this project so far. And I decided to build it. I built my own OAuth 2.0 system 🔐 I started building the OAuth 2.0 mechanism, the developer-side integration, and the documentation. I also created a developer docs page so developers can understand how to integrate Sign in with Rizzzler into their applications. I've tested the mechanism locally, but there's an important distinction: It hasn't been properly tested by a real third-party application yet. So I'm definitely not going to call it some battle-tested authentication system. The core is built. The docs are there. Now I want people to actually try using it. If you're a developer and this sounds interesting, I'd genuinely love for you to integrate it into a small project and see how it goes. Try it. Break it. Tell me what's confusing. Report bugs. That's exactly what I need right now. Because there's a huge difference between: "It works on my local machine." and "Someone else actually integrated it and it works." 😂 And I built a security dashboard too If I'm going to let Rizzzler handle authentication, I don't want users to have zero visibility into where their account is being used. So I also started building a security dashboard. The idea is that users can see where they've used their Rizzzler account to sign in or register. They can manage those connections and remove them when they want. I want users to have actual visibility and control over their authentication activity. It's still something I'm improving, but I think this is an important part of making the whole idea useful. Then I had another completely stupid idea 😂 While I was working on all of this, I was also experimenting with AI-generated emails. And instead of making another boring: "Here is your weekly Rizzzler activity." email... I thought: Why don't I let AI roast your profile? 💀 So I built a system that generates funny emails based on a sample representation of a Rizzzler profile. The AI basically looks at the profile information available for the roast and turns it into an absolutely unhinged little comedy session. You might get something like: "Bruh, your bio looks like a cry for help." And then it just keeps going. It can roast things like having an absurd number of links, an overly dramatic bio, questionable profile choices, or basically anything that can be turned into a harmless joke. The goal is simple: Make the email something you actually want to open. Instead of: "Your weekly report is ready." You get: "Your internet persona is currently held together by vibes." 😭 But what about privacy? 🔐 This is important. NO — I'm not sending your private/user data to the AI just to roast you. The system uses a sample/anonymized profile representation for generating the roast rather than handing over someone's private account information. I wanted to make this clear because the moment you hear: "AI + your profile + email" it's completely reasonable to ask what data is being sent where. Privacy matters, especially when authentication and user accounts are involved. And now the AI emails are actually live After experimenting with it for a while... It's finally working. 😂 There's roughly a 55% chance on any given day that you'll receive one of these AI roast emails. So you might randomly open your inbox and see: "Bruh your bio looks like a cry for help." And then spend the next minute getting roasted by an AI. I genuinely don't know whether users are going to love this or immediately unsubscribe. But that's part of the experiment. So what is Rizzzler becoming? This is the funny part. I started this project thinking: "I'm going to build a link-in-bio platform." Then I noticed: "People don't really have a reason to come back." Then I asked: "What else can a profile actually do?" And now I'm experimenting with: 🔐 OAuth 2.0 / Sign in with Rizzzler 👨‍💻 Developer authentication 📚 Developer documentation 🛡️ User security & connected-app management 🤖 AI-generated emails 😂 AI profile roasting 👤 The original customizable profile system It's turning into something quite different from what I originally planned. And honestly... I like it. Am I overengineering an 11-user project? Probably. 😂 But I think that's one of the most fun parts of building things. I could have looked at 11 users and decided: "Nobody is using this. Forget it." Instead, I started asking why. Why don't they come back? What would make Rizzzler useful after creating a profile? What could a profile become? And that question led me to something I never expected to build: an identity/authentication system. I don't know if this direction will work. Maybe nobody will use Sign in with Rizzzler. Maybe developers will find the OAuth integration annoying. Maybe everyone will unsubscribe from my AI roast emails. 💀 But I won't know until I actually put it out there. So... try it 👀 If you're a developer, try integrating Sign in with Rizzzler. I'd genuinely love feedback from people who aren't me testing it on localhost. If something breaks, report it. If something is confusing, tell me. If the whole idea is stupid... Well... tell me that too. 😂 And if you use it in an actual project, I'd absolutely love to hear about it. Because right now, Rizzzler isn't some massive platform. It's a small project with 11 users, a bunch of experiments, and a ridiculous amount of code. But that's exactly what makes it fun to build. Let's see what it becomes. 🚀 What do you think? Is turning a link-in-bio platform into an OAuth/identity platform actually a good idea? Would you use Sign in with Rizzzler in your project? And most importantly... Would you voluntarily receive an email where an AI roasts your profile? 💀