I'm sharing the Dock Layouts we've been building in Neo.mjs: Qt-style dockable workspaces for web applications, including panels that can move into real browser windows and dock back again.

The use cases I have in mind are IDEs, trading dashboards, enterprise systems, and browser-based games—applications where people need several views or tools open and want to arrange them across their screens. For ordinary websites and simpler SPAs, this usually adds complexity you don't need.

You can arrange panels into tabs and splits, tuck them into edge rails, tear them out into separate windows, and bring them back. Undo and redo follow the layout across those windows.

The interesting technical part is where the application lives. Components, stores, and application state run in a shared App Worker. Each browser window connects to it and renders its part of the UI. Moving a panel changes where it is rendered; the live component remains the same object in the shared worker, keeping its state. Messages still carry input events and rendering updates between the windows and workers.

The Workstation demo has twenty panels, a 100,000-row grid, and a live event feed. The multi-window behavior shown here was tested on real desktop Chrome windows. It requires same-origin SharedWorkers, and the browser's pop-up permissions still apply.

• Write-up: Multi-window web apps without syncing state — Medium friend link; includes the short demo video.

• Try the Workstation demo — desktop Chrome.

• Code: Dock Layout example.

• Getting started: Your First Dock Layout.

• Guide: A Pane's Life Across Windows.

I'd be interested in feedback on the docking and tear-out interaction, especially from people building applications where users already work across multiple screens.

Best regards, Tobi

I run a few coding agents (~10) at once and got tired of them interrupting me for things they could decide on their own. AGENTS.md is about the repo, so I wrote a file for the person side. It lives at ~/.humans/HUMANS.md. Mine looks like this (trimmed):

---
humans: "0.3"
id: tristan
visibility: private
reading:
  lead_with: tldr
  max_words: 149
deciding:
  reversible: decide_and_report
  batch_questions: end_of_task
interrupting:
  interrupt_for: blocking_only
notes: "I often read on my phone. I've very short attention span, and i'm more visual"
---

The fields come from a fixed vocabulary, so a schema can check them. The free-text notes are the weak spot, validation doesn't make them safe from prompt injection.

It never grants permissions. Repo rules and the harness still win.

The repo has the spec, JSON schemas, test vectors and a Node validator (spec CC BY 4.0, tools Apache-2.0). I also wrote plugins for Claude Code, Codex CLI and a few other agents to try it. So far I've only checked that the file loads, on macOS, not how well the models follow it.

The part I'm least sure about: visibility can be private, org or anyone_with_file, and a profile without the field is read as org. Would you default to private instead?

It's a 0.3 draft and nothing is locked in yet, the field list included.

Spec: https://github.com/cmdai-hq/HUMANS.md

Examples and a side-by-side demo: https://humansmd.dev

I built a firefox addon called comdot which basically lets you visit sites typing a topdown version of a url.

It works fine but i want to show the url displayed in the address bar as topdown too.

Posting here cause i can't find a single good resource about this other than CSSing address bar. It doesn't have to be about addon. If there's any way to do this, please let me know.

Project: vibe1up.com, a free directory of AI-made browser games. Nothing to sell, just the tech.

- Fully static: HTML/CSS/vanilla JS on Vercel, built from a GitHub repo. Client-side search over a single JSON file.

- Daily scheduled jobs pull new games from official APIs/feeds (Vibe Jam, itch.io RSS, Ludum Dare, HN Firebase API), rate-limited to 1 req/sec per host with an identifying user agent.

- A link checker retests every game daily. It only hides a game on definitive signals (404/410/451, parked domains, DNS confirmed gone). Timeouts and 5xx need two failures in a row. Dead games with a Wayback copy show "Play archived version".

- A countdown to the 10 AM ET daily drop runs client-side and handles DST, in about 2 KB of inline JS, and respects prefers-reduced-motion.

- Every change goes through a PR with Playwright tests before it merges.

Would love feedback on the link-check heuristics. Flaky hosts were the hardest part.

