When UPS charged me a $684 tariff on $355 of vintage computer parts
oldvcr.blogspot.com
Our investigation into the suspicious pressure on Archive.today
adguard-dns.io
libwifi: an 802.11 frame parsing and generation library written in C
libwifi.so
Show HN: Unflip – a puzzle game about XOR patterns of squares
unflipgame.com
When did people favor composition over inheritance?
sicpers.info
Transgenerational Epigenetic Inheritance: the story of learned avoidance
elifesciences.org
Things that aren't doing the thing
strangestloop.io
Boa: A standard-conforming embeddable JavaScript engine written in Rust
github.com
Archimedes – A Python toolkit for hardware engineering
pinetreelabs.github.io
JVM exceptions are weird: a decompiler perspective
purplesyringa.moe
Show HN: I made a better DOM morphing algorithm
joel.drapper.me
Linux on the Fujitsu Lifebook U729
borretti.me
AMD continues to chip away at Intel's x86 market share
tomshardware.com
Weighting an average to minimize variance
johndcook.com
TCP, the workhorse of the internet
cefboud.com
Feature Extraction with KNN
davpinto.github.io
Nevada Governor's office covered up Boring Co safety violations
fortune.com
Messing with scraper bots
herman.bearblog.dev
Trellis AI (YC W24) Is Hiring: Streamline access to life-saving therapies
ycombinator.com
Windhawk Windows classic theme mod for Windows 11
windhawk.net
A new Google model is nearly perfect on automated handwriting recognition
generativehistory.substack.com
The Nature of the Beast: Charles Le Brun's Human-Animal Hybrids (1806)
publicdomainreview.org
Nice.
> int ret = libwifi_get_wifi_frame(&frame, data, data_len, got_radiotap);
> ...
> int ret = libwifi_parse_beacon(&bss, &frame);
I haven't looked into the implementation, but if I understand correctly, the above code (extracted from the example on the home page) implies that the unparsed segment of `data` is either (1) copied into `frame` or (2) a pointer-span in `frame` references the unparsed segment of `data`. I wonder why either of these approaches have been taken. I imagine that the pointer-span could be computed (possibly even statically) inside `libwifi_parse_beacon` and `data` could also be passed:
> libwifi_parse_beacon(&bss, &frame, data);
This would shrink the size of `frame` and achieve zero-copy. Or perhaps I'm missing something.