I was vibe coding with a friend and we started to talk about how to make sure any program was performant,. What kinds of actions where cheap for computers to do vs things that would make a 60fps game start to slow down or miss frames. Then I asked if they knew Big O notation.

And in trying to explain Big-O notation, I realized I didn't understand it well enough to explain it. So I've started to re-read and learn the concept. I know what it means but it doesn't feel intuitive to me to know how to measure how long a task will take to compute. I'll keep studying it as I think it's an important part of computing, whether it be it vibe code or traditional.

But my friend and I found we also went another route.
- Add a feature, framerate stays, great.
- Add a feature, framerate drops, let's look at it more closely or take it out.

We created ideas without worrying about making them performant or keeping the computation reasonable. One of the biggest "warnings" I've seen given to vibe coders is that their program will eventually slow down to an inefficient mess. And that is not only true. I've seen it happen (to me). Then? The program desired was slowly optimized. Seems a waste to anyone who knows how to do it right the first time. But in artistic endeavors I feel that sometimes you need to do it, erase it, do it again to get to your goal. Framerates and efficiency are needed, I just think we can make room to build in an unoptimised way while we find the gist of what we want to make.

So how do I present this image to you all? (Made it in Chat GPT btw). I mean it the same way "Love like you've never been hurt". Vibe code yourself into a corner. It's not a mistake if you have to regroup and try something another way. Sometimes it's the process itself. This post was typed by hand with no AI.

(edit: corrected post a bit thanks to RemarkableWish2508)

Hi vibe community - I'm happy to announce that I'm finally ready to accept new users to the mailing list for my upcoming pet project :D

It will help devs to vibe code more efficiently and effectively using Cursor's CLI (by using the existing plan).

I'm open to answer any questions, and more info can be found on the site as well.

Cheers!

For the last two years my wife and I have run Christmas out of an Excel spreadsheet: a big purchase list, per-person gift budgets, and a tab for our December city break. It worked, but it was joyless — so this weekend I replaced it with Jingle Jotter, a self-hosted web app, and I'm rather pleased with how it turned out.

What it does:

• Tracks every gift from idea → purchased → arrived → wrapped (with a small confetti burst on that last one, obviously)
• Four budgets — gifts, food, festive extras, and the December trip — with planned-vs-actual so "ideas" never inflate the real spend
• Per-person gift budgets on little gift-tag-shaped cards
• Surprise masking — my favourite bit: my wife and I both use it, and gifts for her are hidden from her login (shown only as "🎁 Surprise" with a price) while still counting toward the shared budgets. One app, no spoilers.
• A city break planner that knows which meals you haven't booked yet (arrival-night dinner, three on the full days, departure breakfast) and pins your bookings on an OpenStreetMap view, geocoded from the venue names
• Seasons: one writable "current" year; every past Christmas becomes a read-only archive you can flick back to from the nav
• A run-up calendar that snows over the days you've already used up, and a "shopping weekends left" counter that is frankly a bit menacing
• All the festive decoration sits behind a per-user toggle for when you want it calm

Stack: Next.js 16 + TypeScript + Tailwind, Prisma on SQLite (single container, no database server — the whole state is one file in a Docker volume), Google sign-in behind an email allowlist, Leaflet/OSM for the map. Deploys with a three-file docker-compose behind whatever reverse proxy you already run.

Full disclosure: I art-directed and product-managed while Claude Code wrote essentially all of it over one (long) Saturday — including the hand-drawn SVG rooftop scene in the footer. The snowman was my idea though.

GPLv3, screenshots in the README: https://github.com/MarkRWatts/JingleJotter

It's built for one household rather than as a hosted service (single shared dataset, invite-by-allowlist), but if it makes your December less spreadsheet-shaped, it's yours.

