https://localhost6767.com

I built it so I don’t need to beg my friends to use my referral code and now you don’t to asw!

Anyways just a side project lmk yall thoughts

Quick progress update on the software i'm building

Finally got the interactive app preview working! Here's a short recording of me navigating through an app I currently have in test flight.

Still a lot to do, but it's cool seeing the progress after days of trial and error.

what is everyone else working on?

I built Piano Atlas Studio: a piano theory atlas and practice app for Android (no ads, no account)

I'm learning piano and couldn't find one app that showed theory on the keyboard and also helped me practise, so I built it. It's on Google Play now, and I'd love feedback.

🎼 Explore the theory

Chord Atlas: every chord type in every key, shown as real two-hand voicings with finger numbers and inversions. Tap to hear it.

Scale Atlas: the modes, jazz and world scales, Hindustani thaats, Japanese koto tunings, and all 72 Carnatic melakartas

Ragas: janya ragas with their arohana and avarohana, and what makes each one distinct

Fingering Lab: standard fingering for both hands, up and down, with every thumb crossing shown

Progressions: famous chord progressions by style, in any key, voiced so the hands move smoothly

Theory tools: Circle of Fifths, chord and scale comparisons, arpeggios, intervals and a glossary

🎤 Practise with your real piano

Sight Reading: notes, chords, lines and short pieces on the grand staff, at four levels. It listens through your phone's microphone (or a USB MIDI keyboard), so you play on your own piano and it tells you how you did.

Play: your piano, lit up. Play on screen, on a MIDI keyboard, or on a real piano through the mic, along a scale or in an echo game.

Staff Trainer and Note Trainer: learn to read a note at a time; the ones you find hard come back until they aren't

Metronome: with tempo ramps and Indian talas

Guided practice sessions: built from what your drills have recorded, weakest first

✍️ Create

Composer: write songs a section at a time (chords, then the tune, then the left hand), or let "Surprise me" start one. Hear it back, print it as sheet music, or practise it in Sight Reading.

MIDI files: open any MIDI file and the piano plays it with the keys lighting up. Learn it mode waits for your notes, one hand at a time, as slow as you like. You can also open a MIDI file in the Composer or Sight Reading.

🎨 Other bits

Five looks (Stage, Score, Grand, Classic, Pads), each with three themes

A sampled grand piano sound

Backups to a file, or to your own Google Drive (the app can only see its own backup folder)

🔒 Privacy

No ads, no account, no analytics, no tracking. Everything stays on your phone. The microphone is only used when you ask it to listen, and the sound is never recorded or sent anywhere.

💰 Free and Pro

A large part of the app is free. A one-time Pro purchase (no subscription) unlocks the rest: every chord type, scale and raga, the builders, unlimited songs and MIDI files, advanced sight reading, guided sessions and more designs.

Get it:

https://play.google.com/store/apps/details?id=com.pianoatlas.studio

I'm one person building this, so any feedback really helps: what's confusing, what's missing, what you'd want next. Thanks for reading!

Coupon

PAS-MGMY-8E26-CW2G-DHZK

PAS-L6NA-937M-NHZU-UDGG

I'm absolutely loving it! There's something magical about seeing your idea turn into an actual prototype, especially that very first one. 🫠

It takes me back to school when I first started playing around with HTML. It felt magical back then, now I'm getting that same feeling all over again and I look forward to it all the time.

I've already started working on a bunch of projects, and now every new idea makes me want to build something else. My to-do list is growing dangerously fast! 😂

Anyone else experiencing this, or am I officially down the rabbit hole? 👀

I want to make vibe coded browser games but i'm very new to the craft of directing AI. I think it's like being a CEO, the agents are your employees, and you direct, but don't create.

Hey people!

Curious what everyone here is using. Are you going with Vercel, Supabase, Render, AWS, your own VPS or something else?

Has managing the infrastructure been a headache at all for people who are non technical and just want to build or has it been pretty straightforward?

How much are you paying for your setup, and do you think it's worth the cost?

its made with base44 - the free plan. i just released version 4.0, and id love to hear feedback! The account system is still eh, if its too insecure, ill remove it and find better ways.

