poizan42

My guess is that they are dynamically changing the quality of the model to always keep the speed above some floor. So once it gets below that they switch to a worse quant or reduce reasoning level, or some combination of both.

> A Home Office spokesperson said: “Over 10 million people have already successfully used eVisas to prove their immigration status. ..."

So how many people did not successfully use it? Could be 100 million for all we know. Do they think just throwing out a large number without anything to compare it to is somehow proving something?

It doesn't really explain much about its purpose. Is it better than libavcodec? I take it that the point is to re-use techniques from the h264 encoder for encoding MPEG-2 where applicable?

It's crazy, the last time any PRs got merged was back in January 2024 [0]. Seems it has just become a black hole completely ignored by anyone at framework.

[0] https://github.com/FrameworkComputer/EmbeddedController/pull...

I have used Opus 5 and some Fable 5 to finally get realtime transcoding of 4K 10-bit HEVC (to 1080p or smaller SDR AVC) working on a Raspberry Pi 4. It was very good at writing optimized NEON kernels. the Argon HEVC hardware decoder outputs SAND30 which is a tiled format that is annoying to work with and not really supported by anything else, the big performance issue has been with converting and scaling it, but as it turned out a lot of it was really with just moving memory around, so by fusing multiple steps into a single kernel it became fast enough. Experimenting with writing the NEON kernels for the different combinations would have taken forever by hand.

I do wonder if auto-research would have reached something similar, it did take a significant amount of steering from me to get it to the point where it was working realtime.

For anyone interested the ffmpeg is at https://github.com/poizan42/jellyfin-rpi-ffmpeg and a shim for using it with stock jellyfin at https://github.com/poizan42/jellyfin-rpi-ffmpeg-shim

The proper name for the calendar using the Gregorian system before the start of the Gregorian calendar is "the proleptic Gregorian calendar".

Nothing more complex than Hello world is easy to implement in C without risking mistakes in checking boundary conditions if you are not really careful.

Maybe there is something else in Gelidium amansii that it needs, if the tokoroten was produced in the traditional way?

Windows has its own library built-in: NLS. There have been a lot of back-and-forth about whether to use NLS or ICU in dotnet on Windows because it resulted in different behavior between Windows and other platforms. I think they ended up using ICU by default from .NET 5 on.

But wasn't the whole (claimed) reason that it got banned in the first place that it is a logical impossibility? Reviewing code for bugs is legitimate. Writing regression tests for bugs is legitimate. If the bug happens to be a security issue then the regression test may be a PoC or at least a step towards one.

m68knommu was merged into the mainline kernel in version 2.5.46: https://www.kernel.org/pub/linux/kernel/v2.5/ChangeLog-2.5.4...

Of course the 2.5 line was the unstable pre-release for the 2.6 kernel. That means that stable mainline linux has had nommu since 2.6.0, which was released 17 December 2003.

So yes, some time indeed.

> A statement that the information in the notification is accurate, and under penalty of perjury, that the complaining party is authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.

DMCA Section 3.A v) - https://www.law.cornell.edu/uscode/text/17/512

It is only the part about being authorized that is under the penalty of the perjury. You can be as malicious as you want as long as you don't falsely claim to own or represent someone who owns the rights to something.

I really wish they would have asked the representative to confirm that they can only share detailed information with the skeletal remains of an author who died 78 years ago. Not that I think it would make any difference, but it would force the representative to acknowledge the absurdity of the situation.

I have been trying to work on debugging tools using Opus 4.8. As it turns out working with low-level techniques that inspects and alters behavior of other processes is bordering close enough to cybersecurity research that it often hits the guardrails.

That's cool and all if you are writing GCC or Clang dialect C, but it doesn't change the fact that it is UB in the C standard.

It's not difficult not to lie to your customers. If you are actually selling a subscription then don't claim the customer is buying the game, and this law won't apply to you.

NTSYNC seems quite cumbersome to use for your own linux software though

> The ntsync driver creates a single char device /dev/ntsync. Each file description opened on the device represents a unique instance intended to back an individual NT virtual machine. Objects created by one ntsync instance may only be used with other objects created by the same instance.

So you need a server process that can open the char device and hold onto the fd that you can then request through a Unix domain socket.

They are GINA gaskets[0], they were supposed to last 120 years[1], but it has recently been shown that they may deteriorate faster than previously expected due to being under constant compression[2][3]

[0] https://www.trelleborg.com/en/marine-and-infrastructure/medi...

[1] https://www.trelleborg.com/marine-and-infrastructure/-/media...

[2] https://www.sciencedirect.com/science/article/abs/pii/S08867...

[3] https://dailygalaxy.com/2026/03/rubber-used-in-undersea-tunn...

And if you switch the tty from "cooked" to "raw" mode then it doesn't do the conversion, and a CR just moves the cursor back to the start of the line and a LF just moves the cursor one line down.

You can tell people what something is, that is nominative use of the trademark. Actually putting it in center of the branding might be infringing, but Don Ho gave their blessing to use that, so that point is moot anyways.

That was 11 years ago, under DHI Group though. I don't think Slashdot Media have been up to the same shady stuff.

Is the "genetic testing" for the presence of a Y chromosome or the presence of the SRY gene? And what about people with AIS?

If it's just karyotype, are men with XX male syndrome (SRY gene without an Y chromosome) then allowed to participate in women's sports?

They haven't pierced the corporate veil as far as I can tell - it's not moot or any other executives that have been personally fined. Also as far as I'm aware the UK doesn't have debtors jail.

See https://reddit.com/r/linux/comments/1rshc1f/i_traced_2_billi...

AutoModerator on /r/linux is set up to automatically remove posts after a set amount of reports.

Okay, but what does any of that have to do with knowing that the glyph at U+237C originated as a symbol for azimuth?

Hmm the comment was a bit difficult to parse, but I think they got it correct. Remember that we have arbitrarily defined the time during local winter as the "standard" time. If we want to keep to that then "permanent daylight savings" is a contradictory term. So what is actually meant is abolishing DST while at the same time changing the standard time to be at the offset of DST before the change. So what I think they are saying is that DST is being abolished, but the actual effective offset at the time when it's abolished is unchanged.

You might need several more dimensions (assuming this quoted claim is correct - it does come with a Citation Needed)

> Recent genetic analysis shows the papedas to be distributed among distinct branches of the Citrus phylogenetic tree, and hence Swingle's proposed subgenus is polyphyletic and not a valid taxonomic grouping, but the term persists as a common name.

According to wikipedia they are cultivated from a hybrid of mandarin orange and Ichang papeda, the latter being from another wild lineage than the three shown.

It sounds plausible, but they really need to spell out exactly what the formatting requirements are, because it can make a huge difference in how efficiently you can write the json out.

> The output should be encoded as a pretty JSON string.

So apparently that is what they consider "pretty JSON". I really don't want to see what they would consider "ugly JSON".

(I think the term they may have been looking for is "pretty-printed JSON" which implies something about the formatting rather than being a completely subjective term)