Hmmm - interesting. I hadn’t bothered to check before now, but I’m seeing something similar on one of the two PBS CTs I run.

Comparing the output of netstat -lantop on both CTs, I can see that the one with more outbound traffic has more waiting connections from localhost on port 82, the port Proxmox Backup Servers provides its API over:

tcp        0      0 127.0.0.1:51562         127.0.0.1:82            TIME_WAIT   -                    timewait (40.38/0/0)
tcp        0      0 127.0.0.1:56342         127.0.0.1:82            TIME_WAIT   -                    timewait (29.92/0/0)
tcp        0      0 127.0.0.1:44864         127.0.0.1:82            TIME_WAIT   -                    timewait (58.94/0/0)
tcp        0      0 127.0.0.1:45028         127.0.0.1:82            TIME_WAIT   -                    timewait (11.88/0/0)
tcp        0      0 127.0.0.1:44026         127.0.0.1:82            TIME_WAIT   -                    timewait (48.66/0/0)
tcp        0      0 127.0.0.1:44852         127.0.0.1:82            TIME_WAIT   -                    timewait (58.80/0/0)
tcp        0      0 127.0.0.1:59620         127.0.0.1:82            TIME_WAIT   -                    timewait (0.00/0/0)
tcp        0      0 127.0.0.1:56374         127.0.0.1:82            TIME_WAIT   -                    timewait (30.98/0/0)
tcp        0      0 127.0.0.1:51544         127.0.0.1:82            TIME_WAIT   -                    timewait (39.98/0/0)
tcp        0      0 127.0.0.1:59642         127.0.0.1:82            TIME_WAIT   -                    timewait (0.00/0/0)
tcp        0      0 127.0.0.1:45008         127.0.0.1:82            TIME_WAIT   -                    timewait (10.92/0/0)
tcp        0      0 127.0.0.1:45016         127.0.0.1:82            TIME_WAIT   -                    timewait (11.76/0/0)

I’m wondering if the graph is pulling aggregated network data, including the loopback interface. If so, and it’s all just port 82 stuff on 127.0.0.1, then it’s probably nothing to worry about.

Edit: found this forum post that seems to indicate it’s aggregating all the byte values from /proc/dev/net, so this is probably nothing to worry about if your netstat output, like mine, only shows API conections to/from 127.0.0.1 on port 82.

Seriously - the whole thing is such a befuddling mess to us non-Americans.

How exactly can one win the popular vote but not the actual election? From the outside, the reporting I’ve seen always talks about the faithless elector problem (not in those words - just in describing the problems). Is it more to do with how many votes (electors) each state gets, based on population size?

Nah - it’s at least partly correct.

I believe the states responsible for those silly outcomes have since passed laws to prevent it happening again.

Could be wrong, but I listened to a podcast last week with an American professor who’s pretty much written the book, explaining the history of the Electoral College and how it really works. I’m sure he said those states since fixed those loopholes.

Either way, the damage is done today. Another four years of stupidity in charge.

Lol @ “some 20 years ago … ADSL from 2002”. Thanks for making me feel old!

Ah, no worries mate. Almost got excited for a minute there.

Are you sure? I went looking after I upgraded and I still only have Assist; Scripts; Actions; and Open Page.

Well, thanks for the fall down that particularly horrifying rabbit hole. I can only imagine the pain these women went through, given this was at a time that predates anaesthesia.

If your strategy as an employer is how to keep your people in indentured servitude, that makes you a cunt. Be a good boss - help your employees achieve their goals and get to the next step in their career. That will help you attract newer talent when you need it.

Oh, sure. I get that. Sending yourself reminders is absolutely understandable. Sending yourself documented evidence of your plans to defraud someone is entirely different.

I use Shortcuts with NFC tags to automate some stuff with HA, and could probably achieve something on an entity by entity basis.

My point is that we used to have the ability to put a widget on the screen with about 6 or 8 entities on it, for simple, single-click access. And now we don’t. Seems silly to have taken it away from us.

In a 2017 email to himself, Smith calculated that he could stream his songs 661,440 times daily, potentially earning $3,307.20 per day and up to $1.2 million annually.

Great idea, but why would you email yourself about it?

Maybe the cop lives there, decided to bring his work with him

Isn’t the picture from Logan?

Edit: oh, it’s called johntucker.jpg.

The casting bit is the missing piece for me.

I’ve built a RasPi with Kodi for our caravan, to use Plex and stream our free-to-air TV here in Australia (using Musk’s space innernets). I just miss being able to cast from my phone, for the occasional thing I can’t do with a Kodi add-on.

RAID5 and unlimited downloads on my 1Gbps fibre. All I backup is my library metadata itself, using a 2N+C strategy.

It possibly would, but I don’t have any Homekit devices, and I just feel hat this is a simple thing a home automation app should offer, it’s almost conspicuous by it’s removal/absence.

Yep, that’s it. One of my most frequent uses of this widget was to turn the kitchen light off - the teenagers are forever walking in to the kitchen while we’re watching TV in the loungeroom nearby, then forgetting to turn the light off when they leave again.

Having a quick access widget for it just made it such a non-issue for me to turn it off. No fumbling and swiping for the app, and no interrupting what we’re watching to issue a voice command.

Disappointing that, if this was a thing, they removed it. Seems like the very definition of regression to me.

At least I know I’m not imagining it. Or that I’m not the only one. ;) Cheers!

Nah - not a widget per light. Per my OP, I had a widget that had a number of lights on it. The number varies based on widget size. I think mine had about 12 entities on it.