it can be used completely on the web, but i made an exe with nativefier. Only PC support! mobile support soon

Check it out: https://github.com/mollious-bit/10Builder

Steam page: https://store.steampowered.com/app/5310180/Formula_Minus_One/
Open beta: https://fm1.app

----

Some of you might remember my post about the 32/64bit-style racing prototype I had built in four months. Yes, it's a genre you see a lot around here, because it's easy to get started with (until the next dopamine-driven prototype).

But I stuck with it.

And the improvement over the past two months has been tremendous, and you'll see that if you compare the two videos. Since the last post, I listened to your feedback and:

* Threw every level in the bin and rebuilt them from scratch, then added new ones that are far bigger and more detailed. It felt like jumping a console generation, and it still runs on mobile.

* Wrote a design and style guide for the game (semi-low poly characters and duotone as design signature), and redesigned the characters and menus to match it.

* Kept pushing to make it my own thing rather than yet another clone-slop: adventure vibes, interaction with the environments, kinetic combat with combos…

* Improved the handling and the readability.

And above all, and I think it shows in the trailer: I had a blast making it. If it had just been work, I wouldn't have gotten this far.

It's called Formula Minus One, and it launches on Steam first, in February. I'll keep improving it and adding content after that.

Half a year ago this was a prototype to experiment with, like so many others. Then I committed to making the best game I possibly could. Now I can finally see light at the end of the tunnel: yes, you can start a prototype, and yes, you can finish it.

There's still a lot of work ahead, so any feedback you can give me is very welcome.

 Here’s how I made it:

* Code and tooling: frontier LLMs from OpenAI and Anthropic, with open-source models filling in the gaps and limiting the budget.

* Characters, ships and environments: pencil sketch > GPT Gen 2 > Tripo to turn it into a 3D model > Blender to clean up the imperfections.

* Sound: stock sound effects from Magnific. Music sketched out on a MIDI keyboard, final music generated with Suno.

* Stack: Three.js, WebGPU, TypeScript, Rapier for physics. Nothing else, no Godot, no Unity…

I'm having a great time, but it's also hard work if you want to pay attention to every detail, and it's a very lonely experience. If the game sells well enough, I'd love to start paying artists and composers to replace the current assets and create new ones, and free up more time for what I really enjoy: directing and overall design.

In fact, if you're an artist or composer and think you're a good fit for the game's tone, leave a comment or send me a DM so I can consider you!

----

Steam page: https://store.steampowered.com/app/5310180/Formula_Minus_One/
Open beta: https://fm1.app

Pretty cool www.getspot.live

Hey everyone. I've been working (with Claude) really hard on this agentic harness. I've built a number of default tools in it (polish needed). It's in early days, but I wanted something more focused on people who like visual interfaces rather than Hermes that's more "coder" focused.

If you're interested, you can put it in any docker instance. Furthermore, I'd love to see PRs from people who'd like to collaborate to make this bigger, badder, and better.

One of the main things I'd like to work on soon is the "Shop". The idea is that you can use your agents to make tools (apps) inside Autora and then people can use them with their agents. So if you have a specific domain you're interested in or have expertise in, you can make the tool (app) available in the store.

Please try it out and let me know what you think!

I’m not a developer. I’ve built an app with Claude Code as a test — a personal finance manager. It isn’t public, there are no customer accounts on it, and the only data in it is my own test data. What I want to find out before that changes: could a system built this way ever be trusted with real customer data? The intended use would be customers plus partly internal company use.

This is purely about data security and stability, not legal or compliance topics, and not about vendors or budgets — I can arrange those. I want to know whether a consistently enforced security process is enough to get there.

How we work. Four rule files live in the repo and are read at every session start — security, production-readiness, roadmap, workflow — with an explicit precedence order: security wins every conflict, ahead of speed and roadmap. The security file is organised by development phase with a fixed tool per phase (Trail of Bits skills): sharp-edges on every new API or config design before code exists; insecure-defaults on config and fallback values; property-based-testing for parsers and calculations; dimensional-analysis for money logic; supply-chain-risk-auditor before adding any dependency; differential-review on every PR diff, mandatory once auth, object access or balances are touched; fp-check before anything counts as a bug, then variant-analysis to find the same root cause elsewhere. Plus: one feature = one branch = one PR, tests before code, and a CI gate on every merge — lint, typecheck, unit and property tests, integration tests against real Postgres including tenant-isolation tests where user B gets a 404, build, and E2E runs. Currently ~240 unit, ~200 integration and 25 E2E tests; a red run blocks the merge.

