deleted by creator

It all is if you’re getting both. You’re sharing IPs with many different devices at the same time. That’s how it works.

Read up on it.

25% of what?

1/4 of 100% of what?

I’ve seen zero RISC devices in the wild, and the phrasing here wants me to think I should have by now.

deleted by creator

I think you’re missing the point or not understanding.

What you’re talking about is just running a model on consumer hardware with a GUI. We’ve been running models for a decade like that. Llama is just a simplified framework for end users using LLMs.

The article is essentially describing a map reduce system over a number of machines for model workloads, meaning it’s batching the token work, distributing it up amongst a cluster, then combining the results into a coherent response.

They aren’t talking about just running models as you’re describing.

I want to say Sonarr has a regex renaming feature, but I may just be making that up as I’m not looking at my instance right now. Doing whatever renaming based on a pattern would be preferable during the download phase in order to keep the metadata of each service clean.

Failing that, if you have a predictable list of release group strings you want removed from filenames, a one liner with sed or similar would take care of this. You’d then break the known locations of these files by any service tracking them of course, but they will eventually be reindexed.

PDF reference of the API here: https://cdn.arstechnica.net/wp-content/uploads/2026/01/2025.12.18-SoundTouch-Web-API.pdf

Seems kind of pricey for that specific unit, but it should work well for just hosting simple services.

It’s a dumbass AI-powered recommendation engine with an awful GUI. That’s about it.

As far as it being malicious, that’s really up to you.

It starts with the hardware first. You started well with tuning your CPU/MEM frequency settings, but that matters less if you’re running giant PSUs (or redundant), more drives than you need, and a huge number of peripherals.

Get a cheap outlet monitor to see what your power draw is and track it at the wall. I just got these cheap Emporia ones. I’m sure there’s more reputable ones out there.

Don’t go crazy with your networking solution if you don’t need them. PoE switches draw tons of power even when idle, and a 24-port switch is a huge draw if you’re only using 3 of them.

Consider getting a power efficient NAS box for backend storage, and low power Minipc for frontend serving instead of using a power hungry machine for all your network apps.

You can dive deeper into any angle thing, but these are the basics.

There’s only so much reliability you can build into a simple home setup without it being a major loss on investment. In a datacenter situation, you’d have fault tolerance on all the network ingress: load balancers, bonded interfaces, SDWAN configurations…etc.

Unless you want 3 of everything you own, just do the basics, OR I guess consider hosting it elsewhere 🤣

Focus more on why the service is going down, and solve for that. Make it reliable by restarting automatically in the face of failures. A Reverse Proxy should be dead simple, and not change states between restarts, so it shouldn’t be dying in the first place. Having it restart on failures should be simple and reliable.

Hmmm, it does seem they’ve finally raised prices. Well that’s a huge bummer.

I can’t say the 3 options you posted are really good deals, but maybe that’s just the market in Australia. I’d check to see what the max RAM in those are and upgrade to at least 16GB though. It should still be cheap for non DDR5.

Anything can be a “server” in your use-case. Something low power at idle will not cost an arm and a leg to run, and you can always upgrade later if you need more.

Check the Minisforum refurb store and see what you can get for under $150.

1. dig , learn it, love it
2. Use a phone or other device outside your network to compare results from #1

They do no such thing.

The first link explains the protocol.

The second explains WHY one would refer to client and server with regards to Wireguard.

My point ties both together to explain why people would use client and server with regards to the protocol itself, and a common configuration where this would be necessary for clarification. Ties both of them together, and makes my point from my original comment, which also refers to OP’s comment.

I’m not digging you, just illustrating a correction so you’re not running around misinformed.

It wasn’t clear where OP was trying to make a point, just that the same host would be running running Wireguard for some reason, which one would assume means virtualization of some sort, meaning the host machine is the primary hub/server.

Honestly, I know a lot of people that do, but delivery address is less of a problem than other personal information.

I always make fake derivative versions of my names for anywhere I but from so I can tell who is selling my information and not buy from them anymore. The address matters less. I’m not avoiding the government and “hiding out” fo fuck’s sake, I’m just avoiding having my data leaked like this. Any number of fake names that like up on the same address also dilutes these data sets the shady dealers try and ship around. The more names at any single address reduce the confidence of its accuracy, and therefore price.

Uhhh, nooooo. Why are all these new kids all in these threads saying this crazy uninformed stuff lately? 🤣

https://www.wireguard.com/protocol/ https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/configuring_and_managing_networking/setting-up-a-wireguard-vpn

And, in fact, for those of us that have been doing this a long time, anything with a control point or protocol always refers to said control point as the server in a PTP connection sense.

In this case, a centralized VPN routing node that connects like a Hub and Spoke is the server. Everything else is a client of that server because they can’t independently do much else in this configuration.

Uhhhh…that is…not how you do that. Especially if you’re describing routing out from a container to an edge device and back into your host machine instead of using bridged network or another virtual router on the host.

Like if you absolutely had to have a segmented network between hosts a la datacenter/cloud, you’d still create a virtual fabric or SDLAN/WAN to connect them, and that’s like going WAY out of your way.

Wireguard for this purpose makes even less sense.

Why would you run a WG Client and WG Server on the same host? Am I reading that second mark wrong?