Yes, it's small, runs at a few watts and is silent.
The Celeron J4105 and Pentium J5005 CPUs in the Wyse 5070 are very close to each other both regarding energy and computing power.
Have a look here: https://www.cpu-monkey.com/de/compare_cpu-intel_celeron_j4105-vs-intel_pentium_silver_j5005
I would take either.
You'll have a hard time finding another silent box with such a small footprint that's able to take 2 gumstick drives - even if one of them needs some tinkering - and 32 GB RAM.
You could try to get a used Dell Wyse 5070.
If you pick the right dual ranked RAM modules (e.g. Patriot PSD416G26662S), you can have a max. of 2x16 GB.
There's a slot for SATA SSDs onboard and with the right adapter (PCIe A/E key -> M key) you can plug an NVME SSD in the WiFi PCIe slot, which gives plenty room for storage and even allow for a disk mirror setup.
All that is very well within your budget and quite a beast that once was meant to be just a thin client.
I believe you're right, but that doesn't solve the problem of making routine full backups, which would come in handy if the device gets lost or breaks.
One can hope future versions of Seedvault care less about what apps want.
I'm being bugged by Seedvault caring for apps that have a 'don't backup app data' flag.
I could live with that being a default setting, which can be manually overwritten in the Seedvault settings for these apps.
Apps not allowing (in case of Seedvault: encrypted) full backups while offering no or bad built-in backups is just cumbersome when trying to have current backups.
Well, some people read something different into my comment. I better delete it, before I create any more confusion...
Oh, they can go in one sentence, if done right.
Nano offers fast transactions on a decentralized network while using very little energy.
Strictly speaking it's not just one blockchain, but one per account, which only the account owner can update (add blocks to it).
This asynchronous design is what makes Nano so fast, because there's no need to wait for others when updating one's own blockchain.
What it doesn't have (yet?) is a sufficiently large network effect, which it may never acquire.
But it is one example of an attempt at making digital money based on blockchain technology, which is not just a copycat, scam, rugpull or other malicious nonsense.
Monero comes to mind as well and maybe a handful others.
Sadly almost all around blockchain is not just not innovative, but outright evil.
Au contraire!
https://en.m.wikipedia.org/wiki/Paradox_of_tolerance
Apparently sometimes leaning on amendments of the constitution is required to protect said constitution and hence the people protected by it.
If one takes beta-carotene instead of vitamin a, an existing deficiency can be resolved without introducing any risk of reaching toxic levels.
Casings would be a viable alternative or so I hear.
It's less the motion of the atmosphere that causes the distortion, but rather differences in its temperature and hence the density of the air, which causes differences in the refraction index of the air along the way of the light.
The variable refraction index makes it look like the atmosphere is moving though.
But that's the effect of the light not going in a straight line and not the cause of it.
Don't forget to mention what xylitol does to dogs.
Small amounts of arund 2 g per 10 kg body weight are very likely lethal within a short time if not treated instantly.
Xylitol can be in sugar free candy or chewing gum potentially making one piece of them a lethal dose for small dogs.
Unless you find/invent a new procedure that's way more efficient instead of doing more cycles of known procedures.
If you want to save energy, consider launching him outside our solar system instead.
I'd be fine with both though and even grant him the trip to Mars of which he apparently dreamt some time ago.
A broken clock may be forever wrong, whereas a stopped clock may be right twice per day.
Then I would stick with ZFS if you're already familiar with it.
I'm not at all familiar with ZFS. It'd be part of the learning curve as is Proxmox as a whole. But I consider knowledge about both as useful.
LXD is a management system for LXC containers. If you're just starting out, stick, with LXD. It's much more user friendly.
I will stick with LXD for containers then if I don't use a VM.
Not really. I run a VPS which acts as a reverse proxy for my docker setup, which has non-local storage via NAS. I don't particularly see a point in fragmenting docker like that, but if that's how you want to roll, then go for it.
This due to my lack of experience with Docker and backing up all properly to do a complete restore. It looks like I have learning curves in more than just one area ahead of me.
I very strong advise against this. But it's perfectly possible. You're just at the whim of the airwaves. I live near a main highway and sometimes when large trucks go by, I lose WiFi for a quick second. Really fucks with certain things.
Yeah, nothing beats a setup, where each network interface is the maximum size of a collision domain.
Yes. Nothing wrong with software firewalls.
Gotta get ahead of that old school me that thinks running a software on a different hardware plays a crucial role in the threat model.
Also yes. Particularly (like I have setup) I have a software firewall that tunnels my local vLAN to my VPS, and then everything else is further bisected using a hardware firewall--so all outside incoming requests are proxified by my VPS meaning any direct connections are dropped by the software firewall, then I manage ports from within the hardware switch.
That's a setup I may borrow from you :)
If they weren't detained and roaming around through the country instead, they'd even spend money.
Make it make sense.
Ah, the famous rug pull after having developed an open source project for over 10 years.
Makes sense.
Permanently Deleted
And here's a potential solution for people who want to remain in control whether this gets installed on their phone:
https://lemmy.world/comment/15344781

Proxmox setup - help needed
Dear selfhosters!
I come to you in the hope of help for avoiding some rookie mistakes.
I plan to migrate my very diverse hard- and software environment to a single machine.
Current mode of operation
I operate several RaspberryPis, a hardware firewall running on OpenWRT and a NUC like mini PC.
The RaspberryPis more or less are there for a single function; one runs Nextcloudpi, two run PiHoles, another one runs iSpy.
The mini PC is for the tasks that are heavier on CPU, RAM or storage space.
Maintaing this has become somwehat cumbersome and a replacement is dearly needed. My plan is to move all to a Proxmox sever.
I do have a general idea how to set up things, but as I'm brand new to Proxmox, I fear that there's a lot of mistakes to be made. I haven't read all documentation, but enough to know that it's no easy task to set up and operate Proxmox properly.
I'm aware that not having server hardware (e.g. no ECC RAM) is not the best setup, but AFAIU at least havin