Definitely, but sandboxes can be escaped, and you can't protect everything via sandbox. Apparently its all cloud anyway, but if it were local and sandboxed, there are still exploits like rowhammer and spectre that may cause further risks.
Its taken years to get browser sandboxes to where they are, and even they get broken every so often.
If you go down the "Little Free Library" + Lemmy community route, you can easily attach NFC stickers to the books, that point to a thread.
You can buy a bunch of NFC stickers for a few dollars and program them with your phone (make sure you write protect them once written). Alternatively, you could print QR codes onto stickers.
Would be pretty cool, please share the community when you have it setup.
You could easily create QR code (or NFC tags) that linked to a post in a lemmy community.
As for posting opinions without a login, that is a little harder to pull off.
Firstly, anonymous internet opinions are usually garbage, so you wouldnt want it to be truely anonymous. You'd be wading through spam in no time.
If there was a way to encode creds into the QR code, such that it autologged into an account, that would be kinda cool, and it might last a little while until the creds were leaked.
A basic (no-auth) guestbook site could be knocked up fairly easily by anyone (give me a week or so and I'll give you something if you want, you'll have to host it though), but getting the auth part right is nontrivial.
Yes and no, the linker does nicely trim a lot of the fat, but rust binaries are still pretty chonky. Its good chonky (debug etc), and static compile doesnt help, but they are quite fat.
Also doesnt help compile times that you have to build all this extra stuff, only to throw most of it away.
I'm not sure its a problem in of itself, but i agree it definitely enables a problem. Between "is-even" and vibe coding, modern software engineering is in a very sorry state.
Its certainly more painful to collect dependencies with cmake, so its not worth doing if you can hand roll your own easily enough.
The flip side is that by using a library, it theoretically means it should be fairly battle-tested code, and should be using appropriate APIs. File watching has a bunch of different OS specific APIs that could be used, in addition to the naive "read everything periodically" approach, so while you could knock something together in an hour, the library should be the correct approach. Sadly, at least in rust land, there are a ton of badly written libraries to wade through... 🤷
That also makes sense. Wouldnt that potentially risk the users de-anonymising themselves (and OP)? They wouldnt be protected by the tor browser protections, so a site could request location etc.
Standard VPN is probably a better tool.
For OP: Routing all traffic through a VPN isnt too hard, you can just add the VPN client and then route traffic through the interface. You can do it all from Luci. If you want more info, I can share how I did it with wireguard.
Depending on your country's laws, you may be on the hook for any content that is accessed via your network. So all the child porn, extremist content etc, thats all possibly on you.
Hacking risk is minimal, but every additional service you run on your router increases its attack surface.
See, this is why naming is important, is this the SDK for "Windows App" (the rdp thing), or something else. I think its something else, but who the fuck knows anymore.
Oh, well, if it requires a password that is pretty much solved. The original commentor made it seem a lot less hands on.
I was under the impression that the shim let OS's boot all the way up, and that it was just a standard part of the boot process, I was suggesting instead that the signed binary only let's you add a new key, which you can then use to boot without the shim.
Doesnt help when the key expires though.
Thanks for the additional info, greatly appreciated.
Definitely, but sandboxes can be escaped, and you can't protect everything via sandbox. Apparently its all cloud anyway, but if it were local and sandboxed, there are still exploits like rowhammer and spectre that may cause further risks.
Its taken years to get browser sandboxes to where they are, and even they get broken every so often.