egberts1

CVE bugs should always include the Linux kernel build configuration.

Ya know, such as CONFIG_BLUETOOTH, CONFIG_NAT, as applicable.

Makes decision making so much easier.

Eh, still have to login.

UK is doing it wrong.

They would get their best arrest rate with a microphone or printed words.

Camera? We just released a terrorist team spotted by an eyewitness.

/very sarcastcally, sardonically, and facetiously

Should be enough to get a broad socioeconomic category out of that.

Or is public health hiding that too?

Hence my multi-decade long zeal to ban JavaScript ... in web browser.

Then don't worry about it.

Your CPU is obviously able to handle your purportedly high-transactional workload ... until it doesn't.

Thank you, very much so.

Precisely.

Fix the browser.

Thanks, I needed that!

In NextSTEP 3, it was zoned-based allocation.

Rhapsody and early MacOS X, Darwin also used zone-based

Early iPhone also zone-based.

Later MacOS X implemented scalable zone, magazine allocator.

iPhone 12+ then went Nano allocator, ScalableZone + large/VM allocator

Latest iOS/iPadOS use Nano2

Zeow! Citation galore! Gotta RAG them into my LLM!

And then THeIR citations too!

Thank you very much!

Thank you for the insightful aspect. This too should be in the lore of memory allocations as well

Will research that, citations and all

Lfmalloc? Humalloc?

I am intrigued.

Is there a source for them?

D. S. Hirschberg, A Class of Dynamic Memory Allocation, CACM 16(10) 1973 covered this variants of halving Buddy Allocator.

Invariably so but I'm mulling over malloc()s on embedded topic now.

It keeps certain web scrapers and inline transparent proxies/IDS/XNS from fetching, 100%

Certain browsers will suffer. Meh.

A great idea for another article. A focus, on embedded and malloc()

I do do have a malloc() benchmark but it is in bad shape and directories have not coalesce nicely yet, tor a single run or a menu-driven one.

Thank you for the critique.

Compilations are hard to get 100% right.

Thank you.

I got tired of reading AI prose so I compiled and wrote it from my collections of others' whitepapers.

As a "For Reference Only", at the very least, for me.

As usual, anyone is welcome to improve upon it under CC BY-NC-SA.

Yes

No

Long list of services, 1,200 lawyers

https://www.faegredrinker.com/en/services/services

One only need to brush up on John Stuart Mill and his "On Liberty (1859).

He wrote about individual liberty (before SCOTUS Chief Warren and Brandeis branded the word "privacy" in their 1890 "Rights to Privacy".

He should have been one of the Founding Fathers.

Ditto.

Moment we create software liability and enforce them, is that moment AI will ship-up or shape-out )I know it's backward(.

Courtesy link for HN readers

https://www.rfc-editor.org/info/rfc9539/

Once again, private equity ruined another fine company ... with incessant advertisements

Electro-mechanical gyroscope

Limitation of LLM for and toward reverse engineering; it's the LLM innate error of forgetting states thru agentic recursion by overflow of context or prior premises being optimized away due to not using ternary-state (uninit/written/read) memory state.

Once again, on LLM being: a digital librarian, at its finest; logic a logic analyst, not so much.

LIES!

We all know 20% more also means take 20% off gets us the exact same value.

NEXT!

No? Isn't that the beauty of gullibility?

I think of tokens as fractional digital librarians.

None of the analyTical.