Can you imagine the US Treasury saying "Um, we made a deal with Blackrock and they bought all our treasuries. It's an exclusive deal and we're not letting anyone else buy treasuries now. Oh and p.s. the price is secret."
Thanks for your interest. If you have any advice on other instructions or M1 optimizations, I'd love to hear.
My first thought is to synchronize effort of the 8 CPU and maybe even the 8 GPU. That's +12dB right there. We have a multithreaded implementation in the project already.
If you want to achieve something similar to _mm_stream_xxx, ie. bypassing the caches and causing bursts of DRAM traffic, try making some uncached/write combined memory mappings and writing to them. I don't know how this can be done in user space. You could try creating memory mapped buffers with OpenGL or Metal, with certain arguments you could get an uncached mapping.
Another option is looking at ARM instructions for memory barriers and cache flushes. ARM's selection of instructions for dealing with caches is much richer than x86's.
Just chiming in to note that "1) if your air-gapped computer has malware that can do this, you've already lost" is a problem specific to this implementation.
Other implementations exist (related work, not in 2.4G band) where it is not necessary to install malware to make measurable transmissions.
For example (shilling) https://fulldecent.github.io/system-bus-radio/ allows to broadcast just by loading a web page. And, importantly, this is an attack vector that is reasonable to execute offline (i.e. connected to a local network with HTTP services, but not the internet).
Here is what people mean when we say we don't like Section 230. And we mean it whether or not Section 230 is actually responsible.
- Advertiser uses our trademark on Google Ads? Google makes money and has editorial control. But we can't sue them.
- Somebody posts something libelous about us on Twitter? Twitter makes serious money and has editorial control. But we can't sue them.
- Fakes on eBay? Can't stop them. eBay not liable.
If Twitter is going to have a "fact checking" department, then they also need a "retractions" department. And if retraction aren't forthcoming when reasonable, then we need a cause of action against them.
Can you imagine the US Treasury saying "Um, we made a deal with Blackrock and they bought all our treasuries. It's an exclusive deal and we're not letting anyone else buy treasuries now. Oh and p.s. the price is secret."