choraria

8 ms·

1.
Ask HN: I've got a cool domain. How do I put it to good use?
2 points by choraria 8mo ago|0 comments
2.
The front page for early products(bulletin.so)
1 points by choraria 9mo ago|0 comments
3.
by choraria 9mo ago
That's helpful. I think I need to beef up profanity keywords A LOT more than I'd originally anticipated. On it!
4.
by choraria 9mo ago
No disagreements there. My goal is to make this THE BEST list (of all, if any) out there. As much as I see AI taking over handling variations, it'll still need an exhaustive source of truth about what's what and I really think I&#
5.
by choraria 9mo ago
Right on all counts. Twitter is a rather simplified example. I see it as something that literally every platform can use. Say, ProductHunt, other platforms that offer product launches, link-in-bio tools etc. etc. I'm a bit bullish arou
6.
by choraria 9mo ago
YOU NAILED IT! That's part of what I want to explore next too. One of the other common thing I've heard is to check other social media platforms to check if a username is reserved. But, namevine.com already did that. Maybe it does
7.
by choraria 9mo ago
I see. Will re-run through the categories and the datasets from which I've adopted the names and categories. Maybe either I missed something or it might've not existed in the import in the first place. But noted. Also, thanks :)
8.
by choraria 9mo ago
Interesting. I think you're right (on the API category this falls under). Also love the approach on keeping this API async. Makes so much more sense that way.
9.
by choraria 9mo ago
Yes; I've gotten that request from another person on LinkedIn too for bulk checking existing usernames. Will work on releasing that shortly too. Thanks for being helpful and constructive all the way throughout the convo :)
10.
by choraria 9mo ago
Hey @sampli — was there some kind of bundling that you were looking for?
11.
by choraria 9mo ago
Interesting! Didn't think about it that way. Currently, it's a super dumb system. There's a list of ~1.7 million records and the API simply looks-up against that. Super lazy approach. Was avoid running an API across OpenAI or
12.
by choraria 9mo ago
I think there's a general aversion to subscriptions at the moment so wanted to offer this on a usage-based pricing to begin with. While I may have to (hope not to though) will switch to subscription if that's what most users end u
13.
by choraria 9mo ago
You're right about the variations there. I did think about it but decided NOT to add that in this version (felt like over-complicating the process), which I've now come to understand IS a required criteria. Will work on improving
14.
by choraria 9mo ago
True. I've tried to add language where possible. I think currently, it's only on dictionary words so if the username is a dictionary word in another name, it would be flagged. It may or may not show-up under the "restricted&q
15.
by choraria 9mo ago
Well, to clarify, this API is really for folks who're building platforms that require usernames. For ex: imagine if you were building the next Twitter or anything that requires usernames. There, you'd want to know what's happ
16.
by choraria 9mo ago
Good point. Currently, I've got "kike" as a Spanish dictionary word and also a public figure. Honestly, the job of this API stops there. It tells the platform that this username needs to be handled differently than "rand
17.
by choraria 9mo ago
Damn! Just read the title and a few lines from the post but will definitely go through it fully and thoroughly. Thanks for sharing. I didn't mean to reduce the complexity of the challenge. Was mostly trying to convey that the specific
18.
by choraria 9mo ago
Fair. I suppose most newer platforms may not think too much about it. So here's the pitch though: Imagine you're building the next Twitter (or, you know the platform has the potential to become the next Twitter). Knowing what we k
19.
by choraria 9mo ago
My take on latency in general is this: You may just use the API to flag (not act) in an async way. This way, you can just alert/monitor and decide later whether or not to take any actions while keeping the flow non-blocking. Another ap
20.
by choraria 9mo ago
Not a joke (I'm taking this in the spirit intended) but I can see there are TONS of things I need to be improving on: 1. latency: my original goal was to make it sub-10s but with checking for auth, cold starts, the actual lookup, could
21.
by choraria 9mo ago
- site is AI generated: yes. I'm NOT a developer. I vibe-coded it using Cursor and other AI tools - post is AI generated: not 100%. I wrote the whole thing myself (promise). The sentiment is real, so is all the context. I just asked AI
22.
by choraria 9mo ago
Tell me about 'em. Will add to the list. I doubt I'll be able to stop ALL variations but I really am determined to manually keep this list updated as best as possible. Currently at 1.7 million records; will be at around 2.5 millio
23.
by choraria 9mo ago
The comment on regex was really because that's what I did when I built internal reserved usernames list of 2 of my URL shortener projects. I love regex, btw. BUT, I don't think they cover all of what we need with usernames specifi
24.
by choraria 9mo ago
I thought about this and decided against complicating ways in which this can be restricted. Honestly, this is a super simple challenge to solve. Perhaps I should introduce this as an API parameter to detect variations. That way, not just ta
25.
by choraria 9mo ago
Thanks and this gives me more perspective too. Here's what I'm hearing: - need to improve categorisation (some are miscategorised, some categories don't make sense) - better list; more subsets to block (fair and very true) —
26.
by choraria 9mo ago
That would depend on the folks implementing the API In it's current state, I'd look at the API to check for reserved / premium names (or something that's profane). If it makes sense contextually: imagine if you were buil
27.
by choraria 9mo ago
Thanks and I do appreciate the comment too. I'm a bit unsure about it's future as a business but for now, hoping it becomes my first app with some paying users. I typically think small scale but you're right. I suppose most b
28.
by choraria 9mo ago
Super valid and fair. Thanks for taking the time and writing this too. In tears (on the inside) because of some validation around problem statement. I am exploring providing this as a pay-once service too, where you get a point-in-time CSV&
29.
Show HN: No more writing shitty regexes to police usernames(username.dev)
19 points by choraria 9mo ago|56 comments
30.
by choraria 1y ago
Thanks for checking it out and all the support! And yes, it’s on the list of features to add. Will make that available as part of a paid plan though ;)

More ›