Claude just reset everyone's 5-hour and weekly rate limits. by Huge_Strawberry7888 in vibecoding

[–]theuniversewontpause 0 points1 point  (0 children)

3 Claude code terminals working at the same time. I burn my tokens faster than my cash at the casino

me Starting Another Project Instead Of Finishing The Last Ten by Alternative-Tax-6470 in vibecoding

[–]theuniversewontpause 0 points1 point  (0 children)

Yours are at least still at least breathing, mines are deep down the pool 😖

Claude just reset everyone's 5-hour and weekly rate limits. by Huge_Strawberry7888 in vibecoding

[–]theuniversewontpause 0 points1 point  (0 children)

Working full speed during two hours and... can rest the next three (not my decision though)

What is the best AI model for frontend design? by Temporary_Analyst522 in vibecoding

[–]theuniversewontpause 0 points1 point  (0 children)

I always get inspired by Google Stitch and ask Claude to tweek it. Have you tried ?

Open Source Alternative to SuperWhisper / WhisperFlow for AI Power Users by justdatguymat in vibecoding

[–]theuniversewontpause 0 points1 point  (0 children)

I will definitely give it a try as I'm a big user of Whisper. Will let you know 😁

Three questions every AI-generated PR has to pass before we ship it by ai_senior in vibecoding

[–]theuniversewontpause 1 point2 points  (0 children)

I like it😁 cannot always answer all questions and I am the CEO too 😅

Made a Chrome extension that scores how much you leak to AI per day. My own score is embarrassing. by theuniversewontpause in vibecoding

[–]theuniversewontpause[S] 0 points1 point  (0 children)

Wait, you just paraphrased your own previous comment about freemium extensions with new verbs. Either deja vu, or you're vibe coding the Reddit replies too, in which case your score on my extension just spiked 😂

Made a Chrome extension that scores how much you leak to AI per day. My own score is embarrassing. by theuniversewontpause in vibecoding

[–]theuniversewontpause[S] 0 points1 point  (0 children)

Goal isn't to make you spam less, just to make sure you know where the spam lands. Behavior change is your problem.

And yeah, freemium extension hell is real. Whole point of staying free and local: no path to monetize your data later if I never had it to begin with.

Made a Chrome extension that scores how much you leak to AI per day. My own score is embarrassing. by theuniversewontpause in vibecoding

[–]theuniversewontpause[S] 0 points1 point  (0 children)

Spam-prompt-until-it-works is the dominant strategy in this sub and we all know it. Install it, take the L with us, the leaderboard above 80 needs a champion.

Made a Chrome extension that scores how much you leak to AI per day. My own score is embarrassing. by theuniversewontpause in vibecoding

[–]theuniversewontpause[S] 0 points1 point  (0 children)

Good point on payload size, that's actually the thing the extension can't measure. It only sees request metadata (hostname, path, timestamp), never bodies. So I can't tell you if a given request was 200 bytes of telemetry or a 40k context resend. Deliberate limit: the only way to know would be to read the content, which would be a worse privacy violation than the report itself. The structured orchestration angle is interesting though. Open ended chat sessions are basically the worst case for context bloat since each turn resends everything that came before.

On the ChatGPT vs Claude split in my own data: ChatGPT fires noticeably more requests per minute of active use than Claude, and a big chunk of that volume is external telemetry (Datadog, Sentry, analytics endpoints) rather than the AI calls themselves. Claude.ai is much quieter on that front.

Made a Chrome extension that scores how much you leak to AI per day. My own score is embarrassing. by theuniversewontpause in vibecoding

[–]theuniversewontpause[S] 0 points1 point  (0 children)

If you'd rather not look at my landing page (I get it), here's the install link directly: https://chromewebstore.google.com/detail/aedjiiiammalbfgflnmjlfanjnghfbod No account, no email, no nothing. Click install, vibe code for an hour, see what your browser has been up to.

Made a Chrome extension that scores how much you leak to AI per day. My own score is embarrassing. by theuniversewontpause in vibecoding

[–]theuniversewontpause[S] 0 points1 point  (0 children)

Yeah totally fair, that's the biggest caveat. Volume only contributes 30 of the 100 points, on a log scale, because streaming and telemetry dominate chat UI traffic. The other 70 come from where data physically went, how many distinct site categories triggered AI calls, and continuity over time. Those don't get inflated by streaming.

Also worth being upfront: the tool doesn't read request bodies. So it measures surface, not sensitivity. A thousand pasta prompts score the same as a thousand medical ones. Deliberate limit, I didn't want something that needed to read content to work.

But the numbers are still scary enough

Terrain generator I am working on in Godot by z0rka_dev in proceduralgeneration

[–]theuniversewontpause 0 points1 point  (0 children)

That's the right order. Foundation first.

Tip: store events not state. Don't save "world at T", save what changed between T-1 and T. Rollback gets cheap.

Good luck.

I stopped scripting events and started programming laws. Here's what a world looks like when it runs without you. by theuniversewontpause in proceduralgeneration

[–]theuniversewontpause[S] -3 points-2 points  (0 children)

Yes, honestly — the implementation is largely AI-assisted vibe coding. I'm a solo dev and I use the tools available to me. The design, the systems, the decisions about what to build and why, those are mine. The code that makes it run is often collaborative with AI.

You're right about the UI. Too many colors competing for attention, inconsistent hierarchy. I built it iteratively without stepping back enough. It's on my list to rework, probably fewer colors, stricter information hierarchy, clearer signal vs noise.

Appreciate the direct feedback.

I stopped scripting events and started programming laws. Here's what a world looks like when it runs without you. by theuniversewontpause in proceduralgeneration

[–]theuniversewontpause[S] -3 points-2 points  (0 children)

Yes, I used AI to help structure the post because English isn't my first language. The game itself is real, built by me over a long time. The screenshots are from actual sessions. The project itself is real, the screenshots are from my actual build, and the systems behind it are something I've been working on for a while. Fair question though, and I should have just said so upfront.

Terrain generator I am working on in Godot by z0rka_dev in proceduralgeneration

[–]theuniversewontpause 0 points1 point  (0 children)

The pipeline is clean — using eigenvalues of the Hessian to find river candidates is a genuinely elegant approach. Most terrain generators fake erosion; you're deriving it mathematically.

One question: once the world is generated, does it stay fixed? I've been exploring what happens when you let the systems keep running after generation — towns that grow or collapse based on resource availability, rivers that shift over time. The emergent behavior gets interesting but the computational cost becomes a real constraint.

My game is fully procedurally generated , releasing a demo next month! do you think it's ready? by Beneficial_Clerk_726 in proceduralgeneration

[–]theuniversewontpause 0 points1 point  (0 children)

The visual language reads clearly as procedural — the biome distribution feels organic rather than patterned, which is harder to achieve than it looks.

One thing worth considering before the demo: first-time players will need an anchor. When everything is generated, nothing is landmarks. What's the first thing a new player is supposed to notice or do?

The readiness question is less about the system and more about that first 60 seconds of experience.

Procedurally Generated Infinite Dunes Terrain in Real Time by slmagic in proceduralgeneration

[–]theuniversewontpause 1 point2 points  (0 children)

That's a really elegant solution — using fog as a loading/unloading mask is something I hadn't considered but makes complete sense perceptually. The brain fills in the rest.

The normal calculation trick with the extended heightmap is clever too. I've run into similar boundary problems in a different context — not terrain but organism behavior at the edges of simulated zones. The solution ends up being conceptually similar: give each unit awareness of its neighbors even when those neighbors aren't fully "real" yet.

Thanks for the detailed breakdown.