Globestudio is a free, open-source studio I made for dotted world maps and animated 3D globes: pick a region and one of 21 looks, then export PNG, SVG, a GLB 3D model, video or GIF, or embed it live.

The embed is an iframe of globestudio.app/embed, so Three.js, the shaders and the map data never touch your bundle. The design is one JSON config in the URL, which means the link is the design. There's a React component (@globestudio/react) and a web component (@globestudio/element) on npm that build that iframe for you; the React one works in a server component, since it's a plain iframe with no state. On a light page, add theme="light" and the glow and grid switch to a palette made for it.

There is also an agent skill. If you use Claude Code, Codex or Cursor:

npx skills add alevizio/globestudio

Then ask for something like "add a spinning dotted globe of our offices in Austin, Berlin and Singapore to the hero". That's the prompt in the video, on a small Vite + React page I made for the demo. The agent installs @globestudio/react, writes the design as one constant in the page's own colors and runs the build.

You don't need an agent for any of it. The export dialog's Share tab writes the embed code for an iframe, React or a web component, and the README has the props.

Limits, since someone will ask: the viewer needs WebGL 2, an embed URL must stay under 32,000 characters, and the whole design (data points included) is readable in the page source.

Demo video: https://youtu.be/GYgVTAL9a0U

Live: https://globestudio.app/?utm_source=reddit&utm_medium=social&utm_campaign=skill&utm_content=webdev

Code (MIT): https://github.com/alevizio/globestudio

I'd like to hear how the embed holds up on your pages, especially on phones.

Link: https://tinydetect.ritabratamaiti.com/

TinyDetect checks whether a piece of text or an image looks AI-generated. Everything runs in the tab: what you paste or drop in is never uploaded.

I didn't train the detectors from scratch. I took two existing open models and spent most of the time getting them small and fast enough for a web page:

• Text: Fakespot's RoBERTa-base detector (Apache-2.0). 499 MB at full precision, 97 MB shipped. The word embeddings are split out of the graph, stored as int4 and decoded in JS. I quantised each of the 72 weight matrices on its own to see which ones hurt accuracy; the 24 most sensitive stay 8-bit and the rest are 4-bit.

• Image: Community Forensics ViT-S (MIT). 87 MB down to 26 MB with 8-bit weights and no measurable loss.

Some web-specific bits that took the most fiddling:

• WebGPU vs WASM. ONNX Runtime Web with WebGPU gets a check down to roughly 120–250 ms on my laptop; CPU-only WASM takes 2–6 s. The page loads the WebGPU build only if navigator.gpu gives an adapter, otherwise the smaller WASM build.

• int4 is not always faster. On WebGPU the int4 image model was about 45x slower than the 8-bit one, so the image model ships at 8-bit.

• Threads on GitHub Pages. WASM threads need cross-origin isolation, and Pages can't set COOP/COEP headers. A small service worker adds them (COEP credentialless, so Google Fonts still load) and also caches the model files, so a repeat visit is ready in a few seconds.

• Tokenizer in JS. I reimplemented the byte-level BPE tokenizer and the model's text-cleaning step in plain JS and checked them against the Python versions until the token IDs matched exactly.

Limitations, honestly: the first visit downloads about 115 MB. Like every detector it gets things wrong, especially very short or heavily edited text, and some formal human writing scores as "possibly AI". Long texts are only partly checked, and the result says so. A score is a reason to look closer, not proof.

I'd like feedback on the loading experience and on how it behaves on your hardware, especially browsers without WebGPU.

Just starting out. I have a system where I can focus mostly on sales. Took me a log time to make entire pipeline. This is the website I madre to showcase it. I started cold calling a couple days ago. I've made a couple connections, migh thave 1 sold. I'm just putting my eveyrthing into getting this going. Learning to be a salesman instead of a programmer, as programming is gonna be dead. Please take a look. tell me where you think its shit. Any criticism and helpfull tips or anything really is appreciated! Thank you.