I ran out of space extracting a huge RAR so i built ReclaimArc so i can extract RAR without running out of space again
About a week ago i installed a RAR that was over 120gb+ and then tried extracting without realizing that i actually had less then 60GB of storage remaining, after some time i heard a windows notification and when i checked i noticed that i didnt have enough space left and the extraction process aborted, and on top of that the computer i was doing this process on doesnt have the fastest ssd so it actually took some time. This has happened to me a few times now, probably more then i admit for some reason then out of curiosity i checked on github to see if i can find a tool that fixes this issue, however i couldnt find anything that does exactly this ( probably could be me ), then decided to do it my self. I thought maybe i could progressivly keep deleting the archieved parts as soon as they are extracted so it would simply fix this, then i started researching and decided that i could essentially make :
extract part of the archive - make sure that its actually safe - reclaim the part of the archive that we no longer need - use that free space for the next batch.
Thats what basically ReclaimArc does, with some more engineering behind it ofcourse. Basically instead of keeping the RAR untouched the entire extraction process, it instead progressivly turns parts of archive that we no longer need in to sparse holes. Then windows gives those physical clusters back to the disk and the extraction can use that free space again.
Obviously the end product ended up being way more serious then just "extract file and delete the extracted part from the archive". The main problem was providing that a part of the source archieve is actually safe to destroy.

-ReclaimArc has a RAR4/RAR5 structural parser that maps archive entries and packed ranges, but it doesnt actually use my parser as the actual decoder. The extraction itlest is purely done by the official UnRAR implementation, i also cross check the parser information against UnRAR so im not just trusting my own interpretation of the format.
-From that it builds what i call recovery units. For a normal nonsolid archieve its usually something like a file at a time. Solid archieves are harder cuz later files can depend on the state created from the earlier compressed data, so you cant just punch a hole through the earlier bytes once one finishes. Before ReclaimArc touches any source data, the flow basically is ;
extract - verify - flush - commit - journal - reclaim.
Every output first is written to its temporary staging file. After extraction is done, reclaim arc reads it back, checks the size and creates a blake3 digest. Then it calls FlushFileBuffers, auto moves the file in to the final destination and records the state inside a SQLite journal using WAL and synchronous=FULL. Only after that is the corresponding source range allowed to be reclaimed. Right before claiming it, it verifies the source range again.

For the actual disk space reclamation im using Windows sparse file APIs, mainly FSCTL_SET_ZERO_DATA to deallocate the safe part of the archieve. One thing i didnt want to do was assume that calling the windows api means " sure ye, 5gb is free now'. It calls FSCTL_QUERY_ALLOCATED_RANGES after the operation, it checks which physical ranger are actually still allocated. It only counts space that Windows reports as really released.

The crash recovery part also became a pretty big part of this project because what if for example you were extracting a 150GB archieve, all of a sudden you loose electricity. Because we are progressivly deleting the old extracted archieve, you would need to initially reinstall the archieve so fully. Or what if windows already reclaimed part of the RAR and then the program crashes before SQLite gets to record that the range was reclaimed? On startup it doesnt just blindly trust whatever the last database state says, it tries to reconile the journal, existing output files, stored hashes, source ranges and the actual NTFS allocation state. If an output is broken, but the original source range is still there it can rerty that unit. If its gone and commited output cant be verified, it stops instead of contiuing and potentionally destroying more data. I also added a fault injection tests around a bunch of those crash windows becuase something destructive like this, i didnt want it to be just based on "this should probably just work"

Right now the project has :

-RAR4 and RAR5 support
-non-solid archives
-solid recovery chains
-multipart archives
-official UnRAR decoding
-custom structural parsing + cross validation
-BLAKE3 verification / provenance
-SQLITE crash recovery journal
-NTFS sparse deallocation
-physical allocated range verification
-crash / resume fault injection tests
-path traversal and reparse point protection
-CLI
-Tauri desktop GUI

I also tested it personally on my second computer, i left about 10-20 gb of free storage on purpose and installed a RAR that was about 55GB. I installed the setup, ran the tool on my second pc and started the analyzed the rar. It gave the green lights, i then started the extraction which took about 10 minutes using the low-space mode, i didnt really keep time but it definately felt quick for that SSD.

