KMD
@kentuckymd64early
Taking longer than usual. Trying again shortly
Project
Project J.E.N.E.S.I.S
A place for developers to manage and see AI-supported software systems easily.
Developer • Founder • Humanitarian Worker
Why is working with the free version of Claude so frustrating? 😅
Taking longer than usual. Trying again shortly
tokens get fried after 3 prompts lol
Taking longer than usual. Trying again shortly
The incident lasted 23 minutes. About 18 of those were spent figuring out what changed. The actual fix took 5 minutes. If those numbers feel familiar, that's what I'm trying to fix.
Taking longer than usual. Trying again shortly
thanks big dawg
First builder post, so I gotta introduce my project, right? I built a Chrome extension that reads any website's design system in one click and sends it straight to all your AI agents: Claude, GPT, Manus, Lovable, or copy to Cursor.
Reason I built it: every time I wanted to build something that "looks like Stripe" or just like a website with design patterns I like, I'd spend 20 minutes in DevTools copying hex codes. Then try to describe it to an AI in words. The result was always generic.
So I made UIDrop. One click, the AI gets the exact colors, fonts, spacing, shadows, component specs, either as a prompt or as "design_system.md"— with the screenshot attached.
It's free. 20 installs so far, launched 6 days ago.
Still figuring out distribution but the product works. Happy to get roasted on what I'm missing.
uidrop.site/
Taking longer than usual. Trying again shortly
Soo cool!
Instagram, Snapchat & Tiktok: secsen.ai
Hello, world!
I'm building an real-time social scam intelligence platform.
Curious to see if that instagram or tiktok ad is a scam, but don't have 10-15 minutes to research everytime?
Don't worry, just send us a screenshot (or a few), we'll do the background check and compile a rapport for you in less than a minute.
Taking longer than usual. Trying again shortly
Yoo this is very interesting stuff
Taking longer than usual. Trying again shortly
Jenesis build log — week 6
built: unified timeline view
broke: event ordering with millisecond-resolution timestamps
learned: clocks in distributed systems are a lie
next: adding sequence IDs to the event schema
still don't know if anyone will use this but the problem is real
Taking longer than usual. Trying again shortly
this is solid shit. snowflake-style distributed ID generation, unique without a central counter. explored this idea actually, went with per-source sequence IDs because the bottleneck overhead matters less than keeping the ingest simple. but you're right it's a tradeoff. might revisit if ordering becomes a scaling issue.