
dev https://nitter.gq/t.co/2qXSTlt9fz https://nitter.gq/t.co/T3Ug1EH4Zh @coingmi_com
Norway
Joined September 2009
- Tweets119
- Following313
- Followers522
- Likes3.4K
I built a thing that replays the crypto market, the top 1000 on one board, rewindable to any day since Aug 2025. Press play and watch a year happen.
official handle: @coingmi_com
coingmi.com/
Replying to @oklar @coingmi_com
You can also watch top 50 from aug 2025 until today
coingmi.com/?d=2025-08-26&fo…
64
I made infiniteslop.ai yesterday completely on my phone with @TermiusHQ on my @Hetzner_Online VPS with @claudeai Code in the sauna while in a group chat of my friends with @marcantoinefon in it
levels is so fast I stopped using AI, i just prompt @levelsio directly, much faster!
seriously, we started discussing the idea at 2:30pm utc, 10min later he said “k i do it”
first version online at 3:18pm, we test, he tweaks some stuff and iterates for 1h30, decide about name, chat about it with @fal and launch at 5:30pm.
3 hours from idea to launch, everything done from his phone while going around his day, insane execution
I laugh when I see people in holding their laptops half open so their Claude Code doesn't shut off
All my projects run on a @Hetzner_Online VPS with Claude Code installed next to the sites/apps that I work on and I just SSH in with @TermiusHQ and it keeps going forever even if I disconnect (I use Mosh or Tmux or I just /resume)
My MacBook Pro battery life is also much better as everything happens on the server not my laptop
I work so incredibly fast now, it's like having a secret benefit over everyone else who are still AI coding on a laptop, then deploying to their server, while their battery life dies and they can never close their laptop
And whenever I want I can just switch to Termius on my iPhone and continue working!
My workflow is literally: I have a bug or feature, I open Termius, I type it in the project tab, it fixes it, every fix it auto commits to GitHub but it doesn't actually deploy from there anymore because it's editing the site on the server live
I don't recommend that to everyone, but I do recommend getting a VPS you can code from and then use as staging and test and deploy from there to your production server
🏆 For the first time in a decade on @Stripe I've started winning disputes with my vibe coded dispute responder
I used to ignore disputes so I almost always lost them, now I've started winning, this one is the first big dispute for $1,199 USD!
Whenever a dispute comes in, my site gets a webhook notice from Stripe, it then starts collecting evidence and generates a PDF with entire user's details, when they signed up, and most importantly what they did in the app
In this case the user used the app for months, generated thousands of photos then tried to get the money back from their bank
The evidence has to be REALLY detailed, and REALLY good, which is why it's perfect to vibe code it, you can get quite detailed with different types of users and activity on your app, and put that all in the PDF
I'm shocked because I again I never would win disputes before
People in US especially abuse the [ chargeback ] or [ dispute ] en masse, unlike the rest of the world, it's easily built into their banking app next to every transaction, so it's one tap to get free stuff. And why not? You get free stuff!
It's destructive for business owners like me on many levels, if I get over 1% disputes on my account, I risk getting shutdown permanently by Stripe, Visa and MasterCard, like permanently for life, not just my business but on my personal name too, it's ruthless
Disputes are also super expensive for business owners: you don't just pay back the amount they disputed, for every dispute you pay $30, which you only get back if you win!
But with AI we can now create our own tools to fight back against dispute abuse and finally win! 🎉
✅ Done
💳 Made an auto-dispute response system for Interior AI to see how easy it'd be
It syncs old disputes but also catches new disputes via Stripe webhook and then auto submits evidence to try win them, it even includes the interior designs they generated in the evidence PDF to prove they used it!
Here's the prompt/skill I made:
----
Build an auto-dispute-response system for Stripe that:
1. Shared evidence collection (app/dispute_evidence.php)
Create a shared file with functions used by both the webhook and sync worker. This avoids duplicating evidence logic.
Key functions:
- getDisputeUserPlan($user, $stripe) — pulls the user's subscription plan from Stripe API (source of truth, since local DB plan field gets cleared on cancellation). Falls back to local DB fields if Stripe call fails. Maps product IDs to plan names and includes price/interval and canceled status.
- collectDisputeEvidence($stripe, $user, $email, $charge, $photosDb) — collects all text and file evidence, returns an array ready to submit to Stripe.
- generateServiceDocPdf($stripe, $user, $email, $photos_done, $recent_photos, $total_amount_paid) — generates a PDF with customer info, usage summary, recent activity table, and up to 6 actual product images (resized to JPEG at 500px wide / quality 75 to stay under Stripe's 5MB file upload limit). Returns both the Stripe file ID and raw PDF data.
Important: pull total_amount_paid from Stripe charges API (sum of succeeded, non-refunded charges) instead of trusting the local DB which can be null/stale.
2. Webhook handler (in stripe_webhook.php)
Catch `charge.dispute.created` events. When a dispute comes in:
- Get the dispute, charge, and customer objects from Stripe
- Look up the user in the local database by stripe_customer_id
- Save the dispute to a `disputes` SQLite database (fields: dispute_id, charge_id, payment_intent_id, stripe_customer_id, user_id, email, amount, currency, reason, status, epoch_created, epoch_evidence_submitted, evidence_json, stripe_response, epoch_resolved, outcome)
- Call collectDisputeEvidence() to collect all evidence (text + file uploads)
- Submit evidence to Stripe via $stripe->disputes->update($dispute_id, ['evidence' => $evidence])
- Send a Telegram notification that a new dispute came in and evidence was auto-submitted
Also catch `charge.dispute.updated` and `charge.dispute.closed` events to track dispute outcomes (won/lost) in the database and send Telegram notifications with the result (with emoji: checkmark for won, x for lost, warning for other).
3. Evidence fields submitted to Stripe
TEXT fields (write strings directly):
- product_description — describe what the product/service is
- customer_name — from Stripe customer object
- customer_email_address — from Stripe customer object
- access_activity_log — detailed usage log: signup date, number of items/actions done, last active date, subscription plan (from Stripe), platform, total amount paid (from Stripe), recent activity with timestamps
- uncategorized_text — the "why we should win" argument: customer signed up on X, actively used the service doing Y things, total amount paid, service was delivered digitally/instantly, customer never contacted us for a refund before disputing
- refund_policy_disclosure — when the refund policy was presented (during checkout, always accessible at /legal)
- cancellation_policy_disclosure — when cancellation policy was shown (during checkout, accessible at /legal, can cancel anytime from dashboard)
- refund_refusal_explanation — customer didn't contact us for a refund before filing the dispute
- cancellation_rebuttal — proof customer actively used the service and never requested cancellation
- service_date — date of the charge (Y-m-d format)
FILE UPLOAD fields (upload file to Stripe first via $stripe->files->create(['purpose'=>'dispute_evidence', 'file'=>fopen($path,'r')]), then pass the returned file_xxxxx ID):
- receipt — pull the invoice PDF directly from Stripe ($stripe->invoices->retrieve($charge->invoice)->invoice_pdf gives a ready-made PDF URL, just download it and upload as dispute evidence)
- service_documentation — generate a PDF containing: customer info section, service usage summary, recent activity table, and up to 6 actual product images/screenshots the customer received. Resize images before embedding (500px wide, JPEG quality 75) to stay under Stripe's 5MB file upload limit.
Also save both PDFs to your file storage (e.g. Cloudflare R2, S3) with hashed filenames so they're not guessable but viewable from the admin dashboard.
Store the storage URLs in the evidence_json as _receipt_r2_url and _service_doc_r2_url (underscore prefix so they're easy to identify as internal fields).
DO NOT use these fields for text — they expect file upload IDs only:
service_documentation, cancellation_policy, refund_policy, customer_communication, customer_signature, receipt, shipping_documentation, duplicate_charge_documentation, uncategorized_file
4. CLI sync worker (workers/syncDisputes.php)
A script that pulls ALL existing disputes from Stripe's API (paginated with $stripe->disputes->all(['limit' => 100]) and starting_after for pagination), saves them to the local disputes database, and for any that still have needs_response or warning_needs_response status and haven't had evidence submitted yet — auto-submits evidence using the shared collectDisputeEvidence() function. This is needed because the webhook only catches future disputes, not existing ones. Too heavy to run on frontend — run via CLI only (php workers/syncDisputes.php). Saves a JSON cache file with sync results so the dashboard can show last sync time.
5. Mini dashboard (disputes.php with ?key= auth)
A simple HTML page protected by ?key= query parameter that shows:
- Stats boxes: total disputes, pending, won, lost, disputed last 30 days (amount + count), disputed last 12 months (amount + count), total $ disputed
- A note showing the CLI sync command and last sync time from cache
- A test form where you enter a stripe_customer_id to preview what evidence would be submitted (without actually submitting) — useful for debugging
- A table of all disputes: date, email, amount, reason, status (color-coded badges), evidence submission status, links to both detail view and Stripe dashboard
Detail view (action=view&id=dispute_id):
- Shows all dispute info, link to Stripe, and a "Regenerate Evidence" button
- Shows PDF file links (receipt + service documentation) if available
- Shows Stripe file upload IDs
- Shows all text evidence fields
Regenerate Evidence (action=regen&id=dispute_id):
- Regenerates the receipt and service documentation PDFs and uploads to file storage
- Updates the evidence_json in the database with new PDF URLs
- IMPORTANT: Use fastcgi_finish_request() to send the HTTP response immediately (redirect back to detail page with "regenerating in background" notice), then continue generating PDFs in the background. This prevents frontend timeouts since downloading images and generating PDFs can take 30+ seconds.
Add an nginx rewrite for the page (e.g. rewrite ^/disputes/?$ /disputes.php). Make sure it's in the correct nginx config file (check which one the symlink in sites-enabled actually points to).
6. Telegram notifications
- New dispute: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence auto-submitted to Stripe. {stripe_dashboard_link}"
- Evidence failed: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence submission FAILED: {error}"
- Dispute won: "{site name} - Dispute WON (checkmark) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- Dispute lost: "{site name} - Dispute LOST (x) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- DB permission error: "{site name} - DISPUTE DB ERROR: {error} - check permissions on data/disputes.db"
7. Make sure these Stripe webhook events are enabled in the Stripe dashboard:
- charge.dispute.created
- charge.dispute.updated
- charge.dispute.closed
8. Database permissions
The disputes.db file must be writable by the web server user (e.g. www-data). If you create it from CLI as root, fix ownership to match your other DB files. PHP-FPM runs as a different user than root.
9. Dependencies
- FPDF (setasign/fpdf) for PDF generation — install via composer require setasign/fpdf
- GD extension for image resizing (usually already installed)
- Stripe PHP SDK (already installed if you have Stripe webhooks)
- AWS S3 SDK for R2/S3 uploads (already installed if using Cloudflare R2)
Olav retweeted
If you’re starting a B2B SaaS you should think about $100 problems or $1000 problems.
Don’t think about $10 problems.
If you’re solving a $1000 problem and charge $79 for it, you’ll have customers.
If you’re solving a $10 problem and charging $15 for it, you’ll struggle.
This is a tough product space.
I have failed in this space previously, and I know at least one other indiehacker who has tried and failed.
While you can point to one or two examples of startups who might be doing ok in this space, I just I think it's too small and challenging for new entrants.
You're a SaaS targeting other SaaS businesses (small market)
Who are releasing features with such velocity that they need a system to manage announcements (smaller)
Who are actually experiencing pain from this (smaller-er)
Who are comfortable with adding yet another JS embed to their site from an unknown 3rd party (smaller-er-er)
The list goes on. Eventually you realise that your realistic total market is tiny.
You can't build a business on $12 / mo subscriptions with a product like this.
The only way it might be feasible is if you charge 100x that amount, and aim it squarely at large enterprises, with specific enterprisey features for those types of customers.
Over the last 20 years I've seen loads of these tools start at a cheap price point, realise it's not feasible, then progressively move up market.
Olav retweeted
Penetration-free for free, you need OGC.
I released the code of our SIGGRAPH 2025 paper: Offset Geometric Contact, where we made real-time, penetration free simulation possible, with @JerryHsu32 @zihengliu @milesmacklin @YinYang24414350 @cem_yuksel
Page: ankachan.github.io/Projects/…
Olav retweeted
Being a prey is not the best situation🤡. New "better" approach on the "gameplay", "more" action, "less" worrying💪 To be fair I don't really know🤪
#IndieGameDev #indiegame #indiegames #UnrealEngine5 #solodev #indiedev
Olav retweeted
Ok so after tweaking and playing with Godot, i now got the kind of render I was looking for, and god it looks awesome !!, wow ! It truly shines when you play with volumetric fog and volumetric lighting
#godot
Olav retweeted
I think secretly, Slots & Daggers is my love letter to game-feel.
I've spent an ungodly amount of time on animations, sounds, getting the freaking screenshake just right and other obsessive details...
I love this stuff, please send your fave game feel & juice examples! 🖤🎰
Olav retweeted
daily reminder that one of the most important tech discussion sites on the web uses tables for layouts & basically your stupid
Olav retweeted
htmx stans going hard in the comments
(no problem w/people going w/wordpress if it makes sense, but htmx is NOT gonna break their site)
Olav retweeted
Missing that `Copy as markdown` button?
I was, so I shipped a fix this weekend:
Just type ✨ i n t o . m d / ✨ in front of any URL.
Get clean, LLM-friendly markdown for any website or docs page.
Olav retweeted
Half of the visitors to omarchy.org in the last month came from within Apple's walled garden. Love to see so many people from there discovering a new, different way of computing. Linux now has all the bits to make a big dent in Apple's capture of dev mindshare.
Olav retweeted
WTF... First they said no to Elon Musk.
Then they built an AI that just shook the entire LLM industry.
– 27M parameters
– Trained on only 1000 examples
– Inspired by the human brain
– Beat Claude, o3-mini & Deepseek
You can’t afford to ignore this: 🧵
Olav retweeted
daily reminder that htmx (& the hypermedia model more generally) does NOT require a server round trip for every interaction & in many cases can be *more* efficient than a chatty JSON API by encouraging the single-request-for-a-UI pattern
easy when the request response IS the UI!
Olav retweeted
Cars, bridges and houses are constantly battered by the elements, Software is made out of bits, that do not degrade. It stays the same. So why does software require so much more maintenance than cars, bridges and houses? youtube.com/watch?v=EGLoKbBn…
Olav retweeted
I think ironically my super simple code base with just PHP, JS, jQuery, SQLite is excellent for AI coding because it's so basic, simple and "dumb"
No complicated things so AI fucks up less


































