HN user

Mindless2112

1,808 karma
Posts20
Comments469
View on HN
arstechnica.com 2mo ago

Beijing bans drone sales even as rest of world buys Chinese drones

Mindless2112
7pts0
www.youtube.com 7mo ago

Mathematically extra-complicated Secretest Santa 2025 [video]

Mindless2112
6pts0
arstechnica.com 10mo ago

US uncovers 100k SIM cards that could have "shut down" NYC cell network

Mindless2112
2pts1
blog.accrescent.app 11mo ago

The Future of Accrescent

Mindless2112
3pts0
www.whitehouse.gov 2y ago

Completing the Transition to Internet Protocol Version 6 (IPv6) [pdf]

Mindless2112
2pts1
www.youtube.com 3y ago

Checksum and CRC Tutorial

Mindless2112
1pts0
www.washingtonpost.com 3y ago

Mexico scraps daylight saving time except along border

Mindless2112
3pts0
arstechnica.com 5y ago

China targets rare earth export curbs to hobble US defense industry

Mindless2112
5pts3
arstechnica.com 5y ago

Security firm Malwarebytes was infected by same hackers who hit SolarWinds

Mindless2112
1pts0
superuser.com 5y ago

What Firewall Rule(s) Will Allow Windows Update and Only Windows Update to Work

Mindless2112
2pts0
wiki.therofl98.co 6y ago

List of words text-to-speech engines can't say correctly

Mindless2112
18pts3
www.peterbalch.co.uk 6y ago

Peter Balch Shareware

Mindless2112
3pts0
www.sigidwiki.com 7y ago

Chinese Firedrake Jammer

Mindless2112
1pts0
github.com 7y ago

RetDec: An LLVM-based decompiler

Mindless2112
1pts0
arstechnica.com 7y ago

Great Google Hangouts Shutdown Begins October 2019

Mindless2112
4pts0
gizmodo.com 7y ago

The “Harvard Sentences” Secretly Shaped the Development of Audio Tech (2015)

Mindless2112
1pts0
digg.zendesk.com 8y ago

Goodbye to Digg Reader

Mindless2112
1pts1
arstechnica.com 10y ago

Linksys WRT routers won’t block open source firmware despite FCC rules

Mindless2112
3pts0
blog.regehr.org 10y ago

The Problem with Friendly C

Mindless2112
173pts173
play.google.com 11y ago

HP Prime Graphing Calculator

Mindless2112
1pts0

A fair point...

I thought the bug was a missing check for the COW flag, but looking at it again it seems it was missing both setting and checking the flag.

In CHERI, for example, pointers have permissions. The pointer to the COW memory would not have the "write" permission.

I could be misunderstanding the bug, of course.

The parameters in the original gpt-oss-20B model are "post-trained with MXFP4 quantization", so there just isn't much to gain by quantizing to Q8. If you look inside the Q8 model, most of the parameters are MXFP4 anyway.

Though, looking inside my "gpt-oss 20B MXFP4 MoE" model, it looks to also be quantized the same way as the Q8, so that was probably an overstatement on my part.

Still, the Q8 is 12.1 GB and the FP16 is 13.8 GB. Not the ~1:2 ratio you might expect.

As of b8966, it is still not great.

  | model                 |      size |  params | backend | ngl |   test |            t/s |
  | --------------------- | --------: | ------: | ------- | --: | -----: | -------------: |
  | gpt-oss 20B MXFP4 MoE | 11.27 GiB | 20.91 B | SYCL    | 999 | pp2048 |  851.81 ± 6.50 |
  | gpt-oss 20B MXFP4 MoE | 11.27 GiB | 20.91 B | SYCL    | 999 |  tg128 |   42.05 ± 1.99 |
  | gpt-oss 20B MXFP4 MoE | 11.27 GiB | 20.91 B | Vulkan  | 999 | pp2048 | 2022.28 ± 4.82 |
  | gpt-oss 20B MXFP4 MoE | 11.27 GiB | 20.91 B | Vulkan  | 999 |  tg128 |  114.15 ± 0.23 |
  | qwen35 27B Q6_K       | 23.87 GiB | 26.90 B | SYCL    | 999 | pp2048 |  299.93 ± 0.40 |
  | qwen35 27B Q6_K       | 23.87 GiB | 26.90 B | SYCL    | 999 |  tg128 |   14.58 ± 0.06 |
  | qwen35 27B Q6_K       | 23.87 GiB | 26.90 B | Vulkan  | 999 | pp2048 |  581.99 ± 0.86 |
  | qwen35 27B Q6_K       | 23.87 GiB | 26.90 B | Vulkan  | 999 |  tg128 |   10.64 ± 0.12 |
