...and accurate to the book, too.
When I read it for the first time, I was surprised by how much of a 19th-Century technothriller it was. In the book, Jonathan Harker has a Kodak camera. There are lots and lots of telegrams-- tweets. Most of the book was written as short epistles -- blog posts.
X wasn't banned in Brazil because of censorship. It was because Musk refused to abide by a court order to block accounts linked to the invasion of the Brazilian Parliament, Supreme Court and Presidential Palace in 2023. Musk preferred to close his Brazilian offices instead of helping to catch those who tried to overthrow a democratic elected government. If someone tells you otherwise, they're either dishonest or misinformed.
This reminds me of those old science videos we watched in middle. School when the teacher was hung over. #cybertruck
@leeb The IBM 1401 computer had optional support for math with pounds/shillings/pence in hardware, back when there were 12 pence in a shilling and 20 shillings in a pound. Of course there were two incompatible standards, so the computer had a knob on the front panel to select the standard.
Wireshark 4.4 dropped. Limits of new display filter features.
https://blog.wireshark.org/2024/08/whats-new-in-wireshark-4-4/
@dalias @rabbit That is an important aspect of a sustainable social media model. Scale must be understood as a mixed blessing that has costs which some communities have no capacity or desire to bear. Small is not a bad thing, as long as it suits the people who choose it. A federated system (which can include diverse platforms) lets sites choose to stay small or to try to manage getting big.
An SQL injection bug that lets you bypass airport security and even JUMP SEAT. Sure. This is great. I’m not having a heart attack or anything. TSA response is definitely also chef’s-kiss. *breathes into a paper bag* https://ian.sh/tsa
I think people really don't appreciate just how incomplete Linux kernel API docs are, and how Rust solves the problem.
I wrote a pile of Rust abstractions for various subsystems. For practically every single one, I had to read the C source code to understand how to its API.
Simply reading the function signature and associated doc comment (if any) or explicit docs (if you're lucky and they exist) almost never fully tells you how to safely use the API. Do you need to hold a lock? Does a ref counted arg transfer the ref or does it take its own ref?
When a callback is called are any locks held or do you need to acquire your own? What about free callbacks, are they special? What's the intended locking order? Are there special cases where some operations might take locks in some cases but not others?
Is a NULL argument allowed and valid usage, or not? What happens to reference counts in the error case? Is a returned ref counted pointer already incremented, or is it an implied borrow from a reference owned by a passed argument?
Is the return value always a valid pointer? Can it be NULL? Or maybe it's an ERR_PTR? Maybe both? What about pointers returned via indirect arguments, are those cleared to NULL on error or left alone? Is it valid to pass a NULL ** if you don't need that return pointer?
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess