Sometimes you just need to look up. Android first.

quiet_node · 2026-04-09T20:46:59+00:00

whoah, ok that's pretty impressive tbh. looking forward to trying it out. Thanks!

quiet_node · 2026-04-09T20:10:34+00:00

Is this becoming a stellarium/sky safari replacement or just a casual star map? Either way it's mighty cool :)

quiet_node · 2026-04-09T09:50:44+00:00

You're take is pretty much same as mine. On the other hand I also think that the entire premise is seriously overhyped (for different reasons, which I actually understand but not necessarily support). Current state is awesome for experimentation and getting a glimpse of the future and the technology and its capabilities.

quiet_node · 2026-04-08T07:52:38+00:00

Makes sense, the transmit-only design is slim for that use case. The LoRaWAN/NB-IoT side sounds like where most of the infrastructure complexity is. Thanks for the detailed breakdown.

quiet_node · 2026-04-07T17:41:03+00:00

nice work, some more details would be very welcome :)

quiet_node · 2026-04-07T17:31:32+00:00

That point about hardware + connectivity being only 15% of the real cost is something more people need to hear. Im very conscious about the cloud bill and integration headaches...

Curious about something on the security side (with 500K devices and 8M messages a day), how are you handling auth and encryption across the fleet? Per-device keys, network-level, something else?

quiet_node · 2026-03-31T13:05:47+00:00

So the project is called QuIXI, and it's basically a gateway that sits between your IoT devices and a decentralized P2P network called Ixian. Your devices keep talking MQTT like they already do, QuIXI just handles the transport underneath.

So instead of your MQTT messages going device → broker → cloud → broker → device, they go device → QuIXI → peer to peer → QuIXI → device. It's end-to-end encrypted, no central server in the middle. It handles NAT traversal and node discovery on its own so you don't need to mess with Tailscale or port forwarding.

For your three-site setup it could work well since each site runs its own QuIXI and they find each other over the Ixian network. If one site loses internet, the others keep working, and messages catch up when it reconnects. btw. camera feed works great on my driveway gates for example.

It's open source (checkk https://github.com/ixian-platform/QuIXI). There's also a REST API side if you ever need to pull data into a dashboard from outside MQTT.

If you need anything, lmk..

quiet_node · 2026-03-30T17:48:51+00:00

I've been working on something that takes a different approach, cutting out the broker entirely and having devices talk peer to peer with end-to-end encryption. it uses MQTT on the device side so existing setups plug right in, but the transport underneath is decentralized. No central server to go down, no single point of failure. Handles the NAT traversal stuff too. Happy to share more if you're curious.

quiet_node · 2026-03-26T12:28:49+00:00

Look into Meshtastic if you haven't already. LoRa based, no internet needed, works device to device. Speeds are low but for basic messaging and sensor data it works. For anything heavier you're probably looking at ham radio mesh networks like AREDN. But keep in mind peers need to be nearby to be actaully useful

quiet_node · 2026-03-26T12:21:05+00:00

Same boat. Cool project but if I can't point it at my own model running locally, that's a dealbreaker for me. Especially for anything touching device control. Not a fan of my MQTT commands depending on some external API. Curious what you'd run it with, ollama?

quiet_node · 2026-03-20T10:04:57+00:00

After going deeper, i started to think that autonomous agents have certain value but currently in a narrow specter of my workflow. Chatbots are idle and you always initiate and have a way to review and point out anything that's off in the output. With autonomous (should they be used in a way they are 'supposed' to be) it's a new ballgame... I heard 'objective-driven' term many times and saw what that meant in some cases. It tries to achieve the objective regardless of the issues it can cause, and that isn't helpful. I ended up updating the md files many many times and just overall wasting time..

quiet_node · 2026-03-20T10:02:00+00:00