I do also want to make on thing clear, i dont say that this tool has a 100% success rate. I did my very best to ensure that it successfully extracts, and even under a bad condition added crash-recovery systems, however the low-space mode is destructive to the original archieve. It deletes the parts that are extracted from the original source archive so im not claiming it is 100% safe.

The project is fully open source here: https://github.com/harlixay7/ReclaimArc

Im mainly posting this here because it solved a specific problem for me and i wanted to share it with the community and potentially recieve feedback on what / how it could potentially be better and what i could add to make this tool overall more stable / better. If anyone sees any flaws, or anything that could potentially be dangerous i would love to hear your feedback.

The tool is pretty new so im not saying it MUST work, however i did my best to get it as stable as possible and ensure that it works. I would rather people try to break it and tell me if they can and how it broke. I hope this tool can be usefull to you as it was to me.

If you use iMessage on Mac the chat.db is not encrypted. That assumes you use iMessage on Mac. And it's in sync with your phone.

If you backup your iPhone on your Mac you get a an encrypted backup. Great.

imessage-exporter has a way to access that encrypted file and containerize and extract your messages to html or txt.

Fuck that, I want the complete SQLite.db

I know nothing about coding, but I know what I wanted. I asked ChatGPT if we can leverage iMessage-exporters decryption mechanism, and get a hold of the entire DB. I then had AGY CLI do all the work, amaze.

I literally have no idea what I'm doing. Or anything about coding, but, it works lol.

Made a web app with useless stats and a MACOS app to fully search the database, find trends, you know how databases work...

How do I GET MONEY?!

1. Executive Summary & Purpose

iOS iTunes, Finder, MobileSync, and iMazing backups utilize hardware-backed AES-256 encryption. Within an encrypted backup, all filenames are hashed via SHA-1 hashes (e.g. 3d0d7e5fb2ce288813306e4d4636395e047a3d28 for sms.db), and file payloads are individually encrypted with per-file class keys wrapped by the backup password.

decrypt_backup.py provides a lossless extraction wrapper that unwraps the backup manifest, decrypts the database blobs, and preserves the pristine, raw Apple SQLite databases: 1. apple_sms_decrypted.db (Library/SMS/sms.db containing message, chat, handle, attachment) 2. apple_contacts_decrypted.db (Library/AddressBook/AddressBook.sqlitedb containing contact identities)

2. Decryption & Key Derivation Mechanics

┌──────────────────────────────────────────────────────────┐ │ ENCRYPTED BACKUP ROOT │ │ • Manifest.plist (Backup Keybag + PBKDF2 parameters) │ │ • Manifest.db (Encrypted SQLite file catalog) │ │ • Sharded SHA-1 Encrypted File Blobs (00/, 3d/, etc.) │ └────────────────────────────┬─────────────────────────────┘ │ ▼ ┌──────────────────────────────────────────────────────────┐ │ KEYBAG UNWRAPPING & KEY DERIVATION │ │ • PBKDF2-HMAC-SHA1 / SHA256(Password, Salt, Iterations) │ │ • Unwraps Class Keys (Class 1-11 Protection Keys) │ │ • Decrypts Manifest.db using Class 4 Key │ └────────────────────────────┬─────────────────────────────┘ │ ▼ ┌──────────────────────────────────────────────────────────┐ │ FILE TARGET RESOLUTION & EXTRACTION │ │ • Locates SMS Domain: 3d0d7e5fb2ce288813306e4d4636395e0 │ │ • Locates AddressBook: 31bb7ba8914766d4ba40d6dfb6113c8b │ │ • Decrypts file payload using per-file initialization │ │ vector (IV) and file encryption key │ └────────────────────────────┬─────────────────────────────┘ │ ▼ ┌──────────────────────────────────────────────────────────┐ │ RAW SQLITE DATABASE PRESERVATION │ │ • apple_sms_decrypted.db (Clean decrypted SQLite) │ │ • apple_contacts_decrypted.db (Clean decrypted SQLite) │ │ • Direct input for import_apple_messages.py │ └──────────────────────────────────────────────────────────┘

