AI models produced from copyrighted training data should need a license from the copyright holder to train using their data. This means most of the wild west land grab that is going on will not be legal. In general I'm not a huge fan of the current state of copyright at all, but that would put it on an even business footing with everything else.

I've got no idea how to fix the screeds of slop that is polluting search of all kinds now. These sorts of problems ( along the lines of email spam ) seem to be absurdly hard to fix outside of walled gardens.

In New Zealand it is pretty common for members of parliament to get thrown out of the chamber for a whole bunch of reasons. In general you have to do whatever the speaker says, sort of like you would a judge in a court proceeding. There's a whole lot ( perhaps dated ) rules around treating other members of the house with respect, letting them speak when their part of the process is up etc.

I think most of this is covered by this list of rules: https://www.parliament.nz/en/pb/parliamentary-rules/standing-orders-2017-by-chapter/chapter-3-general-procedures/

Another trick big box retail can pull is when you make a big enough order with some well known brands you can have them sell it with a custom part number, so you when folks try and price match it you can say 'nope, not the same'.

This video is perfectly applicable, the rot that sets in in a large company when you have no competition to counteract it is exactly what has happened here.

Most hubs didn't protect you from anything in particular.

Most of them would forward everything to every port, some really insane ones would strip out the spanning tree that could have prevented a loop.

It's been a long time since I did anything that goes as far into a network as the desktop, but 15+ years ago we had a customer ring up with the same sort of complaint. After we followed the breadcrumbs on site we found a little 8 port hub ( that we hadn't supplied ) plugged into two wall ports that went to two different Cisco edge switches in the server room, two cisco phones also with their passthrough ports both patched into same switch and then two desktop PC's.

Amazing.

The most impressed I've been with hardware encoding and decoding is with the built in graphics on my little NUC.

I'm using a NUC10i5FNH which was only barely able to transcode one vaguely decent bitrate stream in software. It looked like passing the hardware transcoding through to a VM was too messy for me so I decided to reinstall linux straight on the hardware.

The hardware encoding and decoding performance was absolutely amazing. I must have opened up about 20 jellyfin windows that were transcoding before I gave up trying and called it good enough. I only really need about 4 maximum.

The graphics on the 10th generation NUC's is the same sort of thing that is on the 9th gen and 10th gen desktop cpu's, so if you have and intel cpu with onboard graphics give it a try.

It's way less trouble than the last time I built a similar setup with NVidia. I haven't tried a Radeon card yet, but the jellyfin docs are a bit more negative about AMD.

It might help for the folks here to know which brand and model of SSDs you have, what sort of sata controllers the sata ones are plugged into and what sort of cpu and motherboard the nvme one is connected to.

What I can say is Ubuntu 22.04 doesn't have some mystery problem with SSDs. I work in a place where we have in the order of 100 Ubuntu 22.04 installs running with SSDs, all either older intel ones or newer samsung ones. They go great.

I learned what a tankie is, which is fun.

I've been commenting a bit, whereas on reddit I would only post a comment a few times a year when I could be bothered dealing with the likely burst of negativity that would come as a response to it.

Kind of feels a bit more like Web 1.9 or so from about 2003 which I think was about the sweet spot for minimal rage bait and crazy and still a decent bit of user interaction and scale.

It would be about perfect if you could chop out a few of the folks trying to shoehorn in politics to every little thing.

My day job is building ISP networks. It's been about 20 years since I had a home connection that I didn't configure up both ends of myself.

I've got a 1G / 500M tail into home where I am right now, not that that is particularly impressive. One of the jobs I've been putting off at work is standardising our usage of the 10G GPON platform available here in NZ, when I do that I'll get one of the >1G tails to use at home.

Usually the answer is how ever much I can be bothered building, but my usage is pretty low.

Sorry to hear about that mess.

I posted here https://lemmy.nz/comment/1784981 a while back about what I went through with the Nvidia driver on Linux.

From what I can tell, people who think Linux works fine on Nvidia probably only have one monitor or maybe two that happen to be the same model ( with unique EDID serials FWIW ). My experience with a whole bunch of mixed monitors / refresh rates was absolutely awful.

If you happen to give it another go, get yourself an AMD card, perhaps you can carry on using the Nvidia card for the language modelling, just don't plug your monitors into it.

I had a Brother black and white laser (I think a HL1240?) for almost 10 years and then we started having to print a ton of education related stuff for our kid and colour made sense, so I got the closest thing that I could to the colour one that I use at work which ended up being a DCPL3551CDW.

Printing a little in Windows and Linux, but more often from apps on my Android phone and my partners iPhone.

I absolutely hate printers, but they have been fine.

Steam can do pretty well filling a tail circuit, probably better on average. But a torrent of a large file with a ton of peers when your client has the port forward back into the client absolutely puts more pressure on a tail circuit. More flows makes the shaping work harder.

Sometimes we see an outlier in our reporting and it's not obvious if a customer has a torrent or a DDoS directed at them for the first few minutes.