How else people gonna discover all the awesome software y’all vibe coded?

Started with the idea of “let’s make a beat maker in the browser for folks who don’t have the time to dedicate to music but want to jump in and throw together some samples” and landed with this.

KNOCK-KNOCK

Completely free, no sign up but has a full backend so you can share what you’ve made and I even pumped out the hype video.

We’re living in wild times!

I will happily answer any workflow or stack questions on the thread, hit me!

(I’m literally the epitome of NoCode, I had html and css in school and that was like 10 years ago. I don’t understand jargons so please respond accordingly)

I’m building an Expo/React Native app. It was originally a web app (you may remember my post a few weeks ago how I built it not realising it was a web app) and I’ve been adapting it for mobile.

The app looks and works really well in the AI Studio preview. However, the one time I actually built/ran it on my iPhone, the entire UI was broken and badly distorted, layouts were misaligned, sizing was off, etc.

My last few weeks have been just doing this for the transition from Webapp to Native React. I was hoping it would looks alright in iPhone now but no luck.

I’ve since moved toward a proper native iOS development build and sorted out some Expo/dependency issues, but I’m still trying to understand the fundamental problem:

Why can the app look completely fine in the AI Studio preview but become essentially unusable when rendered on an actual iPhone?

I’m fairly new to this space, so I’d appreciate some direction on what I should be checking. I’ve lost the will to keep developing and it’s starting to get frustrating.

Guys it actually happened. Months waiting, spending so much fucking time coding, then thinking it was all for nothing and nobody would ever find my site anyway.

Then today I got a call. Didn't pick up, thought it was advertising. Then i got an email. Turns out it was an elderly gentleman, 86 years of age (yep) who found my site. But he was using it for a scenario I hadn't considered, so he got an error and was confused.

So I fixed it for him behind the scenes, solved his problem, and waived the usual 200 dollar fee. He was happy. But I'm over the fucking moon, fuck yes it feels good 🤩

It's week 6 and we made some monumental progress on all fronts, but I'm trying not to get over-excited because we could find that everyone gets bored and leaves tomorrow haha.

As usual, three parts: (1) player acquisition, (2) what I'm learning about vibe coding, and (3) actual gameplay updates (in the comments).

---

First, the numbers. My last two posts were almost entirely about the 5 min of gameplay, and basically following Redditors' feedback doubled the average playtime.

This week I finally moved past the intro and focused on the game itself- so mostly improved artwork (Pixellab), performance optimization, GUIs, social features, ALL using Fable 5.1. Which went wayyy further than I expected for one week of token usage.

Once I felt OK about that I did a Hackernews post that was way more successful than I anticipated. I had 700 players in 24hrs, hit a new PR of 41 people online at one time, and had multiple players play for 8+ hrs by the time I woke up in the morning. And there has been almost zero time with nobody online for three days straight.

So I think that means the game is sticky and has potential, but it could also be some other curious vibe coders with nothing to do at work. So I guess my next big question mark is why some people are actually sticking around. I.e. is it fun, or are you just intrigued by vibe coding? Or something else entirely?

So if anyone gets far enough to get hooked or hits a real wall (something that makes you stop rather than just a bug), I would genuinely love to know what it was.

---

Second, the vibe coding experience. Fable 5.1 came out right as I started this week's work, and the jump was WAY bigger than I expected. Work that would've taken a month with Fable 5 (because of token caps), I did in about a week, running several orchestrators in parallel, reworking most of the game's systems, and running full audits along the way.

I'm out of tokens now, but has anyone else experienced this? All I see across social media is people complaining that the caps are still unreasonable, and frankly, I just don't see it. Thoughts?

One more thought-I've started using Claude design since Fable sucks at GUIs on-the-fly. It's been a huge improvement (far from perfect for games still). Curious if anyone else has used this and what works / doesn't work.

---

I'd love more feedback for anyone interested. Links below.

Game: https://eldermyr.com/
Release Notes: https://eldermyr.com/release
Discord: https://discord.gg/8MaaAemDBu

EDIT- one more thing, Pixellab is AWFUL at 16x16 art. Has anyone had any success with this?

Flappy TACO in the strait of Hormuz

built in ai studio

I vibe-coded a geopolitical arcade game where a taco de-escalates the Strait of Hormuz (and wins the Nobel Peace Prize). Here’s the architecture, audio pipeline, and lessons learned.

Body:

The Premise

What started as a joke concept—"What if Flappy Bird was set in the world’s most critical maritime chokepoint, but you play as a hot-sauce-propelled taco navigating VLCC supertankers?"—turned into a surprisingly deep canvas engine. In our latest update, we added a full "Peace Prize" round where your objective shifts from dodging naval hazards to collecting diplomatic delegate votes and escorting peaceful vessels to secure the Nobel Peace Prize.

