The only way to look after land is to build a parking lot or use it to add another lane to a 32 lane highway.
You can get off with just a fine if you dig up the land and put down lawn turf. The fine is reduced if you use 5 gallons a day of water to keep it green.
(/s)
That’s like any FPS game ripping off any other FPS game.
Fight, capture, tame, train, breed animals.
Base building, research tree, enemy raids.
Exploration, resource gathering, survival.
I don’t think Nintendo has a monopoly on enslaving animals.
I know what you mean, tho. It’s always described as “Pokémon with guns and 3xE gameplay”.
But does Nintendo actually have a case that will hold up in courts?
Pocketpair seems confident they can defend against it. So either they have done their research and are up for a fight. Or they (think they) are calling Nintendo’s bluff.
But Nintendo has a whole pack of lawyers.
Unfortunately there are no details on what the patents being infringemed upon are, just that they relate to “Pocket Monster”.
GPT and the whole AI bs we have at the moment excels at being convincing. It’s even prepared to back up what it says.
The problem is, that all of that is generated. Not necessarily fact.
It will generate API methods, entire libraries, sources, legal cases, and science publications.
And it will be absolutely convincing as it presents and backs up those claims.
For example, GPT gives some API function of some library that magically solves your issue. Maybe you aren’t hugely familiar with the library, but you don’t trust GPT - so you research this made up API method and find the actual way to do it. Except you have GPT saying this exists and it works the way you want it to. So you research more, dig deeper.
Eventually you end up reading the source code, have a deeper understanding of the API in general and how to actually find useful answers (IE how to search query for it), and end up using the method you found while trying to find the mythical perfect API method.
I mean, I guess that’s a win? You learned some documentation, you solved the problem… Who cares?
Maybe I’m just bitter because that was how I first tried any of the new AI things. And I wasted 2-3 hours instead of actually solving the fucking problem by consulting the facts.
Reminds me of the story of the old engineer asked to come in and fix some machine in a factory.
The engineer inspects the machine, marks it with some chalk, then strikes the chalk mark with a hammer.
The machine works again.
The company asks for an itemised invoice after seeing the initial invoice for $10k.
To which they received:
- hitting chalk mark with hammer: $1.
- knowing where to place the chalk mark: $9,999
GPT suffers from garbage-in garbage-out just as much as a search engine does.
Knowing how to find search results to fix your specific situation is a skill.
Utilising GPT for such a task is equally a skill. With the added bonus of GPT randomly pulling the perfect API/Library out of its ass
I presume the investigation is taking official testimonies and gathering actual (and traceable) evidence in order to legally confirm what we all know.
It’s all amendment rights until it’s one of the racist fucks that gets murdered.
Then the police get military equipment to deal with the rising crime rates.
It’s from 2015, so its probably what you are doing anyway
I would say the more regular expiration and renewal of an LE cert is better.
It’s an ongoing check instead of an annual check.
At the homelab scale, proxmox is great.
Create a VM, install docker and use docker compose for various services.
Create additional VMs when you feel the need. You might never feel the need, and that’s fine. Or you might want a VM per service for isolation purposes.
Have proxmox take regular snapshots of the VMs.
Every now and then, copy those backups onto an external USB harddrive.
Take snapshots before, during and after tinkering so you have checkpoints to restore to. Copy the latest snapshot onto an external USB drive once you are happy with the tinkering.
Create a private git repository (on GitHub or whatever), and use it to store your docker-compose files, related config files, and little readmes describing how to get that compose file to work.
Proxmox solves a lot of headaches. Docker solves a lot of headaches. Both are widely used, so plenty of examples and documentation about them.
That’s all you really need to do.
At some point, you will run into an issue or limitation. Then you have to solve for that problem, update your VMs, compose files, config files, readmes and git repo.
Until you hit those limitations, what’s the point in over engineering it? It’s just going to over complicate things. I’m guilty of this.
Automating any of the above will become apparent when tinkering stops being fun.
The best thing to do to learn all these services is to comb the documentation, read GitHub issues, browse the source a bit.
Bitwarden is cheap enough, and I trust them as a company enough that I have no interest in self hosting vaultwarden.
However, all these hoops you have had to jump through are excellent learning experiences that are a benefit to apply to more of your self hosted setup.
Reverse proxies are the backbone of hosting and services these days.
Learning how to inspect docker containers, source code, config files and documentation to find where critical files are stored is extremely useful.
Learning how to set up more useful/granular backups beyond a basic VM snapshot in proxmox can be applied to any install anywhere.
The most annoying thing about a lot of these is that tutorials are “minimal viable setup” sorta things.
Like “now you have it setup, make sure you tune it for production” and it just ends.
And finding other tutorials that talk about the next step, to get things production ready, often reference out dated versions, or have different core setups so doesn’t quite apply.
I understand your frustrations.
It’s good to document weird and creepy behaviour.
If things like this don’t make the news cycle, they essentially go un-called-out. Which might make it seem like normal or acceptable behaviour.
Weird behaviour doesn’t live up to scrutiny
I’ve been meaning to play with rust, and I’ve always enjoyed tinkering with various MCUs… Although I’m not very strong with firmware/embedded programming.
Do you think programming an ESP32 is a good project for learning rust?
Any suggested place to start? (Tutorials, YouTube Vida etc)
Yeh, but my ZFS partition is a COW
Blowing up as in catastrophically failing.
Not blowing up as in to the moon.
I guess there is a difference between “it’s known to happen” and “a nation state accuses another nation state”
Nano is useful because it is everywhere.
There are better editors, but being familiar with nano and it’s shortcuts means you can edit files pretty much anywhere.
Same with knowing the basics of vim (like being able to edit, exit and save)
I’m using android jerboa, and I don’t see a heart.
Dunno if there has been an update recently, tho
Oh, this looks great!
I’ve been struggling between customize and helm. Neither seem to make k8s easier to work with.
I have to try cuelang now. Something sensible without significant whitespace that confuses editors, variables without templating.
I’ll have to see how it holds up with my projects
If you want remote access to your home services behind a cgnat, the best way is with a VPS. This gives you a static public IP that your services connect to, and that you can connect to when out and about.
If you don’t want the traffic decrypted on the VPS, then tunnel the VPN back to your homelab.
As the VPN already is encrypted, there is no point in re-encrypting it between the vps and homelab.
Rathole https://github.com/rapiz1/rathole is one of the easiest I have found for this.
Or you can do things with ssh tunnels.
For VPN, wireguard is very good