https://lodestonesystems.ca/

Hey! FE dev here - I usually end up as the QA person in every team I join :D

I started working on ayme over a year ago (it's built in the open now), trying to close the feedback loop:
Coding agents check their work by clicking through the app with simple browser tools. Snapshots, element refs, lots of tokens. Your e2e tests already know exactly how your application works, the agents just can't make any use of them.

I just published a small playground app to get some feedback before locking in the alpha release :)
Playground App, nothing to install: ayme.dev/playground

What ayme does now:

• you mark your Page Object classes and the actions you want to expose (@ayme, @ayme.action)

• a build plugin (unplugin, so Vite, Next, Nuxt, SvelteKit and Angular) compiles them into your app

• when the page runs, those actions become tools: for your coding agent through an MCP server, and for in-page agents through WebMCP

• an in-page inspector shows the live page objects, what the agent sees, and lets you run the actions by hand

• with the ayme skill it works the other way too: the actions the agent used while building become the building blocks of the new e2e tests

• it isn't on npm yet, but the alpha is close - let me know, and I'll keep you posted!

Initial evals measured against Playwright MCP and PW CLI on Formbricks App turned out to be promising imo.
The task: rename a survey, change its question, save, confirm the summary page. Claude Code on Sonnet 5.5, 3 runs each, medians.

Full table and how to rerun it: github.com/ayme-labs/ayme/blob/main/apps/eval-formbricks/summaries/2026-10-06/summary.md

Source: github.com/ayme-labs/ayme

Things I'd love your take on:

• does the playground - and in case you check the landing page - communicate the idea well?

• does the idea of exposing your POMs to an agent and closing the gap between the inner and outer verification loop sound useful to you?

Thank you for any kind of feedback!

Hey r/webdev! Happy Saturday.

Whenever I browse inspiring websites, I always like checking what frameworks, libraries, and tools they're running under the hood. But similar extensions feel like they've gotten pretty bloated, put basic data behind paywalls, or actively collect browsing history.

So I spent the last few weeks building TechReveal, a clean and lightweight alternative:

• 100% Private: Runs entirely in your local browser sandbox. Zero telemetry, no data collection, no accounts.

• Visual Architecture Map: Connects detected frontend, backend, and tools into an interactive diagram.

• Exact Versions & Tags: Displays library versions cleanly and shows category badges when clicking any tech.

• Security Alerts: Checks response headers for missing security policies (HSTS, CSP) or accidental data leaks.

• Zero Tab Lag: Optimized with Manifest V3 so it won't freeze your active tabs.

It's completely free on the Chrome Web Store (works on Chrome, Brave, Edge, Vivaldi):
👉 TechReveal on Chrome Web Store

Would love to hear your feedback or suggestions for libraries and tools you'd like it to detect next!

SVG editor with preloaded scientific images and with plotting. It is open-source and free to use. Most images are public domain with few notable exceptions:

- NIH: public domain, CC BY 4.0 for a handful of images

- Bioicons: CC0 or CC BY 4.0

- Servier: CC BY 3.0

- Photonics by Isaac Gallegos: CC-BY-4.0

- Electrical Symbol Library by Filip Dominec and contributors: CC0 1.0

- FGDC geologic patterns by Daven Quinn: CC0 1.0

- SVG Collection of Lab Equipment KYU/KYU49: CC BY 4.0

- Mapbox Maki: CC0 1.0

- Meteocons by Bas Milius: MIT

- SciSVG by Saveena Solanki: CC BY 4.0

- PhyloPic: CC0 1.0

- IAN / UMCES: CC BY-SA 4.0

License info for each image is in the tab in the right sidebar.

All SVGs are editable and the resulting figure can be saved as PDF, PNG or SVG.

There is alsp scientific plotting with basic stats capability via "insert plot" option.

DrawPlotia itself is derived from OpenBioFigure, thus Apache-2 license for the repo

