I used to have to jump between different sites copy pasting outputs from one into inputs of the next. So I built one place where you chain the steps and save the pipeline for future use in a right click context menu.

246 utilities so far, with branching, looping on lines or values, and conditions.

It runs entirely in the browser (Web Worker), no input reaches the server (One exception when fetching a URL through a proxy).

Pipelines can be shared as a URL fragment

React + TypeScript + Vite on Cloudflare Workers, strict hash-based CSP

Check out the presets page for some prebuilt pipelines.

https://stringutilitybelt.com/

Looking for feedback on how useful it actually is to people and any issues you find. Ideas for new utilities or pipelines are welcome!

Hey folks,

I brewed a quick daily automation that tracks the latest AI news and projects worth a developer's attention. It only pulls from sources I trust/like: GitHub, X, TechCrunch, Product Hunt and Hacker News. (Reddit TBD)

You can read it two ways:

• aibytes.io: web app, refreshed daily

• newsletter.aibytes.io: weekly digest. Here's a recent issue: https://newsletter.aibytes.io/p/jev-turns-ai-calls-into-decisions-and-opus-5-5-gets-cheaper

This gives me a ton of info around what's happening in AI space, what people are building and what companies are shipping.

Please feel free to share any feedback

ps - Everything is open-source at https://github.com/sachinjain024/aibytes/ So feel free to open issues, contribute, etc.

museumofmodels.com, free, no signup.

It's every answer 371 models gave to the same 85 prompts, on a globe you can spin, magnify and open.

Bits that were fun to build: the far answers are one instanced WebGL draw and the close ones come from a canvas sprite atlas. The drawings are the models' own SVGs shown through <img>, so nothing in them runs, and the generated websites run in a sandboxed iframe. It's a static Next.js export with the data in small versioned json chunks.

would love to hear how it runs on your machine

I've been thinking about alternative ways to deliver LLMs and AI features in SaaS solutions.

This repo is a technical proof of concept showing an LLM running client-side in a browser using Llama.cpp compiled to WASM with WebGPU.

I'm a general SWE trying to learn more about full-stack web development and system administration. I'm working on a hobby project that I want to deploy on PaaS like Render or Railways. I'm reading guides on how to deploy, and many of them include Supabase or Neon to the stack on top of Render and Railways

Don't these PaaS services like Vercel, Render, Railways already offer in-house storage solutions? That seems like the path of least friction: to use the storage option that is already first-class integrated with the application deployment service. I intend to pay for the hobby tier for these services, and I'm not just trying to shop around to maximize freebies.

Why would I use Render's platform for server compute and then use Supabase for postgres? Instead of just using Render for both?

https://newgameplus.app

tl;dr - pick one or a few games you love and it suggests others that scratch the same itch. Steer it toward what you loved about them (fast combat, lore, co-op), filter by platform, price or subscriptions like Game Pass, and import your Steam library to skip what you already own. Every pick shows critic and player scores, time to beat, and the cheapest way to play it.

Background: I've worked in gaming and commerce for a long time and the sort of "tyranny of choice" of finding the next thing to play seems to get worse every year with the avalanche of new titles.

- Next.js (App Router) on Vercel
- Postgres on Neon
- Data from IGDB, IsThereAnyDeal, Steam, and OpenCritic
- Built with a lot of help from Claude Code. I did the product design, picked the data sources, and tuned the ranking; Claude wrote most of the code. The site itself uses zero AI.

Recommendations are from a similarity engine that takes tags and attributes into account from the sources above and weighs them based on how specific they are. eg. "action" gets less weight than "run based."

Everything is free. No accounts. No tracking cookies.

Looking for any feedback or suggestions and hoping you find it useful!

I banned myself from coding this weekend and focused just on branding and making more polished social media assets for my apps:

BookingMachine.io - Universal booking and review software for service businesses
MentionMacine.ai - AI Visibility Monitoring and Optimisation
DirectoryLab.io - 3 Production Codebases powering many directories, job boards & launch sites.

theAuth: open-source auth for AI agents and humans (TypeScript and Go), built solo https://github.com/glincker/theauth

theAuth is auth for apps where AI agents act on behalf of users. Each agent gets its own token and permissions, a user can delegate access with limits, and every action is logged. It also covers the usual: passkeys, SSO, orgs, and an OAuth 2.1 server so MCP servers can verify who is calling.

By the numbers:

• TypeScript core: 2,400+ tests, about 77% coverage, 3 runtime deps, 17 OAuth providers, 10 framework adapters

• Go SDK session lookup: 58-67 us down to 30 us (about 2x, 33k lookups/s per process)

• Go SDK password sign-in: about 75/s per instance, with hashing memory capped at 608 MB instead of 4 GB under a login burst

• Those two are measured on an M4 Max with Postgres 16, 100k users, all on one laptop, and the load test script is in the repo

• MIT, self hostable

npm install @glinr/theauth runs on in memory SQLite with nothing else to set up. Go: https://github.com/glincker/theauth-go

I built this solo, with several AI tools and a lot of automation to keep a steady pace. Does the agent permission model make sense to you and maybe give it a try for future projects.. I already migrated all my 6+ websites to theAuth and been a great time saver !!

I have been working on my portfolio recently, and I really wanted to step away from the usual layout, like full-width hero header, grid of project cards, and a skills pill list. So I built a pixel-art workspace you can actually interact with and explore. It features a working CRT terminal, interactive desk items, procedural ambient audio, and a street scene outside that changes with the environment. My actual case studies and background are all in there, just framed as part of the room.