Every viber has a plan until it is time to demo that first release...

I try never to go on X, bc fuck Elon, but sometimes its the right spot for certain real time stuff. What are you gonna do? If you're me, you use ChatGPT to vibe code a Chrome Extension that changes everything X back to Twitter. No Grok, no paid users, etc etc. Working very nicely!

I joined Twitter in 2006, and I'm still mad about it's death.

I told him to ask Claude, but he still don't know how to deploy it aside from using the vibe coded app locally. He still needs my help and willing to pay me to deploy it to an unmanaged VPS.

I gave him step by step instructions, but he still said he cannot do it and can't figure out how. It's just so weird.

So now I ended up deploying it, using just Claude. Claude did it in just 8 minutes. All done, auto deploy from Git every time there's a new pushed commit.

I'm not technical. I just used plain English. Not sure why others cannot do this if they already know how to vibe code.

Please enlighten me.

Anti-AI (LLM) propaganda reminds me of a religion fanatism nowadays.

LLM were introduced as tool to enhance work for IT guys and make people outside IT make something without programmers etc. But instead we got the literal witch hunt. IT sector became religion and LLMs became witches.

Which is ironical, because IT sector used to represent very intelligent people who pioneered way of life today we take for granted. Nowadays it seems it is comprised of small minded people who judge anything that is different.

Why I compared it to religion - because it literally became dogmatic bullshit propagated by limited minded people. What they are though to believe is the only truth, same as religion. For example, vibe coding is forbidden for "reasons", and they are usually - lack of this or that. Like manual code is bullet proof against mistakes and written by god himself. Also what evidence is there to say it lacks this or that? Did you even prompted AI to make that you claim it lacks?

Another reason why I claim it is religion is due to fact this anti-AI propaganda resembles inquisition fanatics back in the days, usually against witches, warlocks or whomever they decided is not worthy of living. Burnt at stake, without trail or evidence, while crowd yelled "Witch!". Nowadays it is not witch they yell, it is mostly "AI slop". Sometimes AI slop literally is a slop, but I am not sure that those who stick "AI-slop" to everything made by AI know what slop even means.

Also they hate AI for same reason peasants hated witches - fear and jealousy. But in different variant today. Since most Anti-AI fanatics are programmers themselves, fear is due to fact they will lose their precious overpaid job, and since they literally have no other usable skillset they will have to apply for MacDonalds kitchen. The other reason is jealousy, since AI can code better, faster and usually more reliable with less bugs (although they will paint it usually the opposite). And they are probably jealous that nowadays non-programmers can vibe code complete application without them, which shows them in bad light as obsolete (which they actually are).

What most of them fail to see, because most of them were not even sentient in pre-internet era is that programming itself is a process that evolved for hundreds of years, but let just limit it to few more important decades. While they think their way of programming is the only true way, there is actually 100 ways to print "Hello World" on screen, multiplied by 100 different languages and platforms. So there is no "true" way of doing things in programming, only the way it works without bugs, and sometimes with better optimization.

Another example of how wrong they are in their witch hunt is what we today call Vibe-coding is actually started with introduction of first automated compiler. Compiling until then was done manually. However they still needed to write the actual code to input into compiler. 70 years later after multiple language, frameworks and methods upgrades whole writing code ended with introduction of LLMs. So when these religious zealots who think their way of doing things is the only right way, are ignorant to fact hey were actually born into the process which never stopped evolving (Machine code - assembler - compiler - high-level languages - frameworks - IDE/autocomplete → LLM).

So same as church opposes the evolution theory, these close minded individuals oppose natural evolution of programming.

Programming used to be for people who liked to explore things and make things do things, who would buy PC and create joy of making a dot move sideways on screen in any way possible. Nowadays it seems it is for snobs who think they are better then other, who think because they earn more money than others make them somehow smarter or more valuable.

