uhhh...so here's a little something i built 2 weeks back in the hackathon though the original trajectory has changed significantly since then and the core idea has a lot of caveats, but here's what i thought and built in 24 hours: . . . imagine you're deep into a brainstorming session with an AI, going back and forth for an hour and then suddenly the free tier rate limit hits. it's a huge mental overhead to switch to another AI because now you got to re-explain the whole thing once again. you're the only one who knows what you're working on right now and to query any AI assistant you got to carry all that knowledge alone. Meniscus is the layer that finally holds that knowledge for you. it sits outside your tools and maintains one shared picture of what you're working on - your current working state, what you've tried, what's blocking you and what's decided. here's a short demo of what it looks like (absolutely boring) and to read about the architecture, have a look at the notion doc below (that i created during those 24 hrs :D)

dude...conversing on emails exudes such an exquisite eminent essence of a prestigious prominent persona.

old setup pic (wen i was young and a wee bit more stupid)

Do it. That's what fable would have wanted.

the tweets of some people are just so relatable on here

only if one has the ability to think, ask the right questions, listen & observe closely and make calibrated discernment, the compatibility is almost always assessable before commitment and its stupid to do the trial & error thing as a substitute for the harder & intentional work.

so yes guys im finished with this mini-protoc actually finished it 2 days earlier i was figuring out how can i integrate it into my mini-rpc. so still working on integrating it have to change its whole design, for now im just shipping this one what it does: -> compiles a .proto file with a limited subset of the proto grammar. -> currently supports a few primitive data types and unary rpc only. -> has a lexer and parser written from scratch that parse the .proto file, build an AST, validate it, and generate Go structs, service interfaces, client stubs, and registration stubs. repo in replies

I was laid off so I rebuilt their product but better (in 2 weeks from scratch) Open Canvas - a multiplayer site builder with an agent at the cursor. Most website builders ask you to fill in a template.I built one that lets you design - on a free-form canvas, with an AI agent at your cursor, where your whole team co-edits live and visitors see your publish update without refreshing. What makes it different: • Drag 14 design primitives anywhere — not into fixed slots • AI agent edits in plain English, you preview before it lands • Real-time co-editing (Yjs CRDT, Figma-style cursors) • Publish → every open visitor tab updates in <100ms Under the hood: one Cloudflare Worker, serverless Postgres, a first-class CMS, version history, a blocking accessibility audit, AI image gen, custom domains — all shipping as pure HTML, zero client-framework weight. It's MIT-licensed and built in the open

exactly.

build it anyway.

i love the youtube channel of @cleoabram y'all should check it out youtube.com/@CleoAbram

yk what i'll be back on 12th June just wait (AAAAAAAHHHHHH)

The only worst part of being at these local hackathons is that the judges are FREAKING IDIOTS.

4.8 is so shit bro oh my god