The_Decryptor

It could also have been going through musth, can cause a 180 in behaviour and make perfectly friendly elephants suddenly extremely aggressive.

The driver crossed onto the wrong side of the road and mounted the footpath, there’s something else going on with them.

Can do it with the compose key if you’re on *nix, and here’s an implementation for Windows.

<compose> + e + ^ = ê, and <compose> + shift + E + " = Ë, etc.

I’ve never used 6rd, but I did use 6to4 for a while (A long time ago) and I got a GUA from that. 6rd is closely related to 6to4 so I naïvely expect them to work similarly?

Now I did it all with OpenWRT, but the gist was you set the tunnel information on the WAN side in the webui, and it produced the configuration for the LAN side. Since it’s a tunnel you never actually set any of the v6 details on the actual WAN adapter, outside of routing (i.e. what v4 endpoint do you send stuff to).

Well she was hidden under a lot of CGI.

I think it’s mostly maintenance issues, the maintainers being employees of the company that originally wrote and donated the driver, so there’s been a backlog of bugs that have sat unfixed.

This new driver on the other hand builds off the preexisting kernel support for NTFS, and the maintainer seems better equipped to respond to bugs in a timely manner.

“I’d like to plead insanity. I think the charge is insane. Anyone who takes it seriously could be such as well.”

“I don’t think I’m insane. I think the law is insane,” Dowling said.

I’m not sure it’ll go well for him, but I wish him luck, and I wish he had a proper lawyer.

Yeah, I bet it’s something to do with a video decoder trying to decode empty data (dropped or corrupted frame, etc.), and the result of that being converted from YCbCr to RGB, it’s too consistent of a failure case.

That’s old school hardware overlays, haven’t really been a thing since XP era Windows.

These days everything is a scene graph with normal texture buffers, and the compositor is responsible for either layering stuff over it or doing direct scanout of that surface.

Ok, but who is making those “open weight” models though? Individuals don’t really have the resources to run these huge scraping operations, so they’re often still corporate releases with fake open source branding.

To me lying implies an intent to deceive, LLMs can’t do that as they have no intentions or understanding of the output they produce.

It’s not lying, because it’s also not telling the truth either, it’s just statistically weighted noise.

Nah, storage is fried.

People always focus on systemd whenever this is posted, but all systemd is saying is that it can’t read the service files when it tries to start something. Earlier on the kernel is complaining about I/O errors as well.

That was Ars Technica.

I bet the actual logo display is a full screen browser too, multiple computers each running chrome just to display ads.

By claiming that you own patents on technology used by said format.

The “open royalty free” aspect applies to companies that are a part of the AOMedia group, if you’re not involved with them you’re not covered by the patent grants and restrictions in place, and can charge whatever the courts say is cool.

Depending on the output device it’s still using ALSA underneath (e.g. Bluetooth output instead is given to the BT stack), PipeWire is dealing with managing and routing the audio output rather than actually performing it.

The best part of the article is the very end, even if the site makes it look unrelated.

Avanci’s Video pool and Access Advance’s Video Distribution Patent pool are both now seeking content royalties from streaming services for the use of HEVC, VVC, VP9, and AV1. Access Advance’s rates are capped at roughly $63 million per year, and Avanci has published rates of 1.6% to 2.0% of revenue or $0.12 to $0.15 per user per month.

$4.5 million max for H.264 is rookie numbers vs. the $63 million max for AV1

There were also compatibility issues with the “CSS box model”, where IE6 didn’t follow the spec at all and broke nearly every site in every other browser because elements ended up with different sizes.

They fixed that with IE7, and we finally entered the utopia CSS promised with every browser agreeing on how to size elements.

And then everybody realised the CSS defaults were wrong, and the IE6 behaviour actually made more sense, and now pretty much any complicated site will opt back into the IE6 box model.

Yeah, we have mDNS for a reason.

Or even just link the DHCPv6 server to the DNS, that’s the default config in most cases anyway.