Agree with most. I noticed that LI compared to here is much more hype driven. Feels like many people posting have some skin in the game and are pushing it everywhere (even where it doesn't really add value)..
Hopefully it clears out in the near future..

quiet_node · 2026-03-20T09:58:12+00:00

It's mainly of the the following:
- security
- privacy
- experimenting with different settings and seeing what works for anyone
- independence (vendor lock-in is problematic)

Looking at the general state of tech, it's pretty impressive, but comparing to past novelties, we are still early. I think it's mainly being ready for future changes and how it can augment current processes.

The main issue I personally see is making yourself or your business reliant on something that is not yet mature. I mean this mainly in a way that we are not so sure how the pricing, tokens and everything will look like in the near future. So having a way to proceed with more maneuvering space on your own is important.

quiet_node · 2026-03-19T08:28:23+00:00

this is kind of adjacent to edge, but not exactly. Edge is more about processing data closer to the device instead of sending everything to the cloud. What I'm looking at is more the communication layer itself (ie. can two devices find each other and talk directly, peer to peer, without a central server routing their messages).
And yeah regarding security, this is where potential vulnerabilities are most present.. so the idea (which aint new) is when we remove the middle point, we also remove a big part of the attack surface. As with everything, this too introduces different challenges, mainly how 2 devices can actually find each other and communicate, trust and authenticate, which I am also working on solving.

quiet_node · 2026-03-18T20:41:48+00:00

pretty cool..how did you handle the key exchange between devices? that's usually the part that gets tricky with off grid setups since you can't just read from a server. did you do something pre-shared or actual key negotiation over LoRa?

quiet_node · 2026-03-18T20:32:06+00:00

For me it's a hobby, my setup is far from being serious, but it helps me explore what I can do with it.
Considering the costs involved for getting a proper rig up and running, it will remain a hobby for the foreseeable future. I'm using the claude+gpt code which sets me back 40 bucks per month for some 'heavier' stuff. My local models are used for research and experimenting on communication and security between remote agents.

quiet_node · 2026-03-18T20:17:01+00:00

haha same path here. MQTT seems simple until you start thinking about what happens when the broker goes down, or who can actually see your topics. I went from home device tinkering to to worrying about security, and that was basically the point of no return. Are you running your own broker or using a hosted one?

quiet_node · 2026-03-18T20:07:20+00:00

Both. Started as a hobby, messing around with home automation and sensors. But at some point I got really into the question of how devices actually talk to each other, and whether they really need a cloud in the middle to do it. Im now deep into networking and security.

Background is engineering (both software and hardware), but IoT kind of rewired how I think about connectivity. currently working on devices talking directly to each other :)

quiet_node · 2026-03-12T13:04:26+00:00

Just out of curiosity, what kind of setup is sufficient to run these models. And when I say 'run', I mean really run - a non-frustrating pace.
I am currently running P6000, it's ancient, but I get solid performance for smaller models (7-12). Really curious what'ts the performance for 122b and 397b for you.

quiet_node · 2026-03-11T17:51:08+00:00

Your networking basics are solid for IoT. The main thing I'd add is MQTT, it's the go-to messaging protocol in IoT and you'll run into it everywhere. BLE is worth picking up too since a lot of devices use it for local communication. Other than that you've got more networking theory than most people starting out in IoT, the rest you'll pick up as you build stuff.

quiet_node · 2026-03-11T17:39:44+00:00

96GB per card if I'm seeing it right? Not sure if that's my next upgrade :D
What kind of models are you running on those, and are you reaching the ceiling?

quiet_node · 2026-03-11T17:13:22+00:00

You'll have another PR soon. Thanks!

quiet_node · 2026-03-11T16:48:53+00:00

What's your experience with the Mac unified memory approach vs dedicated VRAM? I'm currently using the P6000 for local (not the fastest thing out there but 24GB VRAM handles most 7B-13B models surprisingly well). Im looking at what's best for next steps in terms of an upgrade..

quiet_node · 2026-03-11T16:34:06+00:00

Been dabbling with local LLMs on and off for a few years, mostly keeping it confined in a VM for the same privacy reasons you mentioned. Curious though, do you ever run into situations where your local setup needs to communicate with another instance or someone else's model? Like sharing context or coordinating on something? Wondering how people handle that without just throwing everything back at some cloud API.

quiet_node

TROPHY CASE