zergtoshi

joined 1 year ago
[–] [email protected] 2 points 1 day ago

Mario's younger brother vibes intensify.

[–] [email protected] 2 points 3 days ago

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.

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago)

Apparently sometimes leaning on amendments of the constitution is required to protect said constitution and hence the people protected by it.

[–] [email protected] 2 points 1 week ago

If one takes beta-carotene instead of vitamin a, an existing deficiency can be resolved without introducing any risk of reaching toxic levels.

[–] [email protected] 10 points 2 weeks ago

Casings would be a viable alternative or so I hear.

[–] [email protected] 1 points 3 weeks ago

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.

[–] [email protected] 4 points 3 weeks ago

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.

[–] [email protected] 9 points 3 weeks ago (1 children)

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.

[–] [email protected] 5 points 1 month ago

A broken clock may be forever wrong, whereas a stopped clock may be right twice per day.

[–] [email protected] 1 points 1 month ago (1 children)

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 :)

[–] [email protected] 35 points 1 month ago (1 children)

If they weren't detained and roaming around through the country instead, they'd even spend money.
Make it make sense.

 

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 having a data centre SSD and lots of RAM is a good start.

Hardware

In the future all services are meant to run on this machine:
Case/Mainboard: AsRock Deskmeet X300
CPU: AMD Ryzen 5 5600GT
RAM: 64 GB
Storage:

  • 480 GB SSD (Intel DC S4500 Series)
  • 4 TB SSD (Team Group MP44)
  • 16 TB HDD (Seagate Exos, yeah, I know, but realized too late...)
    OS: Proxmox 8.3.1

Future mode of operation

Here's a high-level scheme of what I plan to do:

  • Install Proxmox on the Intel SSD
  • Use the 4 TB SSD as storage drive for the machines
  • Use the 16 TB HDD as storage drive for backups and additional storage (for files that mainly get read like media) for the machines
  • Migrate each physical device to a virtual machine (or create a new one to replicate the service)
  • Repurpose the mini PC as Proxmox backup server

Help!

The areas where I think reading documents can't beat experience are:

  • Do I use BTRFS or ZFS? I tend to use ZFS because of its advantages when making backups. What would you do?
  • Do I use QEMU/KVM virtual machines or LXC/LXD cointainers? Performance wise QEMU emulating the host architecture should be the way to go, right?
  • I shy away from running all services as Docker on the same machine for backup/restore purposes and rather have VMs per service. Is there anything wrong with this approach?
  • I'd love to keep NextcloudPi (because it'd make it easy to migrate settings and files) and there's an LXD container for it. Would you recommend doing a switch to Nextcloud AIO instead?
  • I've equipped the Deskmeet X300 with a WiFi card and antennas. AFAIU trying to use WLAN instead of LAN will create some trouble. Has anyone running Proxmox on a machine with WLAN insteal of LAN access successfully?
  • I'm aware that Proxmox comes with a firewall, but I don't feel very confortable using a software firewall running on the same machine that hosts the virtual machines. Is this just me being paranoid or would you recommend putting a hardware firewall between the internet access and the Proxmox server?
  • What else should I think of, but haven't talked about/asked yet?

Thank you very much for your time and your suggestions in advance!

view more: next ›