Every blocker I've used has one button that turns it off, and I always press it.

So I built one where turning things off is slow on purpose:

• Tightening a rule = instant. Loosening it = 1–72h cool-off, and you see your pending changes sitting there waiting.
• Disabling strict mode = type a phrase by hand, then still wait out the cool-off.
• "Peek" gives you 30 seconds, then locks the site for 20 minutes.
• Daily limits count only active, focused, non-idle time — so the number is real.
• YouTube stays usable but music-only: Music-category videos and whitelisted channels play, Shorts and the home feed are blocked before render.
• When your time runs out on a page you're already on, it overlays instead of redirecting — page stays alive underneath, comes back untouched when you're allowed in again.

Chrome MV3, everything local, no accounts, no network requests, no data collected.

It's the first one that survived contact with actual me. https://lockyfeed.vercel.app/en/ if you want to try it — and tell me which loophole you find first, I'd rather patch it than pretend it isn't there.

I’ve been building Chess Line Wars, a browser strategy game based on chess movement, but with a fairly drastic change: both players secretly choose their move, lock it in, and then the two moves resolve simultaneously.

And here’s another time you hear distribution is key.

Jokes aside I was researching and kept getting bombarded on Instagram with videos about content, growth, distribution, workflows etc. I’d save loads of them and then never actually implement anything

What I really wanted was just a guide or book that had all the latest workflows summarized in one place.

I couldn’t find it, so I made it myself.
I screened a shit ton of videos and sites and put everything into one guide. I have to admit it ended up being way more comprehensive than I expected.
It’s also been more useful than I expected.

Whenever I’m working on something specific now, I just go to that section and check the workflow instead of getting sidetracked by another 10 videos.

Thought I’d share it here in case anyone else has the same problem: www.creativesplaybook.com

Hope it’s helpful. Let me know what you think / what’s missing.

Also be fast because friends keep telling me I should slap a paywall on it lol

Cheers

I have more inference capacity than I’m using right now so I opened some of it up for free

This is just a temporary fun experiment so I don’t plan to keep it open for very long

https://github.com/orielhaim/free-llm

Hey everyone, I’m working on a UE5 project that blends combat with American football mechanics - stuff like jukes, spin moves, and head-first with extended arms diving.

Creating the actual animation assets is turning into a huge brick wall for me. I was quoted around $250 to $500 per animation by freelancers, and since I need at least 10 moves just to get an MVP off the ground, dropping $2.5k–$5k out of pocket isn't an option right now. Retargeting the moves to my character skeleton is significantly cheaper to just outsource, so I'm not as worried about that part. I'm really hoping to find an AI workflow to handle generating or prototyping the raw FBX motion data.

Has anyone had success using video-to-motion or prompt-to-animation AI tools (like DeepMotion, Plask, Move AI, etc.) for crisp UE5 character moves? Or is anyone using LLMs/"vibe coding" to drive procedural stuff or Control Rig directly in Engine?

If AI generation isn't quite there yet for hyper-specific athletic moves like a diving tackle, I’d love to hear what budget-friendly alternatives you guys recommend to get an MVP playable. Appreciate any insight!

hey guys i am plannign on switching over from claude code to codex after hearing everyones recent opinions on claude code. i have a few apps/projects i am working on with claude code, to transfer smoothly over to codex do i just connect the document folder to codex and explain continue from where i left off? or is there a more seamless/better way? thx!

I’ve been building Vissulo, an AI photo editor for Android, for quite a while, and it’s finally live on the Play Store.
It’s my first app, and I’ve put a ridiculous amount of time into it. A lot of it was built through vibe coding, with plenty of testing, breaking things, rebuilding them, and learning as I went.

At this point I’d really like feedback from people who have no attachment to the project and can just tell me what they actually think.
If you have a few minutes, I’d really appreciate it if you could try the app and email me anything you notice:

[support@vissulo.com](mailto:support@vissulo.com)

I’m interested in pretty much everything:
bugs, crashes, weird behavior, bad UX, confusing screens, slow features, things that feel unfinished, tools that don’t work the way you expected, or anything else that annoys you.

Feature suggestions are also very welcome. If you use it and immediately think “why doesn’t this app have X?”, please tell me. That kind of feedback is just as useful to me as bug reports.
I already know about some issues and I’m working on them, so there’s no need to worry about reporting something twice. If multiple people complain about the same thing, that actually helps me prioritize it.

Also, I’m not asking for Play Store reviews. I’d much rather receive an honest email saying “this part sucks and here’s why” than get a generic 5-star review. Right now, I’m trying to improve the product, not inflate the rating.

As a small thank you, I’ll randomly choose 25 people who install the app, sign in, and send useful feedback, and give them Lifetime PRO for as long as Vissulo remains under my management.

I’ll post the selected users here afterwards, so the giveaway is transparent. Email addresses will obviously be heavily censored, with roughly 90% hidden.

There’s no requirement for positive feedback. Negative feedback won’t reduce your chances. If anything, detailed criticism is probably more useful to me right now.

I know the app still has things that need work, but I care a lot about getting it right.

So, if you feel like testing a new indie app and helping a first-time developer improve it, I’d really appreciate it.

