

It’s literally called “IPv6 privacy extension”. It’s what it does.
Unless you’re in the middle and fowarding the packets, you won’t stumble across a connectable IPv6 endpoint.


It’s literally called “IPv6 privacy extension”. It’s what it does.
Unless you’re in the middle and fowarding the packets, you won’t stumble across a connectable IPv6 endpoint.


The smallest possible subnet has 18.4 quintillion addresses.
You can’t scan it before encountering the heat death of the universe.
Outgoing connections are made on a different address that does not accept incoming connections. You never disclose your real IP when browsing.
So, no. It can’t be done.


They’re portscanning bots.
I made SSH IPv6-only and it stopped. You can’t scan IPv6 space for open ports.


AI is “taking credit for the work of humans” all the way down.


I’m old enough to understand this reference.


Installed it this week on an old PC. It really is unusable at this point.


Fun fact: Australia’s youth social media ban was lobbied by crooked betting agencies so that they could run ads without restriction.


Interesting. I’m getting full marks on mxtoolbox but failing the same tests on this one.


We almost had to mention standard cars, which are also half the size.


They didn’t look all that advanced…


Way to stand up to the man!


I wonder if anyone ever wrote an update aggregator that would find all package managers, containers and git repos and whatnot and just do all of them.
Some are a right pain to update, such as Nextcloud. Installing a monthly update should not feel like an enterprise prod deployment.
It’s kinda ironic that package managers have caused the exact problem that they are supposed to solve.


So, ChatGPT can’t match any function of a Casio wristwatch. I’m concerned that when it can, it will consume the power of microwaving a turkey just to tell a user what time it is.


Ahh. That’s usually among the red stuff in dmesg. I glad to hear you solved it, but a failing hard drive is a pricey thing to endure these days.


This is no different to the meta pixel localhost listener exploit.


This is absurd. They know we can go all the way to the root servers, don’t they?


Just start listening to dubstep and you’ll stop noticing 😆.
Maybe run lm-sensors and make sure the CPU/GPU isn’t being thermothrottled? I’d usually look at dmesg and look for red stuff. Any hardware issues are usually pretty obvious.
Try other apps. If you youtube or VLC behaves the same, the problem may be outside of jellyfin. If not, it narrows it down.
If could even be the server not being able to transcode in realtime. Try watching a file known to already be in a suitable format. It should direct stream and be much less load on the server. I’ve seen server encode CPU saturation and it does kinda look the same as client decode stutter. If it’s the server, you’ll probably see the same stutter from another device such as a phone.


There’s a “minimal” install that gives you a bare desktop. The only thing I would consider bloatware is snapd.


Agreed. It’s an uphill optimization battle. We’re now in a world where you need 6GB RAM to chat on Discord while scrolling Facebook.
Ubuntu and its apps (particularly Firefox) are incredibly efficient and respects your hardware resources. I can write a web page with a 5MB RAM footprint. It’s when you open the New York Times that your swapfile gets face-slapped.
Funnily enough, an Ubuntu server will run on a half-eaten potato. I’ve got 16GB in mine, and I’m running servers for LAMP (Nextcloud and Wordpress), NTP, Samba, Mail, Jellyfin, tor, XMPP, CUPS and a few other things. It typically uses around 2GB at idle.
Turn the tap off. Ask questions later. Stress test their data centre.
It’s absurd that they think they can just pay for the water they stole and call it square.