Edit: I've no idea why one would use gpt-oss-20b at Q8, but the result is basically the same:
  | model                 |      size |  params | backend | ngl |   test |            t/s |
  | --------------------- | --------: | ------: | ------- | --: | -----: | -------------: |
  | gpt-oss 20B Q8_0      | 11.27 GiB | 20.91 B | SYCL    | 999 | pp2048 |  854.16 ± 6.06 |
  | gpt-oss 20B Q8_0      | 11.27 GiB | 20.91 B | SYCL    | 999 |  tg128 |   44.02 ± 0.05 |
  | gpt-oss 20B Q8_0      | 11.27 GiB | 20.91 B | Vulkan  | 999 | pp2048 | 2022.24 ± 6.97 |
  | gpt-oss 20B Q8_0      | 11.27 GiB | 20.91 B | Vulkan  | 999 |  tg128 |  114.02 ± 0.13 |
Hopefully, support for the B70 will continue to improve. In retrospect, I probably should have bought a R9700 instead...

Compared to a B70, a 5090 is 1x the memory with 3x the bandwidth at 4x the price. Yeah, the 5090 is better, but you're paying for it.

Never buy another ebook from Amazon, sure.

Never buy another Kindle? I keep mine in airplane mode all the time and sideload all the books/papers I want to read. It works practically just as well as when I bought it. Why wouldn't I buy another? If Amazon makes a Kindle with color at 300 PPI, I will.

Sure, proper EPUB support would be nice, but if I need that I can jailbreak and install Koreader.

If there's another device with comparable hardware/software/battery, I'd consider it. AFAIK, Kindle still has the best standby battery life.

“The outbound and cross-bound DDoS attacks can be just as disruptive as the inbound stuff,” Dobbin said. “We’re now in a situation where ISPs are routinely seeing terabit-per-second plus outbound attacks from their networks that can cause operational problems.”

ISPs are starting to feel the pain, so perhaps in the near future they will do something about it.

The Freestyle Pro is almost a good keyboard. The Esc and function keys are all offset to the left by one key compared to a standard layout, which drove me nuts. I have a Freestyle Edge RGB now, which I like much better. (Though I replaced the wrist rests with some from Goldtouch.)

It seems like this could be easily solved in models that support tool calling by providing them with a tool that takes a token and returns the individual graphemes.

It doesn't seem valuable for the model to memorize the graphemes in each of its tokens.

When an optometrist chose to file a claim against my medical insurance (which did not pay) rather than my vision insurance (which would), the only way I was able to get them to fix it was by filing a complaint with the BBB. Multiple calls with customer service only resulted in "there is nothing we can do to change it", but somehow they figured out how to fix it when they got the BBB complaint letter.

How else can private citizens keep businesses honest? Complaining on the internet only works if you have lots of followers.

Interesting that traffic didn't return to completely normal levels after the incident.

I recently started using the "luci-app-https-dns-proxy" package on OpenWrt, which is preconfigured to use both Cloudflare and Google DNS, and since DoH was mostly unaffected, I didn't notice an outage. (Though if DoH had been affected, it presumably would have failed over to Google DNS anyway.)

Then you use the "lost my passkey" process, which should be the same as the "forgot my password" process. Most services should treat passkeys like unphishable passwords.

Passkeys do not (and are not intended to) solve the problem of lost credentials.