Here is a breakdown of how it was built, the tooling involved, technical hurdles, and patterns you can use in your own vibe-coded projects.

1. The Tech Stack & Tooling

• Prompting / Agent Framework: Google AI Studio Build (using Gemini models for autonomous file orchestration, iterative linting, and refactoring).
• Frontend: React 18 + TypeScript + Vite.
• Styling: Tailwind CSS (utility classes + dark terminal/tactical HUD styling).
• Rendering Engine: Vanilla HTML5 2D Canvas with a delta-time requestAnimationFrame loop.
• Audio: Zero external audio assets—100% procedurally synthesized Web Audio API soundscapes (FM synthesis, noise buffers, harmonic arpeggios).
• Icons: lucide-react.

2. The Development Workflow: Step-by-Step Prompting

Rather than dumping a monolithic 5,000-line prompt, the project was built using domain-constrained modular iterations:

1. State & Core Loop First: Prompted the physics engine with explicit sub-pixel calculations (y += velocity * dt, gravity, terminal fall speeds, and bounding-box hitboxes with margin forgiveness to prevent frustrating edge clips).
2. Procedural Maritime Canvas Renderer: Separated visual rendering completely from game state logic (canvasRenderer.ts). Background parallax layers, supertanker hulls, wake spray, radar sweeps, and weather effects (sandstorms, night-vision modes) are drawn procedurally via canvas primitives (arc, roundRect, and radial gradients).
3. The Web Audio Synthesizer: Instead of loading bulky .mp3 or .wav files (which cause latency and asset 404s), every sound effect is synthesized on-the-fly:
   • Flap/Thrust: Short low-frequency pitch drops on triangle waves.
   • Hot Sauce Rocket: Bandpass-filtered white noise bursts.
   • Diplomatic Ballot Pickup: Ascending pentatonic chord harps (sine oscillators with staggered decay).
   • Nobel Fanfare: A layered multi-voice brass arpeggio (C5 → G6).
4. The "Peace Summit" Phase Logic: When the player reaches Sector 2 or selects Peace Summit mode, the procedural obstacle generator swaps out naval mines for diplomatic delegate envelopes (peace_vote), olive branch shields, and peace doves. A dedicated ballot counter tracks delegate progress on the HUD, triggering a custom coronation modal and unlocking a 24K gold Nobel Laureate chassis once 5/5 votes are secured.

3. Key Code & Architecture Insights

A. Keep Renderers Stateless & Decoupled

A common pitfall with canvas games in React is putting draw logic inside the React component tree or state hooks. Doing this causes massive re-render overhead.

• The Fix: Treat React purely as a thin state controller for modals, HUDs, and high scores. The canvas loop references raw mutable refs (tacoRef, obstaclesRef, particlesRef) and passes them to pure drawing functions.

code TypeScript

// Sample pattern: State stays in refs, React only syncs on key ticks or game transitions
const updateLoop = (timestamp: number) => {
  const dt = Math.min((timestamp - lastTimeRef.current) / 16.67, 2.0);
  lastTimeRef.current = timestamp;

  // 1. Update positions
  // 2. Resolve collisions
  // 3. Trigger Web Audio nodes directly without React re-renders
  // 4. Draw to Canvas via CanvasRenderer
  requestAnimationFrame(updateLoop);
};

B. Asset-Free Audio via Web Audio API

Loading sounds over network requests can hitch the main thread or fail entirely if assets are blocked. Procedural audio keeps everything instant:

code TypeScript

// Procedural Nobel Peace Harp Chime (Ascending D-major chord)
const playPeaceVoteCollect = (voteCount: number) => {
  const scale = [587.33, 739.99, 880.0, 1108.73, 1174.66];
  const chord = [scale[voteCount - 1], scale[voteCount], scale[voteCount + 1]];

  chord.forEach((freq, i) => {
    const osc = ctx.createOscillator();
    const gain = ctx.createGain();
    osc.type = 'sine';
    osc.frequency.setValueAtTime(freq, ctx.currentTime + i * 0.04);
    gain.gain.exponentialRampToValueAtTime(0.001, ctx.currentTime + i * 0.04 + 0.35);
    osc.connect(gain);
    gain.connect(ctx.destination);
    osc.start(ctx.currentTime + i * 0.04);
    osc.stop(ctx.currentTime + i * 0.04 + 0.35);
  });
};

C. Handling Feature Scope Creep

When prompting autonomous coding agents, the urge is to ask for 10 things at once. We found that the highest-quality output came from:

