I used to do that but I find the UX of that quite annoying because before you can do: systemctl status and see what's up with all the system services. Now you have to do systemctl status -M <user-for-that-stack> for every stack that you're running to get a complete picture.
I haven't found a way around that and would be very thankful for pointers.
I tried to find out what this actually does but apart from a video that is very hard to watch on mobile, there's really nothing there that tries to sell me on this. Why not use the readme to do your elevator pitch?
I've recently deep-dived into QEMU performance especially in order to cut down boot/bootstrapping times for quickly running tests and I'd like to share some tricks:
You could try running rustic on your repository. It should be a drop-in for restic and maybe it's faster? I would actually be very interested in this. Would be great if you could do that and report back.
I did this once as a small experiment. Basically use a small TCP stack with LoRa as layer 1 and then expose the whole thing as a Linux kernel module. It was a bit shitty but it seemed promising.
For some reason, I don't find LoRaWan at all alluring. As far as I can tell, in the end it's in the hands of one company and that really defeats the spirit for me. I mostly just use LoRa for point-to-point connections with my own shitty networking stack.
You're looking LoRaWan which is not the same as LoRa. In fact I believe web browsing to be quite feasible if you just use LoRa with your own network stack.
Haven't used it yet, I'm a bit too scared to put something like this into production anywhere. I might do a small installation with a toy project somewhere, though. Seems easy enough to set up.