I've had exactly the same problem a while ago with Barclaycard, had to phone them.

Podman Quadlets is what you're after, I think.

In reality meta quest games use their Platform SDK (for things like user entitlement check, match making, leaderboards, DLC) I'm not sure it'll be an easy port for Quest games because you'll be missing Meta's services that run on the quest itself.

Neat. Do you ever get issues with your email being marked as spam? And if I understand correctly from Addy docs, you have to rent a VPS somewhere, or it's possible to run the whole thing on your own hardware exposed to the internet?

AliasVault has its own built-in email server that allows you to create unique email addresses and receive emails straight in AliasVault. No third-party email service required.

I don't get how does that work exactly in a self hosted environment?

Currently just alpine with docker compose, but I initially wanted to use podman, this was before quadlets were a thing and I found it very cumbersome to configure the networking between containers, also recall having to use kustomize as an extra step, so I gave up and went with compose.

Now there are quadlets with podman, which seem to do everything I need but require systemd. I'd be happy to switch from openrc to systemd just for the sake of using podman.

I'll finally be able to switch from docker compose to podman with quadlets on my server running alpine

GitLab LFS storage is mad expensive. I regret buying into it... We have an unreal engine project and the assets cross over 20GB, not raw assets mind you. I've self hosted perforce before and should have stuck with that

You would probably want to start with the openai-agents SDK in that case.

Isn't VST pretty much a wild west anyway? I wonder how much is this really gonna help to standardize the tools/plugins

Mainly use it as a documentation search for APIs I'm not familiar with, or when I'm not sure what options there are to approach a problem. I work with unreal engine a lot, so I'd get a few pointers from an LLM first, then go read the source code of those APIs and inplement the rest myself.

I guess it can go both ways, but I'd probably put nixos under minimal and experienced branch