Why SSL was renamed to TLS in late 90s (2014)

Start your own Internet Resiliency Club

Working on databases from prison

Modifying an HDMI dummy plug's EDID using a Raspberry Pi

Childhood leukemia: how a deadly cancer became treatable

Jokes and Humour in the Public Android API

Nanonets-OCR-s – OCR model that transforms documents into structured markdown

Is gravity just entropy rising? Long-shot idea gets another look

Twin – A Textmode WINdow Environment

Hello,I would like to share a Rust implementation of the Zstandard seekable format I&#x27;ve been working on.Regular zstd compressed files consist of a single frame, meaning you have to start decompression at the beginning. The seekable format splits compressed data into a series of independent frames, each compressed individually, so that decompression of a section in the middle of an archive only requires zstd to decompress at most a frame&#x27;s worth of extra data, instead of the entire archive.I started working with the seekable format because I wanted to resume downloads of big zstd compressed files that are decompressed and written to disk on the fly. At first I created and used bindings to the C functions that are available upstream[1], however, I stumbled over the first segfault rather quickly (it&#x27;s now fixed) and found out that the functions only allow basic things. After looking closer at the upstream implementation, I noticed that is uses functions of the core API that are now deprecated and it doesn&#x27;t allow access to low-level (de)compression contexts. To me it looks like a PoC&#x2F;demo implementation that isn&#x27;t maintained the same way as the zstd core API, probably that&#x27;s also the reason it&#x27;s in the contrib directory.My use-case seemed to require a complete rewrite of the seekable format, so I decided to implement it from scratch in Rust using bindings to the advanced zstd compression API, available from zstd 1.4.0.The result is a single dependency library crate[2], and a CLI crate[3] for the seekable format that feels similar to the regular zstd tool.Any feedback is highly appreciated![1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;zstd&#x2F;tree&#x2F;dev&#x2F;contrib&#x2F;seekable_format">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;zstd&#x2F;tree&#x2F;dev&#x2F;contrib&#x2F;seekable_f...</a>
[2]: <a href="https:&#x2F;&#x2F;crates.io&#x2F;crates&#x2F;zeekstd" rel="nofollow">https:&#x2F;&#x2F;crates.io&#x2F;crates&#x2F;zeekstd</a>
[3]: <a href="https:&#x2F;&#x2F;github.com&#x2F;rorosen&#x2F;zeekstd&#x2F;tree&#x2F;main&#x2F;cli">https:&#x2F;&#x2F;github.com&#x2F;rorosen&#x2F;zeekstd&#x2F;tree&#x2F;main&#x2F;cli</a>

Show HN: Zeekstd – Rust Implementation of the ZSTD Seekable Format

Real-time CO2 monitoring without batteries or external power

Salesforce study finds LLM agents flunk CRM and confidentiality tests

Occurences of swearing in the Linux kernel source code over time

Solving LinkedIn Queens with APL

Benzene at 200

Object personification in autism: This paper will be sad if you don't read (2018)

Maya Blue: Unlocking the Mysteries of an Ancient Pigment

Darklang Goes Open Source

Hello HN,I built a Typescript library (named socket-call, for lack of a more sexy name) whose goal is to be able to call socket.io events as regular functions.So you declare your server-side like so:<pre><code> ...
 const listenEvents = (services: UserServices) =&gt; ({
 &#x2F;&#x2F; Add your events here, the name of the event is the name of the function
 login: async (username: string) =&gt; {
 services._socket.data.user = { username };
 console.log(`User ${username} logged in`);
 setInterval(() =&gt; {
 &#x2F;&#x2F; Calling an event that&#x27;s handled client-side
 services.showServerMessage(`You&#x27;re still logged in ${username}!`)
 }, 1000);
 return `You are now logged in ${username}!`;
 },
 });
</code></pre>
and then on the client side you call them like normal async Javascript functions (and you can also create client-side event handlers):<pre><code> ...
 const user = socket.addNamespace&lt;UserEmitEvents, UserListenEvents&gt;(
 &#x27;&#x2F;user&#x27;
 );
 
 &#x2F;&#x2F; Calling an event that&#x27;s declared server-side
 user.login(username.value).then((message) =&gt; {
 console.log(&#x27;Server acked with&#x27;, message);
 });
 
 &#x2F;&#x2F; Handling an event that is sent by the server
 user.showServerMessage = (message) =&gt; {
 console.log(&#x27;Server sent us the message&#x27;, message);
 }

</code></pre>
I use this library for my own projects and would be interested to receive feedback about it :-)

Show HN: Socket-call – Call socket.io events like normal JavaScript functions

Mathematical Illustrations: A Manual of Geometry and PostScript