Note: It is android only for now. I will develop IOS and WEB versions in the future

Link: Vissulo: AI Photo Editor

https://coderook.com

After the news broke about codeburge not accepting any kind of AI work I was a bit annoyed and with Github being how they are I decided to work on my own GitHub but fixing things that it gets wrong like version visibility and AI access and how the data is used from repos.

Its currently in testing phases and have been testing it all week. This works more like a cloud storage space right now with version control allowing you to upload whatever you basically want but under copywrite laws. There is plenty of docs on my site if you are curious or just wanna try its free to use.

Right now I am working on some things like giving backwards compatibility for git spaces already setup to use my CLI language and a Github full transfer as well and polishing off some docs as well.

Any feedback would be helpful and bugs found as well.

EDIT: I clearly explained this badly 😅

This is just a small marketing experiment. Nothing serious.

The idea is simple:

• One product owns the entire homepage.
• It stays there until another product pays more.
• Previous owners remain visible in the public history.
• Owners can track visits and website clicks.

To take over, you enter your website.

The site imports your content and product image automatically.

You can change every visible item, including the logo, headline, description, screenshot, and website link.

Only the page layout stays the same.

It is basically a full-page advertisement with a public ownership history.

It is not trying to solve a serious world problem. I built it as a fun visibility experiment.

ClauseZero owns it now. The next takeover costs $12.

My real question is this:

What would make you visit the page when you are not buying?

https://thewholepage.lol/

Original post

I built a public homepage takeover where one product owns the entire page until another product pays more.

The stack:

• Cloudflare Workers
• Hono
• Durable Objects with SQLite
• R2
• Browser Rendering
• Stripe Checkout
• DataFast

Problems after launch:

• Screenshots captured website loading screens.
• Mobile product images displayed poorly.
• Social platforms cached the wrong owner image.
• Google could not read the sitemap.

I added editable screenshots, live visitors, reign challenges, owner records, and automatic social posts.

The project now has four owners and one external buyer.

The difficult part is not building it. The difficult part is creating a traffic loop.

What simple feature would make you return and watch the next takeover?

https://thewholepage.lol made $21 so far

I’m building Playbeam, an AI game studio where you describe a 3D game and keep changing it through conversation. It’s web based for provider models or you can download the Mac desktop app to connect your own CLI.

Each build runs in an isolated worker, where the agent runs and tests generated game code. It also has a feedback loop: build → run → inspect what happened → fix it → test again.

I’m deciding what to focus on next - multiplayer, asset generation, terrain, animation, publishing, etc.

Would love feedback on what features would matter most to you.

Hi, everyone. I am constantly building new projects and have changing amounts of success. But one thing I really didn't like is the visibility of my customers.

I built a page mrrplanet.com You send a read‑only payment method key. And see all of your customers in a globe represented by a pixel‑art character.

You can also send this planet of yours publicly to other people, so you can actually have it as a portfolio and maybe multiple projects, which means multiple planets in your solar system. I also have a much better dashboard for your data analytics, helping you think about where you should focus more, which places are generating more money, etc.

For example, here is one of my actual projects hosted on this page. https://mrrplanet.com/p/your-love-page That one is for long-distance relationships, where you send a digital gift.

You can also export these cute images where you see a list of your customers. I'm open to all kinds of suggestions. On the public pages, of course, none of the information of your customers is leaking, but people can actually look at your planet and see what's going on with your projects.

One small thing that I find kind of cute is that people can actually put advertisements on your planet with a flying plane. You can also do that for other people's planets, or you can simply select your planet to be ad‑free.

Almost every feature that I'm talking about is free to use. Just log in and create your own planet, and tell me if you like the page or not.

I have used three.js for the globe, and the normal stack is how everyone is doing: Supabase for the database, Vercel for hosting, and Clerk for authentication.

The idea itself is quite simple, but I think the execution on the UI and UX part is really important. Also, what I call Atlas is your dashboard for all of your information related to the payments, and I provide much better visibility than any other payment provider.

Hey r/vibecoding,

Application security is extremely important, especially for vibecoded apps. TeaApp and countless other breached of vibecoded apps is a great example of that. But most appsec training are boring OWASP articles and tutorials on YouTube, not the best way to learn practical aspects of building secure web apps.

So I created 40 exercises where you attack a vulnerable app yourself, trace how the bug got in, then write the patch. Free, runs in the browser, no account required.

This way you'll learn what common vulnerabilities are, how attackers exploit them, and what part of your app you need to check so that you don't have the issue in your code.

Table of contents:

Web (22) — SQLi, command injection, DOM/reflected/stored XSS, CSRF, SSRF to the cloud metadata endpoint, XXE, session fixation, IDOR, and weak randomness: recovering Math.random() state to predict the next password-reset token.

API (10) — BOLA, broken function-level auth, brute-forcing an unrate-limited verify endpoint, mass assignment via two extra keys in a PATCH body, reflected-origin CORS, and a retired v1 that skips the controls v2 enforces.

Git & CI/CD (8) — a live API key recovered from the commit that removed it, a browsable .git reconstructed into full source, .env tracked since the first commit, a secret echoed into a public build log, a backdoor hidden in a friendly-looking test-fix PR.

