it has a camera and microphone, so can you actually do video calls?

I don't think any of the T-Watches have cameras. But you're right about the meshtastic bandwidth, it's more for some simple messages.

So if the network isn't great here I assume I can put up my own node.

Yep, and a node is just another LoRa device, like the T-Watch. If it's just near your house, it should work great. My Wio Tracker L1 picks up a repeater on the other side my suburb, and that gives me some crazy range.

It doesn't sound like you do, but if you need intercity range, LoRaWAN might also be worth looking into. In Queensland, many city councils (Brisbane, Gold Coast, Moreton Bay) have their own LoRaWAN networks that peer with The Things Network, and you can integrate it with Home Assistant using an integration, or my preferred way is through MQTT. You would probably have to write the firmware yourself with this option though.

There's also no livepatches from Ubuntu Pro, and I thought this was the whole idea of livepatches, to patch critical bugs before you have a chance to update the kernel.

This also isn't the first time I've been annoyed at Ubuntu's response time. Luckily I mostly run Debian, but I certainly won't be using Ubuntu for anything else in the future.

I heard a theory that the horizontal stabilisers on the tail may not be there through.

AI; Didn't read. It's the AI version of tl;dr (too long; didn't read).

Well you can't sign new certs (with the current date) with an expired root/intermediate cert, but the root/intermediate cert expiring doesn't strictly invalidate the already signed certs.

But I was more talking about the end-user certificates in the previous comment.

Yeah, my understanding was they're not issuing new certificates, but the current ones are still valid until they've expired.

FYI, G3 is the only one listed with the issue, the others are fine AFAIK. But if you don't trust eMudhra at all after that, then that's fair.

Edit: Actually it's the intermediate certs that are compromised, the roots are still fine, but many of them come from the G3 root cert (and Sectigo's AAA Certificate Services)

Source: https://emudhra.we-have-a-problem.com/

Fluxer are also moving away from LiveKit, so hopefully that means it'll require less ports soon.

Actually yeah you're right. I reread the post and their point was it wasn't easily exploitable, not that it wasn't exploitable. Which makes sense when LiveOverflow wasn't able to bypass ASLR.

LiveOverflow kinda debunked this

I remember hearing that alkaline batteries that contain mercury don't leak, they're just much worse for the environment. So maybe that's what happened?

If you don't mind using alternative DNS servers, meaning this won't be accessible to the average person, you could try OpenNIC.

Unless there are vents underneath, you might also want to flip that power supply around, so the fan's on top.

I feel like me were talking about this just a few days ago, although the thread seems to have vanished.

Haha yeah, and I can still see the thread: https://aussie.zone/post/37468988

Also in python programming the pyautogui module only works with X11.

AFAIK XWayland is still supported, and pyautogui should work fine in XWayland.

Edit: Nevermind, thought it was some gui framework, it's more like xdotool.

As far as I know it's not even possible at all in Wayland to make mouse and keyboard automations.

You can, you just can't use the X11 tools, because it's not X11. Look into ydotool for a universal option, or there's kdotool for kwin.

Yeah, although Cockpit is a web UI thing, while systemd pilot looks like a proper GTK app.

Cloudflare, Inc., is an American technology company headquartered in San Francisco, California

https://en.wikipedia.org/wiki/Cloudflare

So it seems I was wrong about Cloudflare having seperate prefixes for WAF and workers. And these are all WAF/workers IPs (but not warp). My guess is that someone's made themselves a http proxy worker, and are using that to proxy their bot's requests.

KitKat managed to turn a stolen truck into a marketing campaign. I wouldn't be surprised if NVIDIA was trying to do the same thing.

What's the IPv4? I believe Cloudflare has different prefixes for WAF, warp, and workers.

2a06:98c0:3600::103 is definitely a Cloudflare WAF IP, so my guess is someone using either warp or workers is sending requests and added that IP to X-Forwarded-For as a red herring.