Encountered my first ublock issue github.com/uBlockOrigin...
github.com
peakd.com: breakage · Issue #34668 · uBlockOrigin/uAssets
Prerequisites This is NOT a YouTube, Facebook, Twitch, Spotify or a shortener/hosting site report. These sites MUST be reported by clicking their respective links. I read and understand the policy ...
![Rung 10 ($32,000): question committed, refereeing...
POST https://api.typesafe.ai/v1/systemone <- 200 in 312ms (request req_)
referee accepted the question; Jev is answering...
POST https://api.typesafe.ai/v1/systemone <- 200 in 311ms (request req_)
POST https://api.typesafe.ai/v1/systemone <- 200 in 317ms (request req_)
Rung 10 ($32,000): In which month of 1985 was C++ first commercially released, with Cfront Release 1.0?
A. December
B. June
C. February
D. October
Host's note: Stroustrup, "A History of C++: 1979-1991" (HOPL-II) and stroustrup.com: Cfront Release E went out in February 1985; the first commercial release, 1.0, came in October 1985, together with the first edition of The C++ Programming Language.
Referee: accepted [Jev: well-formed 59%, needs 60%; claude:opus: key correct, only correct option, question fair, 90% sure, needs 70%]
Jev objected to the form; claude:opus found it fair, so it stands.
claude:opus says: Cfront Release 1.0, the first commercial C++ release, shipped in October 1985, as Stroustrup's HOPL history documents. February 1985 was the non-commercial 'Release E' distributed to universities, so it is a distractor, not a competing answer.
Jev (first look): leans D, confidence 26% [A 16% B 25% C 15% D 44%]
Jev walks away.
Jev walks away. The answer was D.
You answered wrong on rung 9 and leave with $1,000. Jev beats you.
Game over: Jev walked away with $16,000. [fouls 0]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:qcjmkxk5v4o33pd4z7na6wmw/bafkreif5hennuyi5kfwgtskintloe2gf442w22dt4shiydz3a6sqys3tfi)
![Algorithm 1 ICan’tBelieveItCanSort(A[1..n])
for i = 1 to n do
for j = 1 to n do
if A[i] < A[j] then
swap A[i] and A[j]
https://arxiv.org/pdf/2110.01111](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:qcjmkxk5v4o33pd4z7na6wmw/bafkreiatvawcvhqcksjn73il35c7elpbogpvon7q6rzusxq2nborptbfs4)
![$ curl -fsSL https://dl.example.dev/tool/install.sh | jevsh
jevsh: BLOCKED by classifier
{
"decision": "block",
"reasons": [
"reads_secrets (0.98)",
"exfiltrates (0.98)",
"malicious intent (0.98)",
"telemetry (0.95)",
"beyond_install (0.97)",
"mutable_refs (0.98)",
"severity 3.49",
"low severity confidence (0.59)"
],
"signals": { ... every question and its answer ... }
}
https://github.com/serpent7776/jevsh](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:qcjmkxk5v4o33pd4z7na6wmw/bafkreigj3pcblvbszuyvsfwgpiqzyaxaddypkzbla5jqcdh7xiuzrn4vli)
![Screenshot of an interactive Intel instruction visualizer for VPINSRB. It shows the syntax VPINSRB xmm1, xmm2, r32, imm8 and explains that one byte from src2 is inserted into a selected byte position of src1. In the example, imm8 = 0x02, so byte index 2 is selected. src1 contains bytes 0xA0 through 0xAF, while src2[0] is 0x1F. The destination row highlights byte 2 changing from 0xA2 to 0x1F; all other destination bytes remain unchanged. A bit diagram at the bottom shows the low four immediate bits as 0010, corresponding to selection index 2.
https://serpent7776.github.io/simdvis/pinsr.html#vpinsrb](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:qcjmkxk5v4o33pd4z7na6wmw/bafkreifzrsqff4zqeqx3f2fndfmlpiunnqm6b6ytvtxhomoowha4lkmaxi)
![Screenshot of an interactive Intel SIMD instruction visualizer for VPUNPCKLBW / PUNPCKLBW. It shows two 128-bit byte source vectors, src1 and src2, and a 128-bit destination vector. The instruction interleaves the low eight bytes of the two sources: each src1[i] is followed by src2[i]. Example values show src1 bytes starting at 0xA0 and src2 at 0x10, producing destination bytes 0xA0, 0x10, 0xA1, 0x11, …, 0xA7, 0x17. The first source byte and second source byte are highlighted, with arrows pointing to their corresponding destination positions.
https://serpent7776.github.io/simdvis/punpckl.html#punpcklbw](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:qcjmkxk5v4o33pd4z7na6wmw/bafkreifqpatno6d74unmikl3ncjgzebntr5ypfzjy2hijlukwkn6c72yce)
![export-subst
If the attribute export-subst is set for a file then Git will expand several placeholders when adding this file to an archive. The expansion depends on the availability of a commit ID, i.e., if git-archive[1] has been given a tree instead of a commit or a tag then no replacement will be done. The placeholders are the same as those for the option --pretty=format: of git-log[1], except that they need to be wrapped like this: $Format:PLACEHOLDERS$ in the file. E.g. the string $Format:%H$ will be replaced by the commit hash. However, only one %(describe) placeholder is expanded per archive to avoid denial-of-service attacks.
https://git-scm.com/docs/gitattributes](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:qcjmkxk5v4o33pd4z7na6wmw/bafkreid7jczsovw4q62jynicwxblxwk7dfb63ofwrhqhndswhb3craclcu)
![Screenshot of an interactive visualization explaining the AVX2 VPMOVMSKB instruction. The interface shows a 256-bit YMM register split into 32 color-coded bytes (src), with each byte displayed in hexadecimal and binary. Green boxes below indicate the extracted most significant bit (sign bit) from each byte, forming a 32-bit mask in register r32. Arrows connect source bytes to their corresponding output bits. The example result is r32 = 0x17D4EA0B, with accompanying text stating that 16 of the 32 sign bits are set and TZCNT = 0, indicating the first byte with its sign bit set is src[0]. Control buttons for editing byte values (0x00, 0xFF, alt, rand, 00/FF) appear in the upper-right.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:qcjmkxk5v4o33pd4z7na6wmw/bafkreid6f5ybq7is2mgxnbbt5itlqotomuu33aqihq3xwsl6npuqx6z3m4)