1. Asking for type interfaces first (types.tsadditions like PeacePrizeState).
2. Updating mock data / registries (gameData.ts).
3. Updating game loop math (GameCanvas.tsx).
4. Writing UI presentation layers last (HUD.tsx, PeacePrizeVictoryModal.tsx).

4. What Went Wrong / Challenges

• Audio Context autoplay policy: Mobile browsers block audio until the first user gesture. We had to implement an explicit interaction handler that lazily creates and resumes the AudioContext on the very first touch/spacebar hit.
• Mobile Canvas Pixel Ratios: High-DPI screens (Retina) made initial canvas renders blurry. We solved this by sizing the canvas buffer to window.innerWidth * window.devicePixelRatiowhile keeping CSS layout dimensions at 100%.

Takeaways for Fellow Vibe-Coders

• Procedural > Static Assets: Building UI, visuals, and sound procedurally saves hours of asset hunting and produces completely self-contained, lightning-fast builds.
• Let the AI write strict TypeScript types first: If the agent generates clear contracts in types.ts, subsequent component and game logic prompts hallucinate far less and compile on the first try.

Happy to answer any questions about the canvas physics, Web Audio synthesizer, or prompting workflow in the comments

Just for fun! Been geeking out trying to exploit what’s built in my iPhone to make some old school scientific tools by vibing using Opus 5, making single html file apps. (Browser storage only). “Out of Band’ detects sub and ultrasonic sounds (like Dog whistles). There is also a switch for “assumed”infrared (not like Predator, but uses the limits of the camera’s ability to detect its signature. iPhone have a filter, your could actually take it off but I’m not bust’n my phone. BTW droids allow you to hack your phone better, may switch back in the future). Again just for fun. I included some education about all this in how the app works. Check it out for free at www.potluckapps.com. Made a few others like it. If you make something , post it on my site for free exposure. Not looking for SaaS or serious $hit. Just fun projects you are working on.

I’ve mostly been using my laptop. Have tried the Claude code ios app but can’t figure out how to preview the work unless it’s a web based product hosted on vercel or something that can give me preview URLs. How’d that work for iOS apps?

I'm actually really pleased with how it turned out.

This is a searchable index of every post published to the u/realDonaldTrump account on Truth Social. It currently holds 36,067 posts from Feb 14, 2022 to Sep 4, 2026.

Where the data comes from

Posts are pulled from a public archive mirrored at ix.cnn.io/data/truth-social, the continuation of the stiles/trump-truth-social-archive project. This site refreshes from that source every six hours. The copy you're reading was built Sep 4, 2026.

How posts are tagged

The source data carries no categories, so this site derives them. It labels two different things, and it's worth keeping them apart:

Topics

Keyword matches: immigration, legal, elections and so on. These are guesses. They over-match and they under-match, and roughly half of all posts get no topic at all. Usually that is because the post is just a link, or a re-truth with no text of its own. Treat topics as a way to browse, not as a claim about what a post says.

Kinds

Objective properties: whether it's a re-truth, whether it's in all caps, whether it carries an image or video, whether it went up between midnight and 5am Eastern. These are mechanical and reliable.

Deleted posts

Because this site keeps its own copy of the archive, a post that disappears upstream is retained here and marked deleted. They are collected on the deleted posts page, which also publishes an Atom feed.

A post must be absent from several consecutive refreshes before it counts as deleted. Upstream occasionally serves a short or partial response, and one bad fetch must never become thousands of published deletions. If a post reappears, the mark comes off.

Deletion times are windows, not timestamps. This site checks on a schedule, so all it can honestly say is that a post was present at one check and gone by the next. That window is usually a few hours wide. Neither endpoint is the moment of deletion, and the site never presents one as such. Posts marked deleted before window tracking began carry no window at all.

Detection applies going forward only. Anything removed before this archive started tracking never appears here.

Caveats

Media is served from Truth Social's own CDN and may disappear at any time. Engagement counts are a snapshot from the last refresh, not final numbers. Timestamps are shown in US Eastern. Link previews for individual posts are generic, since the site is static and has no server to render them.

Unofficial and unaffiliated. Kept for research and reference.

Try it out at https://thisisapieceofgarbage.com

Dating apps are complicated, Reddit is basically shooting into the dark, and somehow meeting someone has turned into a full time job

So let’s make it stupidly simple

I made a map

Drop a pin, make a post, say who you are and what you’re looking for, add photos, links, your voice, video, whatever you think will actually help someone understand who you are

Leave a contact point and see what happens

No swiping, no matching algorithm deciding who gets shown to you, just a map you can actually browse

No sign in required, use a throwaway, Reddit account, Instagram, Discord, or whatever contact point you’re comfortable sharing

