zergtoshi

joined 2 years ago
[–] zergtoshi@lemmy.world 1 points 18 hours ago

To put it bluntly: if you do an offline transaction, you're prone to fraud.
If you expect the senders account chain to have balance x (because that's your offline record for that) and the sender has sent all funds to a different address after you synced that account chain, you receive money that isn't there - kind of like an invalid cheque.
I have no clue how that would work in practice, because to know a random account in advance, you'd have to sync the whole amount of account chains there is (called block lattice in Nano's case).
With a mobile device that's hardly feasible and without a mobile device I don't see how you'd get in contact with people to make such an offline transaction.

That kind of specialized AI is what I imagine to be a use case for locally run AI, too.
After all you don't want to build processes on an AI, where you have zero control over what happens behind the curtains.
That includes feeding potentially sensitive data back to it as well as being unable to control the training data set, its learning, version numbers, etc.

[–] zergtoshi@lemmy.world 2 points 21 hours ago

Wouldn't infrared achieve the same at less risk for the eyes of other people and less power consumption?

[–] zergtoshi@lemmy.world 2 points 21 hours ago

WLAN depending in the standard in use runs exactly there.

[–] zergtoshi@lemmy.world -1 points 22 hours ago (2 children)

Funny, that you even know about Nano!
...it's one of the often overlooked projects because it doesn't have a ton of fuck-off-money and instead tries to focus on a solid protocol.

Nano has a lot of interesting attributes, but I fail to see how what you describe would work in practice.
If both parties want to make sure there are no shenenigans at play, they need to know about the most recent state of the respective account chains, which essentially requires them to be online for agreeing on said transaction.
But overall Nano is very fast and efficient by design and only a failure in terms of "gainz for Lambo".

As we're here in a thread about AI I should remark that machine-to-machine-payments - in this case: agent-to-agent-payments - would work pretty well with Nano as currency because of the transaction finality (typically less than 1 second) and the feeless nature of transactions.
If AI agents are looking for the most viable way to transfer tiny amounts of value fast and without fees they might find Nano and use it - who knows...
...and just like Nano showed that efficient ways to create digital money are possible I'm hoping for efficient AI models that are economically and ecologically worthwhile.

[–] zergtoshi@lemmy.world 3 points 1 day ago (1 children)

Not OP, but I read it as "accepting" that kind of money equals getting bought with it and by the people who put the money in the PAC.

[–] zergtoshi@lemmy.world 15 points 1 day ago (7 children)

I'm glad you specifically pointed out proof-of-work blockchains.
They're very inefficient (economically and ecologically) by design. In almost all cases this design isn't warranted.
Alas there are other designs and while most of them are rubbish as well, a few ones are doing things quite right.

I hope that just like other schemes than proof-of-work were thought of regarding blockchains, there will be AI models that are way, way more efficient and ideally can be run locally - for those cases that can use AI...

[–] zergtoshi@lemmy.world 6 points 2 days ago

Good, but why not 120%?

[–] zergtoshi@lemmy.world 17 points 3 days ago

You missed the part where that was fully automated.
With E2EE someone at the other end of the communication would've sounded the alarm.

But go on normalizing that authoritatian state.
I'm glad that other people see the problem that lies within such surveillance.

[–] zergtoshi@lemmy.world 1 points 3 days ago

In that case I'd be willing to shit the extra mile without shortcuts.

[–] zergtoshi@lemmy.world 14 points 4 days ago (2 children)

I think the dead should be allowed to reap the respect they earned in life.
In some cases that means you intentionally got to get infected by dysentery just to be able to almost shit enough on their grave.

[–] zergtoshi@lemmy.world 21 points 5 days ago (2 children)

How long until you have to watch an ad before you can start going with the car?

[–] zergtoshi@lemmy.world 5 points 1 week ago

About time to return the favour and free the USA from the Nazis...
Waiting any longer is risking the step from concentration camp to mass murdering camp.

 

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 ›