This sounds similar to rumors about how SSD companies work. First they would design a new drive with better performance that everyone uses to benchmark against other models; then slowly change its parts to worse ones, either because they are cheaper, the originals are no longer available, or whatever reason
An interesting case is "WiFi", short for "wireless fidelity". "Fidélité sans fil" in French should be feminine, but every technical person says "le WiFi" (masculine) while many (most?) non-technical people intuitively say "la WiFi" (feminine).
If you keep your access point secure and in good working order, or if you can flash any firmware into OpenWRT... make sure to publicly credit your excellent "Wi-fu"
WiFi is not an acronym for "wireless fidelity"; the developers likely just thought it sounded cool. The term is probably just a play on the words from the audio term "high fidelity". The phrase "Wireless Fidelity" is meaningless.
> It is disputed whether the name Wi-Fi is short-form for 'Wireless Fidelity',[34] although the Wi-Fi Alliance did use the advertising slogan "The Standard for Wireless Fidelity" for a short time after the brand name was created,[31][35] referenced "the Wi-Fi (Wireless Fidelity) logo" in a white paper[33] and the Wi-Fi Alliance was also called the "Wireless Fidelity Alliance Inc." in some publications.[36] IEEE, a separate but related organization, has stated "WiFi is a short name for Wireless Fidelity" on their website.[37][38] The name Wi-Fi was partly chosen because it sounds similar to Hi-Fi, which consumers take to mean high fidelity or high quality. Interbrand hoped consumers would find the name catchy, and that they would assume this wireless protocol has high fidelity because of its name.[39]
So it’s not really safe to say it’s not meant to mean wireless fidelity, in fact it sounds pretty likely.
I haven’t looked into the history, but my understanding from the comments is that it exists to preserve `x == y -> hash(x) == hash(y)` for `x` and `y` with different numeric types (int, float, decimal) – which seems like it should be solvable, but isn’t a constraint I’d want to be working under, so I sympathize.
His inputs are large numbers that don't fit in a standard integer. Bigints. The set inclusion test not only has a hash lookup but an equality test, which will be a bigint comparision rather than integer comparison, and bitint comparison is itself O(n) based on the size of the bignum. And the code that tests each bignum is in the set also _sums_ those bignums, which itself is an O(n) operation based on the size of the bignums being summed.
So he's not testing dict/set performance, he's testing bignum performance, because of the inputs he deliberately chose
Thanks for flagging this. From what I can tell, it's Beehiiv's locale detection overriding my publication settings, nothing I can change but will file a support ticket with them.
DDoSing a website, modifying their archives surreptitiously to serve their own wants (which was what tipped Wikipedia towards banning their use), running weird sockpuppet campaigns to build dependence on them, and fucking with Cloudflare's DNS resolution to prevent anti-tracking measures from working.
Oh and even if I wanted to ignore all of this, I couldn't use them anyways because they blackholed the majority of Finnish IP ranges after the DDoS incident to I guess punish the entire country for the targeted blogger being born here.
All that tells us is that the site is probably not run by the FBI. It could still be run by the CIA, Russian intelligence, or some lone morally neutral guy from Prague
Because if he's being targeted by the feds, he obviously he doesn't want his private information being published by some guy who self-admittedly did it on a whim?
I'm not well-informed about this situation, but DDOSing does strike me as an action which is fundamentally counter to information freedom and archival, so that seems like a reasonable suspicion to me.
I would add it was also completely ineffective since the site in question was hosted on wordpress.com, which is about as likely to work as ddosing Google.
> If you live in Europe, this restriction may be considered "gatekeeping" and exempted by the Digital Markets Act.
That's not how the DMA works at all, there is no concept of gatekeeping practices. Instead, the EU Commission designates companies that act as gatekeeper for some services (current list here: https://digital-markets-act.ec.europa.eu/gatekeepers-portal_...) which then puts constraints on what they do.
reply