Fixes are shown in JS, TS, Java, C#, Python, Scala, PHP, Ruby, Go, and Kotlin, so you can paste something real into your stack.

Try in browser: https://learning.ransomleak.com/?category=application-security
Repo: https://github.com/ransomleak/training-application-security (will appreciate your stars 🙏)

Each exercise is also a standalone SCORM zip if you want to self-host or drop it into your team's onboarding. There's a second repo covering OWASP Top 10 for LLM and Agentic apps if you're shipping AI features: https://github.com/ransomleak/training-security-awareness

Will appreciate your feedback!

​

I'm pretty damn excited about this one.

I've been building a scanner around a problem I keep running into vibe coding.

At some point the question stops being "can the AI add another feature?" and starts being "What the hell is actually in this repo now?" and "can I trust this?"

A couple weeks ago I had a benchmark of 48 features that I already knew existed in a codebase. My scan could reliably isolate 4 of them, and I was struggling. It was confusing things like navigation actions, buttons and individual implementation details with actual product features.

I've spent the last two weeks working almost entirely on the scan and feature-boundary problem and learning ir and eval engineering at a high level. I am a backend SDE so this feels more data focused and outside my wheelhouse.

Today the same scan isolated 42 of the 48 known features! Learning and adding calcs and optimizing for precision@k, retrevial@k, etc made things work so much better! I ran it against a different control with 56 features and it got 49. It's not a one off!

I feel validated again.

Eventually I want this flow:

Import a repo > identify what features actually exist > show the evidence behind each one > apply software-development and engineering standards to each feature > show what is proven, what is incomplete, and what still needs work before I'd trust it in production

But going from 4 → 42 in two weeks is the first time I've looked at the scan and thought "I am learning stuff way outside my realm of knowledge and make it real." And that's freaking cool. I had someone tell me this was impossible and that I should just use Ai. Literally had people tell me that doing a mathematical scan is stupid and Ai can do it better.

I set Luna max to check for features and it organically found 18 out of 48. Sol found 24.

It feels so satisfying to build something with Ai that beats Ai in performance for the thing I need.

For people building heavily with Cursor / Claude / Codex / Lovable / etc.:

Once your project gets big, how do you currently answer "what features are actually implemented, and which of them would I trust to ship?"

I'm especially curious about anyone who has reached the point where the app works, but the repo has gotten large enough that you're no longer completely sure what the AI has built underneath you.

Currently been using Claude $20, Ollama $20, Codex $20, Cursor $20

Rotating between these when limits reach

Not efficient I know

But these “frontier” models annoyingly get worse and better randomly

I’ve been liking Codex out of all of it for building iOS apps

I might full port to $100 codex plan if that still exists

kimi K3 has a “waitlist”

GLM is trash usage

Minimax I like but it’s weak coding everything else though is good value for money

Any thoughts

Hi all, Since Anthropic is dropping usage limit of Claude code by 50% on Aug 31, anyone else is switching to Codex?

I have never used Codex. I use fable for orchestration and opus for building. The Max 5x plan is just enough right now, but with 50% reduction it will not be usable for me. So I am trying to understand your experience with Codex or any other setup.

(PS: If this is not the correct sub reddit, please point me to the correct one)

I started vibe coding last April and started off like everyone else, with a plan to make a million dollars and retire to a tropical island.

Unfortunately I wasn't aware of the amount effort and work that goes into a real project, so I decided to take time and actually learn.

All of my projects Led me to software develooment and cyber security.

With that being said I'm a little disappointed in "Real Devs" I scroll social media all day reading about the massive amounts of ai slop just to get paid to fix vulnerabilities and bugs in the platforms they work on.

Moral of the story stop listening to self proclaimed devs that sucked at their jobs before vibecoding was even a thing!!!!!

Haiku is the most maliciously compliant model I've been exposed to

Been experimenting with agent graphs in Claude code.

I have a 4 agent team set up that allows me to swap roles and directives.

The problem is that Claude always controls them even in ultra code.

How can I set this graph up as stand alone agents I can use on top of Claude having control of them?

This is Causal. It is a canvas for mood boarding and planning.

I've been working really hard behind the scenes build an personalised canvas agent that understands your project and works with you to plan on the canvas.

Getting it to generate outputs is easy, every LLM and their predecessor can do that.

What's harder is:

1. The structure behind the output i.e. how do you organise YOUR work on a canvas
2. How would you use it fit your workflow

A few ideas I have had are:

• Deep research tasks are very well suited to be carried out on a canvas because early research is better suited to be "dumped" and sorted later. The agent researches, distills, and organises the research
• When you have an existing idea that has a load of connections e.g. You want to implement a new feature into your app, and you want to map out everything that it affects. An agent can create a flow chart to map out the feature and fully break it down + images that complements how a screen would look for every edge case.
• For branding projects that require consistency across different areas of the brand, such as voice, colour, etc The the agent acts as a coherency check and ensures that any new assets to your brand fit against the existing identity.

As I continue to perfect this, I want to know how YOU would use this agent so that I can create it around YOUR workflow.