Tailscale is a mesh VPN. Its a level of abstraction passed a regular VPN, lime wireguard or OpenVPN. Tailscale uses wireguard under the hood.
rutrum
Very beautiful setup. Thank you for sharing. What is the little table that sticks out from the counter?
I never considered there could be libraries for building these games, just assumed any game would always start from scratch. I've not heard of any.
I made an attempt to build my own from scratch a long time ago, and I ended up with an engine in code and a yaml file to configure everything. I wonder if there are solutions where you dont write code directly, but you write plaintext configuration files and just pump it into the game engine.
I don't know how much content there is to share, so you might be overflowing with things to talk about every week. But I fear that doing so much effort weekly could be unsustainable. I would suggest, or hope you consider, a less freqent blog/podcast, like every other week. I think this would be more modest, and easier to maintain. You wouldn't need to change to title of the blog, either.
Anyway, this is an exciting project and I'm thankful for your work.
Can you elaborate more on deduplication? Is this a feature you setup, or does it sort of work out of the box? This is a new concept to me, but sounds incredibly useful, especially in that scenario.
Perhaps I'm guilty of good luck, but is the trade off of performance for reliability worth it? How often is reliability a problem?
As a different use case altogether, suppose I was setting up a NAS over a couple drives. Does choosing something with COW have anything to do with redundancy?
Maybe my question is, are there applications where zfs/btrfs is more or less appropriate than ext4 or even FAT?
How exactly do you simulate die rolls? Do you actually use a random number a bunch of times and average? Because its 2d6, it has a known distribution. You could iterate over all combinations and use the probably distribution to weight each result. How did you accomplish this?
Those keycaps are very nice. What was something you learned from doing your first build?
Keep it up. I enjoy hearing about the updates.
Yeah when you iterate over cards mutably, you're borrowing it again at the line cards[id].copies +=... I think. If you're going to access the card by index there then you loop over indicies at the top lop instead of iter_mut
Theres so many. Check out the awesome list: https://github.com/awesome-selfhosted/awesome-selfhosted
I think your stategy should be one service at a time. Do everything in docker, and start by tackling a simpler service. For example, you should try paperless-ngx. Absolute game changer. I didnt realize how much managing ny own directory structure sucked until I used this. Then, grow your service list more and more!