返回首页
最新
I built a “serverless” online chess app and published it on my personal website. It runs mostly client-side and connects players directly over WebRTC (P2P). No accounts, no matchmaking, no backend game server.<p>The entire UI + chess rules/validation run in the browser (static HTML/CSS/JS). For multiplayer, the host generates a 6-digit room code and shares it. The guest pastes it in and connects. WebRTC signaling is done through a small set of endpoints (create room, store offer/answer, delete room). After signaling, the connection is direct peer-to-peer via SimplePeer.<p>There's a known limitation where connection doesn't with both players connected to the same network.<p>Demo: <a href="https://www.adriclumma.com/projects/chessOnline/" rel="nofollow">https://www.adriclumma.com/projects/chessOnline/</a><p>Code: <a href="https://github.com/ALumma/chessOnline" rel="nofollow">https://github.com/ALumma/chessOnline</a><p>Let me know what you think!
This idea has been floating in my head for about 10 years. Some of you might remember LowEndSpirit.com back before it became a forum, I started that. I've been obsessed with making tiny, cheap VPS actually useful ever since.<p>TierHive is my attempt to make 128MB VPS great again :)<p>It's a NAT VPS (KVM) platform with true hourly billing. Spin up a server, use it for 3 hours, delete it, pay for 3 hours. No monthly commitments, no minimums beyond a $5 top-up.<p>The tradeoff is NAT (no dedicated IPv4), but I've tried to make that less painful:<p>- Every account gets a /24 private subnet with full DHCP management.
- Every server gets auto ssh port forwarding and a few TCP/UDP ports
- Built-in HAProxy with Let's Encrypt SSL, load balancing, and auto-failover
- WireGuard mesh between locations (Canada, Germany, UK currently)
- PXE/iPXE boot support for custom installs
- Email relay with DKIM/SPF
- Recipe system for one-click deploys<p>Still in alpha. Small team, rough edges, but I've been running my own stuff on it for months.
Would love feedback — especially on whether the NAT tradeoff kills it for your use cases, or what's missing. (IPv6 is coming)
<a href="https://tierhive.com" rel="nofollow">https://tierhive.com</a>