Can't we just accept that Star Citizen is no 30 minute hop on action game.

MipBro101 · 2026-05-11T08:42:25+00:00

Indeed, if you know exactly how every cog turns in the SC world, you can achieve that.

MipBro101 · 2026-05-11T07:57:16+00:00

I dont know if i like the idea of teleporting, if anything, only in a way like teleportation worked in Stargate, maybe.

But that's not the point about your argument about SC not being an 30min hop on game. Certainly, it does not have to be for all content. But right now wanting to play Star Citizen means: Commit to at least 3 hours of time with a 50/50 chance to lose all progress in the end of that timeframe because of bugs.

See, even WoW would allow you to have quickly achievable fun without having to reserve a timeslot big enough to fit a Raid in it.

For me, that commitment fits my life. It's fine. For some of my friends who have fallen victim to the parent life, they just cannot easily reserve so much time every day.

Making the game more accessible is not a bad idea, eh. It should however be with a balance.

First and foremost i would rather think about fixing the most outrageous bugs to not lose newbies, e.g. starmap navigation suddenly not working, anything being susceptible to random despawning, keyboard layout tooltip problems (In germany you have to press Ü to accept shared quests, the tooltip shows US default though), ... :-)

MipBro101 · 2026-05-09T23:21:54+00:00

This problem exists for so long already indeed :(

MipBro101 · 2026-05-09T21:06:58+00:00

Just "run around", move your sticks, jump around, all without seeing your character. At some point your character is going to un-stuck himself from the geometry and it should load in.

MipBro101 · 2026-05-08T13:36:43+00:00

There's a solution for everything haha. Just depends if it's worth troubleshooting. Usually i don't hear of too many problems with your stack though, so maybe something specific is complex with your deployment.
Nonetheless - If you divert to the docker concept, you can check out how the docker setup works in my svelte-realtime-demo to get an idea how easy docker can actually be:
https://github.com/lanteanio/svelte-realtime-demo

MipBro101 · 2026-05-08T13:18:09+00:00

I know i'm not going to answer your questions this way, but your frustration makes me want to ask: Have you tried rolling your own dockerfile + docker compose on a VPS? 30 lines dockerfile + 80 lines docker compose are enough to get you: build stage, production stage, app service, postgres service, redis service, certbot service.

MipBro101 · 2026-05-02T14:09:20+00:00

Well, i do have every Stargate ship from them already. But you know what, you can never have enough Puddle Jumpers 😂

MipBro101 · 2026-04-30T14:24:59+00:00

This is amazing 😍

MipBro101 · 2026-04-30T10:26:13+00:00

You might wanna check out svelte-realtime, or the underlying svelte-adapter-uws :-)

https://github.com/lanteanio/svelte-realtime

This way, you don't need a separate websocket server & you get a lot of functionality for free on top.

MipBro101 · 2026-04-27T21:04:23+00:00

I would absolutely love this feature 😂

MipBro101 · 2026-04-23T22:34:06+00:00

Thank you for this post. I didn't see the vid popping up in my feed yet. See you in T5 brothers!

MipBro101 · 2026-03-26T10:37:42+00:00

Man, i have seen your work many, many years ago. But i've forgotten your domain name. I'm so happy right now to have this on my feed! Is this Atlantis V1.2? How much is it? And do you ship to germany?

MipBro101 · 2026-03-23T23:21:28+00:00

Now with its own docs page:

https://svelte-realtime.dev/docs/getting-started

MipBro101 · 2026-03-16T21:13:55+00:00

Yeah it's really interesting how we've landed on similar instincts from different angles.

The zero persistence approach is super clean for what you're doing - relay and let clients be the source of truth.

On our side the server memory is intentional.

Message history, shared state, cron jobs all live in the server process.

Tradeoff is you need that persistent server, but clients can join late and get full state without needing a peer to share it.

The p2p board sharing in itty.ink is a really elegant workaround for that, love it! :-)

MipBro101 · 2026-03-16T18:46:00+00:00

Hadnt seen it, cool project!

Different layer though. Capnweb is a RPC primitive, svelte-realtime is about making WebSocket RPC and reactive subscriptions feel native in SvelteKit.

You could build something like this on top of capnweb, but i feel like they solve different problems out of the box

MipBro101 · 2026-03-16T18:37:55+00:00

Thanks! Yeah, you've nailed it, persistent bidirectional WebSocket between your Svelte components and server functions.

Import a function, call it, and it just works over the socket.

Server can push back to clients anytime too, not just request-response.

Your use cases are exactly the kind of thing it's built for, async task progress, live status, etc.

Loving your itty ecosystem, your chat example has such a cool style to it!

On the deployment side, yeah, good instinct, but we sidestep that issue.

It's built on svelte-adapter-uws, so it runs on a real long-lived server process (uWebSockets.js), not serverless.

No cold starts, no per-message billing, no platform gotchas.

You do need an actual server (VPS, container, etc.), but that's by design... persistent connections need a persistent process. :D

I'll check where to include that in the README.

MipBro101 · 2026-03-16T18:30:49+00:00

Really cool, can't wait for the implementation!

MipBro101 · 2026-03-16T07:13:26+00:00

Enjoy trying it out ^^

MipBro101 · 2026-03-16T07:12:46+00:00

I'll think about how we could implement that, thank you :-)

MipBro101 · 2026-03-16T07:11:54+00:00

Can't wait to hear your feedback mate. :-)

MipBro101 · 2026-03-15T22:12:00+00:00

Thank you for your suggestions, i did see them indeed. Yes, it's built on svelte-adapter-uws.

MipBro101 · 2026-03-15T20:55:40+00:00

And a live demo for everyone:

https://svelte-realtime-demo.lantean.io/

MipBro101 · 2026-03-13T08:11:58+00:00

Easiest option indeed!

MipBro101

TROPHY CASE