There are pedagogical books (CF. 'Counterexamples in Topology', 'Counterexamples in Analysis') that teach the nuances of subjects through counterexamples. They're popular as it's sometimes easier to learn details from a pathology or degenerate example than from just learning what is intended.
Tangentially, I recall reading a paper not that long ago that showed that under certain assumptions that Zermelo's theorem showed that making the games 'quantum games' didn't actually offer any real advantage.
I've been trying to get access to CHERI for quite a while - I have a background in hardware security so was very curious to have a play. But only 'approved partners' are allowed to have access... guessing even in projects like this, Security through Obscurity still reigns.
Short and simple Chrome extension that reads the requests in a page looking for '.pdf'in URL or 'pdf' in MIME type, and then reads all the chunks and reassembles the file from the base64 provided by Chrome. Uses `Network.getResponseBody` to get the data - select a tab from the dropdown, go and reload the content (scroll all the way through if it's long), and it should find all the pieces, reassemble, and present them as a download.
Designed for getting a file out when you have to from a page that doesn't have a download button and has a CDN that you have to parse through all the chunks in order to acquire the file from raw requests.
EDIT - uses `chrome.debugger` API, so wont' work in Firefox without totally reworking it (but probably possible!)
Hard agree with this My fave workflow I did was making the first fully regulatory approved LLM workflow for a global retail bank, using GPT 3.5 in June 2023 on Azure early access. That stack is still the reference for a lot of the work we've done since and currently.
Cobbled together with Clanker Claude over a few weekends, based on work I was doing on the RAPTOR project for automated vulnerability finding. Based on the CHEESECLOTH by Cueller et al. from USENIX '23 - https://www.usenix.org/conference/usenixsecurity23/presentat...
With a lot of disclosure chatter going around like it's 2000-and-great, perhaps we can utilise the cryptography of ZKPs and tlock cryptography to disclose bugs; I can prove the bug works in a zkVM, without anyone knowing the details of the exploit except those who have the keys. Then you can timelock it to reveal after disclosure period, or not... your choice. Either way, we can assess the risk and determine important facts about an exploit without ever diclosing it until required.
Aim - to upgrade the conversation around disclosure. It's the future, let's act like we have more options.
I'm actually very impressed how many people are now playing with Zero Knowledge on HN... I put this out a week ago, and have seen many more popping up. Amazing!
So two parts to a reply - first is, you don't need the encryption per se, but you can add that in the case that you give it some key and then it's encrypted. I don't see the value unless you're using this to generate frames for a video, which isn't current functionality but totally doable.
Second part, Charlie Bennet said "the only entropy source is one you can trust" and the best entropy source is quantum fluctuations, so we built a fully open source phase diffusion QRNG at Quantum Village and released it. Link: https://github.com/QuantumVillage/EntropyLoop
There is a toggle where you can show what chunks have been received. This is also where the 'show specific chunk' function comes in... the receiver can see "oh, I'm only missing chunk 125, so just show me that" etc. etc.
This seems to get impressive results cross compiling models from torch (with vollo-torch) into FPGA friendly formats. Speedups look quite impressive...