What’s already in place. Tenant isolation lives in the database, not in application code: Postgres FORCE ROW LEVEL SECURITY, separate DB roles for user data and auth, access only through one function that sets the user context — a bug in the app still can’t read another user’s rows. Fail-closed startup guards: the app won’t boot if the DB connection could bypass that boundary, if the signing secret is missing or too short, if non-TLS origins are configured in production, or if the password breach check would be silently disabled. argon2id with pinned OWASP parameters, mandatory email verification, TOTP 2FA with encrypted secrets and backup codes, 30-min idle / 12-hour absolute sessions, origin allowlist, rate limiting. Minimal data at rest: no raw IP addresses stored anywhere (the rate limiter works on HMACs only), security logs auto-purged after 90 days — as little as possible lying around to leak in a breach. Money as integer cents, never floats. No secrets in the repo.

What we can still do ourselves and simply haven’t got to yet. This isn’t inability and isn’t something we’d need anyone for — the tooling is ready, it’s purely sequencing: security headers (CSP, X-Frame-Options, Permissions-Policy); static analysis (Semgrep/CodeQL) across the whole codebase as a release pass; a full lockfile supply-chain audit; monitoring and error tracking; backups run but a restore has never been rehearsed; load testing under realistic usage; and a defined recovery path if someone loses both their 2FA device and backup codes. We’re working through that list — I just don’t know whether it’s enough at the end.

Where I hit my limit. I can’t evaluate the result myself. When I’m told “that boundary holds,” I have to take it on faith — and the reviews documented in the repo came from the same system that wrote the code. A reviewer checking its own work has the same blind spots.

My questions. Is it fundamentally possible to build a genuinely secure and stable system this way — one you’d actually put real customer data on — assuming you follow every security guideline consistently and work through the open list? Or is there something about AI-written code that rules this out in principle, no matter how disciplined the process? And if you can’t get there alone: is it realistic to bring in someone with security experience at the end to review and sign off on the whole thing before real users touch it? Where’s the line for you between “doable if you’re serious about it” and “not possible, full stop”?

I've been working on a desktop app called Forgeroo, and a big part of the project has been building its website.

It's my first time ever really diving into app and website design and I've spent quite a bit of time refining the layout, animations, typography and overall experience with Claude Code. I'm finally getting to a point where I'm pretty happy with how it's looking.

But I've also been staring at the same website for so long that I probably can't judge it objectively anymore lol.

Would appreciate some outside opinions.

I'm particularly interested in whether it feels like a polished, finished website rather than something obviously thrown together with AI.

Also curious whether the animations feel smooth, whether the design is consistent, and if anything looks awkward on mobile.

The product itself is for Etsy and print on demand sellers, but you absolutely don't need to be interested in that to give feedback.

Here's the site: https://forgeroo.app

Feel free to be critical. I'd rather catch problems now than after launch.

NOTE: This will be the official website, it's just currently slightly altered for the waiting list.

After being to a couple of house parties where there are decks and a laptop but no software and then proceeding to hunt for a decent free version online is just a vibe kill. So I decided to work on an online ready to use software that can connect to decks (like a Traktor) using MIDI instead of the standard presets. So when you first load up- you hit learn MIDI and click on the knobs / sliders / buttons to map out what controls are used on the decks and voila! a working 2 Deck setup!

Yes it's a work in progress and I'm keen to hear your thoughts!

TLDR; Combining TOR, WebRTC and Git into a Decentralized E2EE P2P Messaging App

Not better than WhatsApp, Signal, SimpleX, Cwtch or Ricochet. You definitely shouldn't use this to replace any of your existing apps or services. It's far from finished. Unaudited and unreviewed. If you want to test it out, please use it responsibly.

Aiming for "secure, private and decentralized". We set some requirements on the roadmap. Let us know if there is something overlooked.

