made you look
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.
I bet the actual logo display is a full screen browser too, multiple computers each running chrome just to display ads.
I would argue that a battery powered bike is closer to a dirt-bike/motorcycle/mini-bike and should probably be looked at the same as those.
I don’t really know if I’d consider this
A motorcycle.
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
tbf it was played straight in Hot Fuzz, Sgt. Angel was right and there was somebody who caused it.
Makes it portable across architectures while also providing sandboxing.
The fedi software I use (GoToSocial) runs both ffmpeg (Sorry, ffmpreg) and sqlite through WASM, also makes it easier to integrate it with Go code apparently.
There’s BlackSky now, the first full outside server setup (Things like relays and PDSs are just smaller components of the larger required stack)
So you know, they’re at 2 total instances currently.
Git itself (Or any other VCS for that matter) really should treat symlinks as special, similar as to how btrfs stores everything as “reflinks” internally. They be stored as special references to other tracked objects (so it’d be impossible to commit a symlink that pointed at anything other than a checked-in file, and ensure they always match), and git can materialise them as needed.
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.