2xsaiko

This is what I do too.

What they suggest sounds like setting up a bridge interface between your LAN and the VPN interface to connect the VPS with your LAN. That’s actually a good idea since it would not need you to have a separate /64 for your local network. In this case I’m pretty sure that your VPN needs to be a layer 2 VPN, i.e. transports whole ethernet frames instead of TCP/UDP only, for this to work correctly. Wireguard doesn’t do this, OpenVPN can for example.

To make the VPS a gateway, you need to configure it to forward packets between networks and then set it as your default route on the clients (with IPv6, default route is usually published using router advertisements, set up radvd service on your VPS for that). That’s pretty much it IIRC except for the firewall rules. Here’s an article that’s some cloud stuff but is also applicable to your situation: https://www.linode.com/docs/guides/linux-router-and-ip-forwarding/#enable-ip-forwarding

I had the network before moving here (created it when I did have a public IPv4). Can't test creating one new since it will only allow me to make one per IP.

Hm, it doesn't? I'm not behind CGNAT but I'm in a network I don't control (university dorm) so my gateway is just another device in the local network and I don't have a public IP which I control, which I feel like should effectively be the same thing as CGNAT, and it works for me. Maybe it isn't the same.

The easy way is to just use tunnelbroker.net, that is what I currently have (this would use one of their assigned net blocks, not the one from the VPS). Set it up on the Pi, set up IP forwarding with appropriate firewall rules, make the Pi serve RA so clients can assign themselves an IP, done (IIRC).

If you want to set up the v6/v4 gateway yourself, I would do this with a /64 you can fully route to your home network like you would get with tunnelbroker.net because then you don't have to deal with the network split and essentially two gateways for the same network (your Pi and the VPS), because otherwise your clients would assume the VPS is directly reachable since it's in the same network when in reality it would have to go through the gateway (you would have to set up an extra route in that case on every client, I think). You'd need a second network from Oracle for this.

But it's pretty much the same thing I would assume plus the setup on the VPS side, make the VPN route your /64 block (or use 6in4 which is what tunnelbroker.net uses), configure IP forwarding on the Pi and the VPS between the VPN interface and local/WAN respectively.

You're looking for an OAuth-compatible identity provider (personally I use Kanidm, if Keycloak does that too that works, I've never used it). And then set it up as the auth mechanism for Immich, and whatever else you want: https://immich.app/docs/administration/oauth

Podcasts are distributed via RSS (example). Spotify is probably just a frontend for that.

How about GNU M4 + Make (output)?

(to be clear this is a joke suggestion. but yes it is what I legitimately use)

I like to order tech stuff from mindfactory.de

Here's a demo one that works on rooted Android: https://github.com/Hirohumi/RustyRcs/

(Also iOS 18+ Messages lol)

It's not RCS's fault Google locks down the API on their OS.

No it's not. Get the spec here: https://www.gsma.com/solutions-and-impact/technologies/networks/rcs/universal-profile/#download

No it's not. Get the standard here: https://www.gsma.com/solutions-and-impact/technologies/networks/rcs/universal-profile/