u/leifrydenfalk

Tja! Jag håller på att bygga ett system som ska göra det enkelt och gratis för vem som helst att lägga upp annonser och sälja på plattformar som tradera (Tradera är ändå integrationen just nu) med en bild.
Du tar en bild.
Du får en tydlig annons som du kan ändra.
Sen så läggs det ut på tradera.
Det är helt gratis att använda!
https://rheo.se

github.com/ce-net

I've been building ce-net, a peer-to-peer compute mesh for your own devices — laptops, servers, Pis, phones — where you can deploy and run software across the whole fleet with one command. Posting here for the Rust-specific design feedback, since the whole thing is Rust end to end.

Stack and choices that might interest people here:

• libp2p for transport/discovery (mDNS on LAN, bootstrap peers + relay for hybrid public/private). NAT traversal so devices behind home routers join the same mesh as servers.
• Pluggable runtimes behind a Runtime trait — the node holds a Vec<Arc<dyn Runtime>> and dispatches a Workload by type. Four backends today: OCI images (gVisor/runsc, falling back to runc), native per-target binaries, WASM (fuel-metered, linear-memory-capped), and a build-from-source "recipe" tier. Apps are described by a small ceapp.toml manifest, so wrapping an existing Docker image or binary is ~15 lines.
• Content-addressed artifacts (blake3) so installs are reproducible across the mesh.
• Capability-based auth — attenuating, scoped, time-limited tokens instead of a central auth server, layered over libp2p identities/keypairs.
• ce-rs SDK (Rust) plus a TypeScript client, for building your own mesh apps, schedulers, and dashboards. There's a WASM target too (compiles to wasm32), so the same client runs in the browser.

Things I'd genuinely like opinions on:

• The runtime-tier abstraction — is Workload enum + dyn Runtime the right seam, or would you push more into the type system?
• WASM sandboxing for untrusted workloads (currently wasmtime-style fuel + memory caps) — anyone done capability-passing to WASM guests cleanly?
• libp2p ergonomics for a long-running supervised daemon — pain points you've hit at scale?
• Source (mostly AGPL, commercial option): GitHub org ce-net — ce, ce-rs, rdev are the best starting points. Site: ce-net.com

Disclosure: architecture and core implementation are mine; I used Claude as an assistant for tests, boilerplate, docs, and rubber-ducking hard parts. Happy to go deep on any of the internals — would love critique of the trait design and the capability model in particular.

github.com/ce-net
ce-net.com
cerena.ce-net.com

Im creating the worlds biggest fps game by letting every user hold a part of the server using ce-net - my systems for developing and deploying and connecting together any app over your devices and browser instances.
Deploy between YOUR devices with one ce app install —fleet=mine
Deploy globally in production by filtering nodes for the http-ingress capability and use ce-serve to lett your ce apps talk to http. Ce apps are any container and defines its capabilities and what it needs and where it wants to be and the mesh places it where it should.
libp2p - capability based and auth using ce-iam

ce-net is a authenticated trust (not trustless) system built for sharing and distributing the worlds idle compute to projects decided by the ce-net community using trana, the ce-native communications and social media platform by voting on decision proposals.

You build trust and karma by posting, voting and contributing. You use ce-net to use the internet for free - hosting and browsing, building and playing.

ce-net provides the substrate and example ecosystems and example apps to build on and use ce-net but everything is open, changing, evolving and growing together with our community and trust.

I’m 100% sure I fucked up tons of decisions, but the most important thing is just to launch and get it started and we can perfect it later.

Reason why.

The current state of ai has waaaay too much centralization and focused control. We developers do have the compute we need to compete but we don’t. Why? Because you would need to trust eachother and connect computers together in a big mesh and that’s annoying.

ce is a libp2p wrapper spawning wasm tasks and containers and exposes an api for the apps running on it - how it talks to eachother through it.
It has an auth system (ce-iam) which lets you grant permissions to other people’s devices or your own devices, set and manage keys and which apps running on ce-appmgr has access to them.
You connect devices to your identity. You build trust and karma on social media on ce-net, by hosting other people’s work and building genuine connections with people.
I stream every day on YouTube (right after I’ve built the streaming platform on top of ce-net lol, we’re about 2 hours away)

I’ve built
ce-drive - because fuck file systems which are on just one computer - install it with ce-appmgr in ce on a ce-node in ce-net - to have an instant sync shared drive with all your memory and harddrives combined.
ce-storage - s3 buckets over the sea (;))
spacegame (spa.ce-net.com) - a massively multiplayer game i built to prove scalability - built to handle an infinite number of concurrent players on one server - scales with amount of compute and every new user is a new server instance serving itself and surroundings.
ce-exo - exo over the sea - run llms on your ce-nodes (devices you’ve installed ce on)
trana - Swedish word for crane bird - it’s a social media platform just like the one I’m writing this on - Reddit clone. Will do its frontend tomorrow currently it’s just distributed backend.
And a lot more…

Where it’s heading:
Ce net policies decided by everyone on trana by voting on them.
Llms run on ce-net to validate policies for user content (check source code, binaries, documents, posts…)
Community driven super computer training llms, running hospitals and central infrastructure?
Since when can a secure free distributed dropbox be built and hosted for free for anyone to use in one hour? Since this week. A new age is coming.

So what would YOU build on ce?

I made ce-net - a wasm based supercomputer available to everyone - as long as you donate!
ce-net.com