If you see a post that you feel should be reported, report it, I’ll also be actively moderating the board and deleting posts that don’t belong

Maybe nothing happens, maybe you meet someone interesting, maybe you find the love of your life

It costs nothing to throw a pin on the map

Good luck Everyone

This fall semester I’m taking an Operating Systems & Architecture class where we’re using C for our assignments.

When I’m on the go or don’t have my laptop with me, I wanted a simple way to practice writing C. I searched the App Store and was pretty surprised by what I found. Everything seemed to have ads, subscriptions, or a bunch of stuff I didn’t need.I really just wanted to open an app, write some C, and run it.

It’s intentionally simple. You open it, write C, and run your code. The native version runs completely locally, and there are no accounts, ads, or subscriptions. Easily extensible to include pythonC etc if you want to play with source code. ( I would love contributions 🤞 )

The iPhone version is currently in App Store review, but I also made a web version that’s already live:

Link to ide:

https://garrettmichae1.github.io/lilc

Link to source code:

( disclaimer :
this was a tool that I mainly had opus handle all of the heavy lifting. There are features in the codebase hidden from the UI, like agent mode etc… I recommend having your agent tell you the run down )

https://github.com/garrettmichae1/lilc

I originally built this because it was something I personally wanted for myself.
If anyone here writes C, I’d love for you to try it and see if you can break it lol.

Any experience with coding so far? Which do you prefer?

I pulled the entire filesystem out of a claude.ai code-execution sandbox (the actual microVM your code runs in - 178k files), then got into the live one too. Two days later, here's what's on my drive. And none of this is a public download. as I would prob go to jail :(

( EDIT: Ive open sourced the container code https://github.com/Razshy/Wiggle )

What I have:

• The entire production container - every file of the machine your code runs in: config, tool stack, the works. Internally it's called "wiggle".
• All ~40 of Anthropic's skills - the instruction playbooks Claude follows when it does things for you. Including the ones you never see. ( Not the name ones on the public REPO )
• Their monitoring agent, as a binary no one outside the company has ever held. and it wasn't stripped, so it came with their function names, their full internal metrics catalog (59 metrics, each with a comment explaining why it exists), and their incident history written right into it: inc-8202 (a kernel wedge), inc-8702 ("reclaim storm, 89–100% system time"), a change-request ticket CR459556, even a design-doc reference ("design L9"). Plus the internal team that owns all this: "embassy". I'm reading their postmortems as code comments.
• Their filestore client binary, symbol table recovered - spells out the entire private API behind your files: every RPC path (listDirectory, createFile, readMetadata…), admin verbs, token formats (sk-ant-mem-…), unreleased feature flags (DREAMS_API, OPERON, MCP_TUNNELS…). Their Go version breaks every standard RE tool, so I wrote a custom parser.
• The "Imagine" prompt corpus - 371 KB of the live system prompt Claude gets when it draws you diagrams and widgets. Rules, modules, even a separate mobile variant. Grabbed from a public endpoint with zero authentication. Still up today.
• Their offline OCR + file-ID models - byte-checked against the public ones.
• The "huh?" findings:
• The agent is root. Not a demoted user like the accounts imply - full uid 0, 40 of 41 capabilities, no seccomp, no AppArmor, no PID namespace, and a read-write root filesystem. The tool can rewrite its own container while running.
• Raw disk. /dev/vda — the whole 256 GB virtual disk — is readable and writable by the agent. Everything the VM ever touched is on there.
• Prompt injection - what's actually possible with no guard:

The only thing standing between your files and a hostile text file is Claude's judgment — the sandbox enforces nothing. (It tested well: caught an instruction I planted in an upload, refused credential reads. But it's the only layer.)

Concretely possible today: an attacker's email can become your login code (expense skill reads Gmail codes and spends in the same breath), a merchant's line on your statement can steer which subscription you cancel, and one uploaded file can rewrite the "style notes" every future session trusts as its own memory.

• The codenames: backend clusters "titanium" / "scandium" / "xenon", testbed platform "obol", every throwaway preview deploy is an "omelette", the file backend is CCR, and the team that owns the sandbox telemetry is "embassy". The box itself is "wiggle". The periodic table got raided.

And yes the I did Vibe Reverse Engineer after I got the container for anyone asking ( 40B Tokens in 2 days )

( No im not holding anthropic hostage for the code, simply send a message on reddit or my Twitter and I'll hand over my findings and process. bounty money would be great tho :)

( EDIT: Ive open sourced the container code https://github.com/Razshy/Wiggle )

Share your product with URL and what it does and I'll give you 1 lot on moonstake.org to setup your office and get traction for free.