Uhh, this might be true for WebRTC, except not much uses WebRTC other than for realtime streaming/calling. Jellyfin for example is just an mp4 stream over http; and http(s) will only use the IP in the DNS record. I'd like to see a packet capture if you are certain something is switching IP.
SteveTech
I’m pretty sure QWERTY telegraph keyboards post-date typewriters.
Yeah they do! Actually a Japanese research paper (and this video) also theorises that they also grouped similar sounding letters in American Morse Code together (e.g. Z ∙ ∙ ∙ ∙
& SE ∙ ∙ ∙ ∙
, or C ∙ ∙ ∙
& S ∙ ∙ ∙
)
No worries! I believe there is a way to install desktop extensions on Android Firefox, but I'm not sure if it'll work.
Yeah, YunoHost explains why http://localhost:8536/
wouldn't be working. If cloudflared and Lemmy are in separate containers you have to put an actual IP in, since localhost points to the container itself.
How are you accessing it without Cloudflare? How do you know that Lemmy is actually listening?
What's the URL you using to access it without Cloudflare?
Edit: Also that curl tells me it's not listening on that IP/port.
Can you access it without Cloudflare?
Does curl http://localhost:8536/
work?
You are using cloudflared right? Because normal (non-cloudflared) Cloudflare doesn't support port 8536.
With dynamic DNS? Yeah it always has, as long as you can host a http server.
With a dynamic IP? It should do, the certs are only valid for 6 days for that reason.
I know this seems pretty much solved, but I just wanted to point out:
Frigate doesn't need a TPU, OpenVINO is quite performant even on decade old Haswells, or if you've got a GTX 750 or higher you might be able to use that as well.
Oh okay, I had assumed compiling would be a bit more I/O bound, while gaming would be a bit more CPU bound, but I guess you're right about the benchmarks!
Cert pinning is pretty uncommon in the self hosting community though, especially when both Cloudflare and Let's Encrypt have a 90 day validity period and often renews after 60 days.