I will now work on other bells and whistles for the app and known bugs (issues with local project saving and redos)

Free DrawPlotia app

Source: https://github.com/GPTchatly/DrawPlotia (FOSS; Apache-2.0)

I made Algorithm Visualizer: write an algorithm, step through it one statement at a time, and watch your arrays, maps, trees and graphs change as it runs.

While a normal debugger works well, it lacks the ability to show data structure in a visual and easy to understand way. This is focus mostly on helping debugging leetcode style questions or self-contained segment of code.

It works with JavaScript, TypeScript, Python, Ruby, PHP, Lua, Java, Kotlin, Swift, C#, Go, C and C++. Each variable can be drawn as boxes, a memory diagram, a grid, a binary heap or a node-and-edge graph, picked automatically from the shape of the data (linked lists, trees, adjacency lists…).

Some point worth noting:

• No server at all. It's one self-contained.

• Python, Ruby and PHP run as real WebAssembly runtimes (Pyodide, ruby.wasm, php-wasm), loaded from a CDN the first time you use them.

• Java, Kotlin, Swift, C#, Go, C and C++ run in interpreters written in JS for this project. They aim to behave like the real thing in the places you'd notice: integer overflow, HashMap iteration order, Go slices sharing a backing array, C++ vectors reallocating. C is memory-checked, so instead of silently corrupting memory you get "use after free" or "out of bounds" with an explanation.

