duncesplayed

What kind of rube works in the same country they live in? I met a lot of WFH workers when I visited Thailand, and not a single one of them was working for a company in Thailand.

OMF is by far the best fighting game I've ever played. Absolutely unmatched.

I chatted with Kenny Chou/cccatch on IRC once (the guy who wrote the soundtrack to OMF) and he told me about the technology stack they used for music in that game, which I found pretty interesting. He wrote the music in MultiTracker Module Editor and they had some proprietary software that would convert .MTM files into the music engine's native format and package them up. The clever thing is that all the songs were saved together in one package, which means that if he reused the same samples in all of the songs (which he had to do), then the tool would be clever enough to have each sample on disk/in memory only once, so samples only had to be loaded when you started the game. Then when the game switched songs, only the pattern data (notes) had to be freed/loaded.

BitWarden+PiHole+NextCloud+Wireguard combined will add to like maybe 100MB of RAM or so.

Where it gets tricky, especially with something like NextCloud, is the performance you see from NextCloud will depend tremendously on what kind of hard drives you have and how much of it can be cached by the OS. If you have 4GB of RAM, then like 3.5GB-ish of that can be used as cache for NextCloud (and whatever else you have that uses considerable storage). If you have tiny NextCloud storage (like 3.5GB or less), then your OS can keep the entire storage in cache, and you'll see lightning-fast performance. If you have larger storage (and are actually accessing a lot of different files), then NextCloud will actually have to touch disk, and if you're using a mechanical (spinning rust) hard drive, you will definitely see the 1-second lag here and there for when that happens.

And then if you have something like Immich on top of that....

And then if you have transmission on top of that....

Anything that is using considerable filesystem space will be fighting over your OS's filesystem cache. So it's impossible to say how much RAM would be enough. 512MB could be more than enough. 1TB could be not enough. It depends on how you're using it and how tolerant you are of cache misses.

Mostly you won't have to think about CPU. Most things (like NextCloud) would be using like <0.1% CPU. But there are some exceptions.

Notably, Wireguard (or anything that requires encryption, like an HTTPS server) will have CPU usage that depends on your throughput. Wireguard, in particular, has historically been a heavy CPU user once you get up to like 1Gbit/s. I don't have any recent benchmarks, but if you're expecting to use Wireguard beyond 1Gbit/s, you may need to look at your CPU.

I disagree. I don't think it's the world's responsibility to cater to someone's bad browser configuration.

The big difference between [the WWW] and Hyper-G is Hyper-G's distributed link server. This server keeps track of all the relations (e.g. links) between Hyper-G objects, allowing for automatic maintenance of the information network. For example, when an object gets deleted, the link server will be able to find and delete all links pointing to the object. In contrast, in Gopher and WWW there is no easy way to find out what other documents are pointing to a given document

Dear God that sounds horrible and amazing. I'm glad it didn't catch on, but I really want to see it in action.

Yes, with some big "if"s. NextCloud can work very well for a large organization if that large organization has a "real" IT department. I use "real" to describe how IT departments used to work 20+ years ago, where someone from IT was expected to be on call 24/7, they built and configured their own software, did daily checks and maintenance, etc. Those sorts of IT departments are rare these days. But if they have the right personnel, it can definitely be done. NextCloud can be set up with hot failovers and fancy stuff like that if you know what you're doing.

It is the ticket. Tickets don't really exist. Even before the Internet and digital technology, what we called a "ticket" (a slip of paper that you showed to get in) was in reality just a receipt/proof of purchase. "Ticket" and "receipt" are 100% synonymous.

This seems to be the answer

Maybe that's why the new one got renamed to Aptos, ha.

That's less fun. I believe you've either got to put everything on one SLAAC network (no static IPs), or you've got to use DHCPv6 (with a smaller network size) instead of SLAAC.

There are a few projects here and there that do it, like this one (haven't tried it). Generally if you find projects online like that, they're generally written for the purposes of a particular academic paper and might not work very well for the general case, but the worst you can do is try it out.

The "random ass websites" you find that do a good job of it probably have put more work into training a good general-purpose model. If you want, you could try doing that yourself, but it would require a fair bit of work.

(Whoops, accidentally hit "Delete" instead of "Edit" and Lemmy doesn't ask for confirmation!! Boo!! I'll try to retype my comment as best I can remember)

I'll buck the trend here and say "Yes, for a home LAN, it's absolutely worth it. In fact for a home LAN it is more important than in a data centre. It is absolutely the bees' knees for home and is worth doing."

All of that depends on how your ISP does things. When I did it, I got a /56, which is sensible and I think fairly common. If your ISP gives you anything smaller than a /64, (a) your ISP is run by doofuses, but (b) it's going to be a pain and might not be worth it. (I now live in literally one of the worst countries in the world for IPv6 adoption, so I can't do it any more)

The big benefit to it is that you can have your servers (if you want them to be) publicly reachable. This means you can use exactly the same address to reach them outside the network as you would inside the network. Just make one AAAA for them and you can get to it from anywhere in the world (except my country).

When I did it, I actually just set up 2 /64s, so a /63 would have been sufficient (but a /56 is nice). Maybe you can think of more creative ways of setting up your networks. Network configuration is a lot of fun (I think).

I had 1 /64 for statically-assigned publicly-reachable servers. Then I had a separate /64 for SLAAC (dynamic) end-user devices, which were not publicly reachable (firewalled to act essentially like a NAT). (Sidenote: if you do go to IPv6 for your home network, look into RFC7217 for privacy reasons. I think it's probably turned on by default for Windows, Android, iOS, etc., these days, but it's worth double-checking)