Playtests typically involves a full on NDA for this reason. If your playtest is aimed at creators that are allowed to stream it’s not a playtest, it’s a marketing exercise.

If it’s only you (or your household) that is accessing the services then something like hosting a tailscale VPN is a relatively user friendly and safe way to set-up remote access.

If not, then you’d probably want to either use the aforementioned Cloudflare tunnels, or set up a reverse proxy container (nginx proxy manager is quite nice for this as it also handles certs and stuff for you). Then port forward ports 80 and 443 to the server (or container if you give it a separate IP). This can be done in your router.

In terms of domain set-up. I’ve always found subdomains (homeassistant.domain.com) to be way less of a hassle compared to directories (domain.com/homeassistant) since the latter may need additional config on the application end.

Get a cheap domain at like Cloudflare and use CNAME records that point domain.com and *.domain.com to your dyndns host. Iirc there’s also some routers/containers that can do ddns with Cloudflare directly, so that might be worth a quick check too.

Guess I’m a bit too young for that still lol. We got a pair of ISDN2 lines in 1994 (so technically also 256k lol) at home, but I was too young to remember that. With cable internet coming in 97, that was technically still slower than bonded isdn at the very start.

In a way I was very privileged growing up when it came to Internet. My dad’s company at the time paid good money to get all the latest (often testing phase) stuff to his house in return for being available 24/7.

Talking about Lan uplinks, in the early 2010’s I had the joy of working with a 20gb uplink at a small university LAN (the sysadmin got a good amount of free pizza and beers for that one). I spent a large amount of my savings on a 10gb NIC only to find out my hard drive couldn’t keep up lol.

There’s a couple SD-WAN solutions out there that you can do this with. Essentially route all your traffic through one or more VPSes while still keeping things like port forwards and STUN working properly.

I’ve had to use it to enable proper video feeds to and from people that had Spectrum as their ISP.

They’re called digital signage displays. Those module slots are usually in the intel SDM form factor.

This stuff is expensive as these displays and modules are rated for 24/7 operation and the software they ship with by default is specifically made to manage content on a large fleet of them.

You’re honestly gonna get a way better experience for cheaper by getting a normal TV + a NUC/Nvidia shield and just not connecting the TV to a network ever.

I definitely rely on documentation more than copilot, since I’ve noticed that the code it writes is only ever as good as your own codebase.

Most of the stuff I code is API wrappers to get arbitrary data into a format our broadcast graphics system can understand. Once all the data structures are properly defined copilot is extremely useful in populating all the API endpoints.

The actual problem solving is getting the data in the first place and morphing it into the correct format.

I’m very much a novice coder, but I often find myself doing the opposite. Write a good comment and let copilot write the actual code.

For some reason every registrars dns panel has its own weird restrictions, bugs and interface quirks. Pointing the nameservers to Cloudflare at least makes for a consistent experience.