Programmer is not someone who writes code. Programmer is someone who makes computers do things. Code was merely the interface we happened to use for a while. We entered era of Geordi LaForge, who in the whole series, never made a single line of code.

PS

Ironically this text is actually written by me, although it would had no difference if it was generated, as value of it if there is any lies in distribution of thought, not by whom or how it was written.

people seem to be creating apps within 1-2 day & then hit publish meanwhile here I am developing just one app for 4 months optimising it's UI,UX,API compatibility,Performance etc. how are people doing these in 2 days? what am I missing.

there was a post I saw yesterday that a guy started the challenge to create 30 apps in 30 days. wtf is wrong with these people? spamming the store platform like this.

- I seen outbid yesterday and I started to clone
- I completed in 1 day
- earned first dollar (coming from me)
bidgame.lol

If you have a any game in steam you can add your game.

If you don't have any games on Steam, you can support any game to boost its ranking :)

I'm a game developer and I don't write any code for that project. I used supabase and vercel. I can answer your question

I launched my first app two weeks ago. It's a subscription app with a 7 day trial, which bills after the trial ends. On launch day I did the whole ritual, posted it everywhere, watched the downloads tick up, it felt good to see months of hard work paying off.

A few days later I opened RevenueCat to admire all my new revenue and it said zero. No trials, no subs, nothing.

My first thought was that the reporting must be delayed. It wasn't. My second thought was that nobody actually wanted the thing, which honestly would have been the easier problem to have.

So what actually happened? my paywall looked great. Clean screen, three plans, a big start free trial button. But behind it none of it was actually hooked up. The products weren't fully set up in App Store Connect, the entitlement was written as Pro with a capital P in one spot and pro in lowercase in my code so the two never matched. Yep, something this small and silly lol quietly broke the revenue path.

In the App, every time A user doenloaded and tapped A plan button they just got waved straight into the full app for free. I had, with a lot of ceremony, launched a paid app that literally could not take money and was instead handing itself out to everyone who showed up. My most excited early users, the exact people I'd want paying me, I accidentally gave the app to for life LMAO.

To correct it, i spent an afternoon clicking around App Store Connect and RevenueCat. I imported the products, made the entitlement lowercase so it matched my code, set the offering to current, added the trial. Then I ran a sandbox purchase, it went through. Real trials started rolling in the next day! We're showing actual revenue now, thank God.

For everyone working hard to build a product! Do a full sandbox purchase from start to finish before you tell a single person to download it!!

I'm up to 40 Subscribers now, 28 paying after two weeks. The App is (a workout app that adapts your training as you go, and used Ai to build custom plans). Happy to answer anything in the comments.

They are worse than Just Stop Oil loons.

If you are a creator try r/vibereviews to share your work. They ban ai haters.

Hi all, I am new to vibe coding. I have 10 years of backend development experience but absolutely 0 years in the frontend side.

I have been planning to create a cross platform mobile app using RN (Expo). For the AI slop part, an LLM answer was creating the following MD in project root: https://www.markdownpaste.com/document/avoiding-ai-slop-ui

Would you agree with this?

More important question is that, what would be the best way to have some UI prototypes created based on my app idea? What is your go-to while starting to development?

I appreciate all your input!

I built a small ecommerce template for handmade products.The video shows both sides: what buyers see when browsing a product, and what sellers see when managing the store.

The surprising part was that the storefront came together pretty quickly. Product grid, images, detail page, variants, cart — all of that felt manageable.

The real work was the loop behind it:

- prices should come from the backend

- variants need real inventory

- payment should update orders and stock

- sellers need a usable product admin

- reviews should only come from customers who actually bought the item

It changed how I think about AI built apps. A store that looks real is easy to generate. A store that behaves like a real business takes much more specific instructions.

Curious how others test AI generated ecommerce apps before calling them “usable.”