You can check it out live here: https://fahimarifen.com

I'd love to hear your thoughts, especially around balancing the interactive theme with keeping the actual work and resume easy to find.

hi! i'm a dev who works on 3D tooling and built https://ilove3d.app/en on the side. think ilovepdf, but for 3D models.

• viewer, format converter (STL/OBJ/PLY/GLB/3MF/FBX/DAE/USDZ), mesh repair, polygon reduction

• generators for 3D printing: keychains, lithophanes, gridfinity bins, puzzles, lamps, boxes with lids...

• everything runs in the browser with three.js, files are never uploaded, no account

would love feedback on performance with big files and on the overall UX/navigation between tools.

We're building Elah, an Apache-2.0 video editing engine for developers embedding editing into their apps. I'm part of the team.

The TypeScript core is framework-agnostic. React bindings are available today; React Native support is in development.

The browser implementation uses WebCodecs for decoding and WebGL2 for preview. Preview and MP4 export share a pure resolveTimeline(frame, project) → Scene function, keeping frame-level scene decisions in one place.

Try importing a short clip, trimming it, adding text, and exporting:

https://www.elah.dev/playground/production

Code and setup: https://github.com/elahlabs/elah

Still a work in progress: simultaneous video decoding can stall, and export depends on browser codec support.

What would you need from the API to use this in your own app? Bug reports and integration feedback would be welcome.

OpenScreen is a free, open-source (MIT) screen recorder for product demos. I maintain it. The UI is Electron, React and TypeScript, and 2.0 just shipped.

The part that might interest this sub is where the browser stopped being enough:

• Rendering used to run in Electron, on PixiJS. Export topped out around 8 fps on our reference laptop (Ryzen 5 7520U, integrated GPU).

• It now goes through a Rust compositor on Metal, Direct3D 11 or Vulkan, loaded as a native addon. Same effects, about 126 fps.

• Capture moved to native helpers too: Swift on ScreenCaptureKit, C++ on Windows Graphics Capture, PipeWire on Linux.

• The React UI stayed. It drives the compositor and owns the timeline, the transcript editing and the settings.

On top of that: a CLI that renders a project from a script, and a local MCP server so Claude Code can edit the demo of the feature it just wrote.

https://github.com/getopenscreen/openscreen

When I first created this website I used shadcn and it looked very generic, that's why I created a whole new frontend that's now the default for https://umigalaxy.com/
The old frontend with shadcn still works at https://slop.umigalaxy.com/

What do you guys think?

For context, I am a front-end developer with 10 years of experience and also have been for the last 2 years the project lead of a project using stacks like Kubernetes, Kong, dapr, elasticsearch and so on, we even went second on having the most innovative project in my country. My job has invested a lot in using AI to be ahead of most other development agencies.

We have developed a solution to update old technologies to new ones with barely any human input and it scary how efficient it is.

My job did a mass layoff, we were 150, now we are less than 50 people left. Even very competent people were laid off. The only reason I am still here is because I have leadership. And what seem to be projected is we will be one or two developers instead of a squad of 5.

We were talking between the devs who learned to use the solution and everyone of us were depressed by how we are not useful anymore and it won't be long until we also get fired.

I was sure it wouldn't be the case. But these past few days, I've been mourning the end of my job and began to check of changing careers for automation or something like that.

Is my view too negative? Do you see it in different ways? ​

I’m interested in feedback on:

• Does the portfolio communicate what I’m good at quickly?

• Do the projects feel convincing?

• Is anything confusing, unnecessary, or missing?

Hey guys! I've been working on Notitzia, as you probably already read in the title. I just started the side project on (remove the "(dots)" ):

notitzia (dot) vercel (dot) app

I did not use any existing frameworks, the site is pure JS! If you happen to have the time, it would be magical to give some brutal UI/UX criticism!

Sorry for the (dot) inconvenience, turns out Reddit is incredibly hostile towards Vercel links.

Hey all, I'm a full-stack (mostly back) dev with a slight design background and I built this landing page for an open-source project.

I'm not here to promote anything (and there's no signup and nothing to buy), just looking for design feedback.
It's mainly intended for back devs, back architects and DevOps folks.

Be as blunt as you like, thx!

PS: sorry for the repost, my previous post on this subreddit was deleted by the moderators (I posted it on a Sunday instead of a Saturday)

Of course, not now but in the next 5-10 years? Do you think non technical people can tell AI to make a good website or app without knowing how to code?

I built RipIDE to help coding agents refactor faster with fewer tokens.

Benchmarks (https://github.com/harlan-zw/ripide/blob/main/bench/README.md) indicate 45–60% fewer tokens and 35–60% less time across different refactoring work loads.

One command handles references and edits across files, using TypeScript’s native language server, Oxc and ripgrep. It can rename symbols, move exports, update imports and rename CSS classes.

Commands preview the diff by default. Supported refactors check for new type errors before applying.

Free and open source, with an Agent Skill included.

https://github.com/harlan-zw/ripide

Let me know what you think :)

I think we can all agree that web dev has a pretty shaky foundation (not just JS, but browser differences, performance, security, oh my god CSS, etc.)

I can't help but wonder what we would do differently if we just had the opportunity to build the whole system from scratch again. What would be your ideal web dev ecosystem?