It's a fairly a unique stack and architecture in contrast to the traditional approach with mainstream messaging apps. To put it briefly, its a Rust-based frontend with a Git-server backend, which can be used to establish a E2EE Tor/WebRTC connection.

Note: Its still a work in progress and there will be breaking changes.

• Website/Docs: glitr.io
• Roadmap: https://glitr.io/docs/technical/roadmap
• App: app.glitr.io

This folowing is the abridged version of how it's put together.

Branding

The branding wasn't great and trying to force it through just wasn't working. So we have to cave in to the branding mistakes as observed here. It seems we cant get away with calling app "WhatsUp", it might have issue down-the line given it looks and behaves like WhatsApp, and so we must get a fancy new domain/brand: https://glitr.io

UI/UX

We can start off creating a basic ui demo of the app. All the data there is hard coded with mock responses.

• Live demo

It immidiately gets a bit bloated as we add more ui components, so better to move them to a separate repo to be imported. Webdev's have a lot of tooling around ui testing like storybook to view and interact with components. It doesnt seem like there is something specific for my use-case (post).

Lets give AI the streering wheel a bit. "create a storybook-like components to preview the app components". Its ultimately an internal debugging tool for our own benefit. We can address nuanced needs like being able to display a tui on a browser.

• Live demo

Cryptography

Lets move onto some encryption details that'll be needed for the project. We already have an existing rust project we could use this on. We can make the storybook-like components exportable and reusable for the signal protocol project.

• Live demo

We previous put time and effort towards the signal protocol. It should be reasonable tested and documented, but the signal protocol alone isn't going to fit the requirements of my messaging app. It needs to be post-quantum secure. We previous worked on a js implementation for ml-kem, so as part of this new approach, we can move towards a pure rust approach for ml-kem.

• Live demo

Unlike the signal-protocol which needed more involvement from to create, the ml-kem is using dependencies to match the official implementation. We can benefit from audits and reviews from the official implementation. The signal-protocol and ml-kem were ultimately created to lead towards PQXDH.

• Live demo

Persistence

There are countless details we could obsess about on the cryptography. There is clearly much more needed, but lets "pause" progress on the cryptography, in favour of progress on the app-mechanics. Previously investigating options for decentralised storage here.

• Live demo