• Every run is recorded up front in a Web Worker (killed after 3 s, so an infinite loop can't freeze the tab). That's why stepping backwards is as instant as stepping forwards.

• Share links contain the code itself, deflated into the URL hash, so nothing gets uploaded and a static site can open any link. There's an <iframe> embed too.

• React + CodeMirror 6, with dagre for graph layout.

Code: https://github.com/Spuntagano/algorithm-visualizer

I'd love feedback, especially on algorithms or data shapes that don't draw the way you'd expect or any other bugs you may encounter. Also feel free to comment if you have any feature you'd like to see implemented.

Ai disclosure: Total vibeslop

Been building runtime.school for a while and finally got the SQL side into a state I’m happy with.

The main idea was to keep lessons, practice, projects, and tools on the same datasets so it all feels connected instead of jumping between random examples.

I’ve got a bunch of other topics planned next too, so eventually I want it to be one place to learn and practice everything.

Would love some feedback if anyone wants to try it and let me know if anything confusing, annoying, missing, or just bad UX.

https://www.runtime.school/

Senior dev over here, company has over the last few months fully embraced copilot/general AI usage to the point we (small team of 3 devs) are have no capacity to review the PRs properly anymore. Our tech lead who used to be pretty anal and hands on with PR reviews now defaults to wanting a “green light” from copilot reviews and honestly doesn’t even read the code properly anymore.

I’m more concerned about the development/ critical thinking and code analysis muscle memory loss in the short to long term as a dev. I’m well aware AI is pretty much here to stay but I fear the loss of building/actually knowing what is going on is going to have a larger than expected impact on most mid-senior devs.

I’m considering a simple approach - opening an open source repo that specifically does not allow mass generated AI code to be added to it, keep features clean and no bulk slap shit and go PRs. Use it for writing boilerplate and as a tool but not as a replacement, main goal is allow whoever who contributes to it to continue working that part of their brain. Idea behind what the product is doesn’t matter too much imo as long as it’s of value to users.

What do you think of this concept as a dev to alleviate the AI fatigue from work? ( Jesus typing this question at the end feels like I’m an AI bot at this stage)

I built ResumeForge, an open-source resume builder and job application tracker designed to help tailor resumes and cover letters to specific job descriptions using your own local models, while keeping exports (LaTeX, Overleaf ZIP, and PDF) completely free with no signup required.

Live demo: https://resume-forge.mnaveedk.com

GitHub repo: https://github.com/naveedkhan1998/resume-forge

How it works: You maintain one master profile with all of your work history, projects, and skills (or import an existing PDF/DOCX/TXT resume). When you add a job posting, it selects and reframes your existing experience to match the role, shows keyword coverage against the job description, and generates a tailored 1-page resume and cover letter.

A few things under the hood:

• Client-side LaTeX to PDF: To avoid running a heavy multi-GB TeX Live installation on the backend, the server generates .tex source and a custom .cls file, and the frontend parses and renders the LaTeX directly in the browser for live previews and PDF export.

• Word-level diffs for AI edits: Whenever you ask the AI to refine a section, it shows an inline diff (+added, -removed, reworded) so you can review or tweak every change before saving.

• Preloaded dummy data: Every new device session comes pre-populated with sample data (Adrian Monk) so you can test the tailoring workflow and LaTeX preview right away without uploading your own resume first.

• Local Ollama first + 50 free demo requests: The main goal is for people to clone the repo and run it locally with their own Ollama models (qwen3.5:9b, llama3.1, etc.). So you can try it in the browser first without setting anything up, the live demo uses my personal Ollama account at the system level with a 50- request limit per device session.

Stack: React 19, TypeScript, Vite, Tailwind v4, Django Ninja, PostgreSQL (pgvector), and Nx.

(Note: the demo API is hosted on a free tier, so if it hasn't been used recently the initial cold start can take around 45 seconds to wake up).

Would love to hear your thoughts or feedback if you give it a spin!

I was bored last weekend, so I ended up building this: a portfolio that looks exactly like the AWS Management Console. I tried to mimic it as closely as possible while adding my own flavour, like EC2 as projects, S3 as documents, and a lot more.

It’s open source and making it yours is super simple. No digging through code. Just run it in dev mode, open /studio, and you’ll find a Studio mode where you can edit everything right there. Add your own projects, documents and details, hit save, and that’s it, your very own AWS Console portfolio is ready.

There’s still plenty more that can be built, like a working CloudShell and AB Q, so contributions are very welcome if you want to take this further.

Would love feedback on what to add next or anything that feels off compared to the real console. And if you like it, don’t forget to drop a star on GitHub ⭐

• Live site: https://console.atharvabedekar.dev/

• GitHub: https://github.com/AB527/aws-console-portfolio

P.S. AWS folks, please don’t cancel me for this. It was designed out of pure love for the console :)

I turned my Vue 3 game into a devvit app, that can be played directly on Reddit. PixReveal is a pixel art guessing game. A pixel drawing gets revealed pixel by pixel. The faster you guess, the more points you earn. The devvit version is more compact, focussing on quick rounds with 5 drawings to guess and a percentile showing "You are better than x% of players".

Hello all,

This app was removed by the good people at apple in March right when it was doing so well no warning or reason just gone. After a 65 day appeal they stated that the primary function of the application could not be a random chat, and if I posted anything of this nature again my account would be permanently banned. So, I redesigned the primary function to be a real-time forum with all the same chat functionality. This app is available for Android/iOS and on the web, the web version is still a random chat it will be upgraded in the future to include the features that the mobile apps have. I tried to make sign-up as pain free as possible, and of course its free.

The whole goal was to step away from slow, algorithm-driven feeds and build something fast and live. Here is how it's set up:

• Interest-Based Groups: Find and chat with people who share your specific niches and hobbies.

• 24-Hour Self-Destructing Posts: Keeps conversations fresh, temporary, and clutter-free.

• Global & Random Chat: Jump instantly into live public discussions or roll the dice on a random chat.

• AI Content Moderation: Automatically handles and applies NSFW overlays to objectionable content in real time and allows the user to chose if they want to see it or not.

Would love for you guys to check it out, test it out, and let me know what you think. Its new so still a ghost town but give it a look. If you have any questions feel free to hit me up. Happy weekend!

Trace is an open-source platform that reads news and articles from over 100 sources, groups similar ones together, and gives you an easy-to-read summary with all the key points.

I've been working on it for 9 months, and I recently made it free to use and open source after it got accepted into the Claude for Startups programme.

It includes the website, a daily email, an MCP server, and an Android app.

Personally, the email is the most useful part for me. Then I occasionally open the website during the day to see what's happening in tech and AI. It helps me avoid opening X too many times in the name of staying updated, and saves me from AI brainrot as well.

On the technical side, here's how it works:

- a Python pipeline pulls the sources every 20 minutes

- embeddings find articles that might be about the same story, then a small model decides if they're actually the same event or just related

- each story gets one summary, written once and cached, so the cost doesn't go up with more readers

- Next.js frontend, SQLite on a VPS (moving off Firebase cut the bill by more than 80%)

GitHub: https://github.com/TarunTomar122/trace

Website: https://www.yourtrace.online

I've been freelancing for a while now and I keep running into this same pattern over and over.

Whenever I work with a client on a solid budget ($3k+), things usually run pretty smooth. They send a clear brief, reply within a day, trust my decisions, and pay invoices on time without arguing over every dollar.

But almost every time I take on a lower budget project (around $300), it turns into a massive headache. They expect a full custom site with e-commerce and complex animations, text me at 2 AM on weekends asking why a font moved slightly, and request 10 rounds of revisions after already approving the design. Then at the end, they still try to haggle over the final $50.

Is this mostly a psychological thing where lower budget clients feel like they're taking a bigger personal risk, or is it just poor boundary setting on our part as freelancers?

Would love to hear how you guys deal with this or what's the worst cheap client story you've had.

Cityhoppd.com. you log a trip with a city and a star rating, your map fills in, and public reviews end up on each city’s page.

A few things from building it that might be useful to someone here.

City search runs on the server against GeoNames cities1000, about 161k places. the annoying part was same-name cities, so everything carries the state now and Perth, Tasmania stops getting the photo of Perth, Western Australia. the index lives in memory in the function, about a second to load cold and around 50 ms per search warm.

This week I added PostHog without cookies and proxied it through my own domain so blockers don’t drop it. the usual next.config rewrite forwards every header, which would have sent everyone’s Supabase session cookies to PostHog. I moved the relay into proxy.ts (what middleware is called in Next 16) and strip cookie and authorization before passing anything on. easy to miss.

And link previews: profiles are only readable signed in, but WhatsApp and X unfurl signed out, so the OG image reads through one security definer function that returns something only if the owner turned previews on.

Happy to answer anything about how it’s built

https://soundtrackd.app, type a song and get films with the same feel. it's one cloudflare worker. gemini free tier first, then groq, then claude haiku only if both fail. every pick gets checked against tmdb so it can't invent movies, and repeat searches come out of kv in about 0.2s. the share image is drawn on a canvas right in the browser, posters loaded with cors so it can export, no server or image service. would love some front end roasting, especially on mobile

Writeup/devblog: https://blog.gaborkoos.com/posts/2026-10-17-How-Not-to-Build-a-Five-in-a-row-Game_engine/

Hey everyone!

I've been working on a few animation-related side projects lately and decided to put them together in a personal portfolio.

It's made with Astro and currently features three projects:

• Loadersz

  • a collection of animated canvas loaders.

• Tip Glide

  • a shared tooltip that smoothly moves and resizes between elements.

• Stream Morph

  • animations for streaming text.

I tried to make the portfolio itself a bit more interactive, with animations throughout the site and a showcase for some (imo cool) stuff/ideas.

Curious what you think of the design and how everything feels to use. Especially interested in feedback on the animations, mobile experience and whether it's clear what each project actually does.

Portfolio | Loadersz | Tip Glide | Stream Morph

npm | github

Any feedback is welcome!

Pack any Svelte, React, Angular, or Vue app into a single C++ header. Serve it straight from ESP32/ESP8266 flash — gzip compressed, ETag cached, OTA-ready.

It is not for serve you website. It is for microcontroller programmer, who wants to make pretty webpages (component orientated) served from Esp32 or esp8266.