Show HN: Stream iOS Simulators to a Browser Window
2 by EvanBacon | 0 comments on Hacker News.
Agent tools seemingly know how to work with browsers better than with iPhone simulators, so I built this tool to capture the simulator XPC stream and render it in a webpage. This means Claude Code/Codex desktop apps can use their existing browser-use tools to launch the preview, screenshot, and read logs without getting caught in a osascript loop.
Hack Nux
Watch the number of websites being hacked today, one by one on a page, increasing in real time.
New ask Hacker News story: Ask HN: Hosted Fossil for small teams – interesting, or wrong call?
Ask HN: Hosted Fossil for small teams – interesting, or wrong call?
7 by ragelink | 1 comments on Hacker News.
I've been working on a hosted Fossil SCM service for a few months and I genuinely don't know if it's a good idea. The "We need a federation of forges" thread on the front page today made me think it's worth posting. What I'm building: a hosted home for Fossil repos. Same onramp feel as a code host, but each project is a single self-contained SQLite file you can clone, email, or walk away with. The open source omnibus (Django + Postgres + Redis + Caddy + Litestream-to-S3) is at fossilrepo.io. The hosted version will be in private beta soon. My rough thesis: 1. Fossil is already federated by design. Every clone is the entire project: issues, wiki, forum, history, code. That's the federation discussion happening on the front page right now, just with a 15+ year-old tool the SQLite project itself uses. If fossil clone works between any two hosts, lock-in basically dies. 2. AI agents need integrated context. A Fossil repo is one queryable SQLite file. An agent reads code + tickets + wiki + history with SELECT * instead of 47-odd GraphQL calls. RAG and MCP setups become trivial. Also has a cli tool thats super easy to use. 3. Small-but-serious teams are underserved. Git+GitHub won the macro market and that's not changing. But the 1-50 person team where the spec, the tickets, the wiki, and the code all belong in the same place... the integrated model is just better/easier. Things I'm worried about: - Network effect — a repo isn't very useful if nobody else can find it - Inertia — Git muscle memory is hard to break - Codeberg / Forgejo / Gitea are all credible — what's the right wedge, if any? is this a solution that anyone wants? I'd rather hear it from HN now than after we launch. Three honest questions: - Is this interesting, or am I solving a problem nobody has? - What would make you actually switch? - What am I missing? Also stuck on the name. Both domains land on the same page, so vote whichever you'd actually use: https://fossilforge.io or https://fossilhub.io (I also have the .ai versions but .io feels more developer-y)
7 by ragelink | 1 comments on Hacker News.
I've been working on a hosted Fossil SCM service for a few months and I genuinely don't know if it's a good idea. The "We need a federation of forges" thread on the front page today made me think it's worth posting. What I'm building: a hosted home for Fossil repos. Same onramp feel as a code host, but each project is a single self-contained SQLite file you can clone, email, or walk away with. The open source omnibus (Django + Postgres + Redis + Caddy + Litestream-to-S3) is at fossilrepo.io. The hosted version will be in private beta soon. My rough thesis: 1. Fossil is already federated by design. Every clone is the entire project: issues, wiki, forum, history, code. That's the federation discussion happening on the front page right now, just with a 15+ year-old tool the SQLite project itself uses. If fossil clone works between any two hosts, lock-in basically dies. 2. AI agents need integrated context. A Fossil repo is one queryable SQLite file. An agent reads code + tickets + wiki + history with SELECT * instead of 47-odd GraphQL calls. RAG and MCP setups become trivial. Also has a cli tool thats super easy to use. 3. Small-but-serious teams are underserved. Git+GitHub won the macro market and that's not changing. But the 1-50 person team where the spec, the tickets, the wiki, and the code all belong in the same place... the integrated model is just better/easier. Things I'm worried about: - Network effect — a repo isn't very useful if nobody else can find it - Inertia — Git muscle memory is hard to break - Codeberg / Forgejo / Gitea are all credible — what's the right wedge, if any? is this a solution that anyone wants? I'd rather hear it from HN now than after we launch. Three honest questions: - Is this interesting, or am I solving a problem nobody has? - What would make you actually switch? - What am I missing? Also stuck on the name. Both domains land on the same page, so vote whichever you'd actually use: https://fossilforge.io or https://fossilhub.io (I also have the .ai versions but .io feels more developer-y)
New ask Hacker News story: Ask HN: Why does tech industry not have more co-ops?
Ask HN: Why does tech industry not have more co-ops?
2 by conqrr | 3 comments on Hacker News.
Sounds like this should be the default path if AI is really enabling everyone and setting an even field. Why is it just winner (CEO and co) takes all and losers go home?
2 by conqrr | 3 comments on Hacker News.
Sounds like this should be the default path if AI is really enabling everyone and setting an even field. Why is it just winner (CEO and co) takes all and losers go home?
New Show Hacker News story: Show HN: A TUI for Markdown view an editing
Show HN: A TUI for Markdown view an editing
3 by cloked | 0 comments on Hacker News.
Hi HN, I built a simple TUI for viewing and editing .md files in the terminal. More and more markdown files keep appearing in our projects, and I found myself needing a quick way to view(with syntax highlighting) and edit them without leaving the terminal, so I built this
3 by cloked | 0 comments on Hacker News.
Hi HN, I built a simple TUI for viewing and editing .md files in the terminal. More and more markdown files keep appearing in our projects, and I found myself needing a quick way to view(with syntax highlighting) and edit them without leaving the terminal, so I built this