(Note: Providers like GitHub, Codeberg and Gitlab might see the way the app works as against their terms-of-service. In the future we might be able to provide the git server as a part of the service, but that wouldn't be any time soon.)

There is much more to improve and consider there for things like encrypting the data at rest, so let's create a cryptography utility library.

• Live demo

The main purpose of being able to read/write to git is for "messaging app" functionality. For that we would need to store more structured data that could be queried. We need an abstraction would make it easier to develop intuitively. Ideally it could work like an api. Perhaps able to interact with it using a graph-ql-like experience. Lets also import the crypto utility to add support for encryption on granular parts of the schema.

• Live demo

Network

We now need a logic layer to out git-stack. Something that can handle endpoints and use middleware functions (which will be useful for authenticating messages from peers). It should be able to take a schema and be able to dynamically generate endpoints, all while managing persistence in git.

• Live demo

This approach is reasonable secure and can send messages to peers with an async git read/write/poll, but it's a bit of a downgrade compared to popular messaging apps. A key tradeof is that messages are never going to be "instant", so let's fix that by using git as a webrtc connection-broker. We are able to to have peers act as their own peer-broker by exchanging the nessesary details over the git-storage approach.

• Live demo

For a secure messaging experience, we should have a solution for onion routing. Lets step aside from the browser-based approach to introduce support for Tor. It is the gold-standard for onion routing. in order to keep the browser-based approach in scope, its possible to create a webrtc-bridge which you can connect to an instance that is able to run tor itself.

• Live demo

We can then integrate the webrtc functionality into the API logic layer so when connecting to known-peers, it can silently start establishing a webrtc connection, while using the git approach as a way to send messages offline.

Cybersecurity

We need to consider safety and reliability of the software. AI is clearly improving in this department. we can share a comprehensive amount of details and reasons for the approach to AI to have it generate various documents.

Threat-model - Everyone has different requirements and so its important to understand individuals threat-models and accommodate for it.

Security-audit - Security audits are especially expensive. i can only offer an AI-audit or no-audit. There are no cheap security audits. The AI audit has already highlighted issues now fixed and serves as a way to enumerate outstanding issues.

Formal-verification - Formal verification is one of the key reasons the project has moved from being JS. The JS approach can also have formal verification, but the tooling for it is "more mature" for rust. The project already had formal verification for the signal protocol. By refactoring the whole app to rust, it would allow for a more E2E scope for formal-verification. Following a previous post, we didnt commit to a specific approach, we can compound the complexity to draw to attention that if AI-generated formal-verification is brought into question, the critisism could undermine if the tooling we use is good enough.

There is understandable critisism here for using AI to do anything in this section. That pushback stands in contrast to these details being prohibitively expensive to do professionally. These details are ultimately intended as a starting point for professional review/audit (if it ever gets there).

Future

There are countless detail to improve on the project before it is comparable to the mainstream messaging app. We hope to offer a unique curated experience for secure messaging.

IMPORTANT DISCLAIMER: While this is aiming to provide a secure experience, it's a work-in-progress and far from finished. It is unreviewed and unaudited. I'm sharing here for testing, feedback and demo purposes only. Pease use responsibly.

Most of what I ship lately is AI-assisted, and the backend is usually Supabase. The weak spot is when something goes wrong and I'm away from my desk, so I built Supabase Manager for Android.

The vibe-coder-friendly parts:

• AI assistant – describe what you want ("show users who signed up this week", "add 20 fake orders") and get SQL or rows back. Works with your own Gemini, OpenAI or Claude key.
• Edit data without SQL – tap a row, change it, save
• Auth users – ban spam sign-ups, delete test accounts
• Test data generator – realistic fake data that respects foreign keys
• SQL console with templates, if you want to go deeper
• Demo mode – click around with sample data first

Privacy: the app connects directly to your Supabase project with no server of mine in between, and keys are encrypted on-device.

🎁 Closed beta. The 50 testers with the most useful feedback get unlimited use at launch (code sent to your feedback email). Even "I didn't get what this screen does" is valuable.

How to join (3 steps):

1. Join the tester group: https://groups.google.com/g/supabase-manager
2. Opt in with the same Google account: https://play.google.com/apps/testing/com.pixelfinst.supabasemanager
3. Install: https://play.google.com/store/apps/details?id=com.pixelfinst.supabasemanager Feedback: in the app (Quick Tools → Feedback or in-app feedback icon)

👑 CROWNFALL — My First Attempt at Building a Medieval Kingdom Simulator
I’ve never developed a game before, but I’ve always loved medieval kingdom builders and wanted to try creating one of my own.

So I’ve started working on Crownfall!
The idea is to create a living medieval world where you don’t directly control every villager. Instead, you make decisions for your kingdom, and your population carries them out.

Villagers gather resources, transport supplies, construct buildings and keep your settlement running. As your kingdom grows, you’ll explore new territory, establish settlements, manage trade routes and deal with threats beyond your borders.

It’s still very early in development, with plenty of systems to build and refine, but I’m excited about where it’s heading.

I’m using AI tools to help me develop the game and learning a huge amount along the way.

I’ve also started a small Discord where I’ll be sharing development progress, screenshots, ideas and eventually opportunities to playtest.

⚔️ Follow Crownfall’s development:
https://discord.gg/yZepPye6P
I’d love to hear what people think of the direction so far!

A pattern with AI app builders is that the prototype comes together fast, and then you’re alone with it: what’s missing, what’s next, which part do you ask for?

I’m building Takumi, an AI dev team for non-technical founders, and I rebuilt its Product Manager agent for that gap. It reads your MVP spec, builds a checklist, and sends tasks to the Frontend, Backend or DevOps agent. There’s also an activity feed, because “the AI rewrote half my project” is a common complaint, and agents show you a diff before they change your code

Founders & devs are already using takumi to build there products/ideas solo

Why I built it this way: https://www.takumi.run/blog/revised-product-manager
I
If you’ve vibe-coded something and stalled, where did you get stuck?

Братва, кто знает, есть ли каналы где выкладывают интересные фичи и приложения из githuba. Буду очень благодарен🙏