RCS has no end-to-end encryption in the standard, though. That's a non-standard google messages extension. I think a better example would be the cross-device messengers like signal/whatsapp/etc.
Google is slacking here and I hope Apple's involvement in RCS will help to move this forward. Samsung Messages also does not support Google's E2EE even though it supports RCS and pretty much all of the user-facing features Google Messages provides. Based on Google's whitepaper [1] about their E2EE support, I imagine it's because of the identity service they use for key exchange being centralized and internal (when really the identity service a contact uses should be an RCS capability in the extended contact system [RCS terminology here], and they should interoperate).
This article is so close to what I am asking about, but in the end it's once again about an unexpected increase in warming. Yet you can see that the information probably exists somewhere....
> ...analysed[sic] data on ship emissions as a model system for quantifying the climatic effect of human aerosol emissions in general.
This analysis could produce a whole set of factors and a relatively up-to-date numerical characterization of their impact. Some will be higher, but some may be lower (which also matters for planning!). Instead we get a report on a single factor that's most alarming.
Yes, it does. RCS without E2E is following the SMS model and putting your telco in charge. It uses transport encryption but that is basically meaningless when every relay sees the entire contents of the message.
RCS uses transport encryption and I honestly have no idea if it uses cert pinning or server certs or the like. The bigger concern to me is that it puts your telco in charge, just like the old days of SMS. Without E2E they get to see all of the contents of messages and to share it with whoever they deem they want to share it with, which history has shown is too many people. Telcos were very willing partners in the development of RCS for a reason. And there's a reason the base spec doesn't include E2E. Telcos want a return to the good old days.
SMS is insecure and no one should use it. RCS isn't that much better and history is a lesson that it returns to a partner that isn't trustworthy.
Yeah anything that's not E2E encrypted is pretty useless for privacy/security these days. Might as well just use DMs on reddit, twitter, etc if you don't care about E2E
Traffic restrictions are not part of the "15 minute city" initiatives. I think they are often confused because of Oxford's traffic filter scheme. As the article you link says, tying walkable city initiatives to one particular city's traffic scheme is indeed a conspiracy theory.
If you have valid criticisms of the traffic filter trial in Oxford then that's fair enough, although I imagine Oxonians won't be particularly interested in hearing it unless you're a local resident.
Notably it does bound the energy of gamma rays over long distances (as the higher the energy the more likely it will annihilate with other photons along the way.)
The wikipedia article on the Breit-Wheeler process has some history of the work on experimental observations, although I don't know how accurate or up to date it is https://en.wikipedia.org/wiki/Breit–Wheeler_process
The more recent 4 bit quantizations are almost along these lines. Q4_1 in ggml for example takes a block of 32 weights and gives each block a scaling factor 'd' and takes the minimum of the weights 'm' to be the quantized '0', so the final weights from a quantized weight 'q' is q * d + m, and taking a relatively small block size makes it more likely that those are all within a reasonable quantization range. Notably, d and m can be stored with more accuracy without sacrificing too much space, since the overhead is divided by 32. Q4_k goes a bit further, and takes 'superblocks' of 8 blocks, and applies another scaling factor 'd_s' and minimum 'm_s' to that, so the final weight is (q * d + m) * d_s + m_s, and the additional factors are stored as 6 bits instead of 4.
In practice this seems to get very good results, while being cheap to implement and relatively space efficient, Q4_K for example works out to 4.5 bits per weight instead of 4. The PR adding it has more details: https://github.com/ggerganov/llama.cpp/pull/1684
Very efficient for storage and memory bandwidth, but such a scheme is a headache for high throughput hardware implementations (at least compared to regular 4 bit math, which can be packed really really densely)
QEC implies phase error correction (if you don't care about phase errors you could just use a classical error correction code). A 'logical qubit' refers to an abstraction layer that implements some sort of idealized qubit behaviour (including the phase) that is used as a qubit in computation without considering the underlying implementation. The underlying implementation of a single logical qubit may be something like 5 'physical qubits' using https://en.wikipedia.org/wiki/Five-qubit_error_correcting_co... or a entire structure of many physical qubits using something like a https://en.wikipedia.org/wiki/Toric_code
You can run it on either now (for example, MochiDiffusion allows you to pick https://github.com/godly-devotion/MochiDiffusion#compute-uni...). Anecdotally, the GPU seems to be faster for an M1 Max or up GPU, the ANE is a touch faster on anything smaller, and more power efficient in general.
You neither need an app nor do you need to unlock your phone in order to use it for the ticket gates on the tube. Perhaps older phones need to be unlocked?
I use my phone exclusively without unlocking it and there's no delay.
