Not to say I agree with that comment. But I think the case for why ECC would be easier to break than RSA using quantum computing is that key sizes of ECC are much smaller so would require less qbits to break.
You can break a 160 bit EC with a 1000 qubit quantum machine. An equivalent 1024 RSA bit key needs about 2000 qbuits. (The following paper has a cool table and formula for working out how many you need for each)
My incredulity is in the idea that Google and the NSA apparently have 1000 qubit machines that can do that, but not 2000 qubit ones (and you should be very confident that will remain the case in future).
Note that once you're at the "I have a stable 1000 qubit machine that can perform complex calculations" realm, you can consider doing things like entangling it with that other 1000 qubit machine you have lying around, bringing yourself rapidly into the 2000 qubit realm. Getting to the first part is really hard. If you can pull that off, you're probably only a few years away from the second. The main thing that's stopping us from doing that today is that the (physcial) qubits we've made so far aren't stable enough; getting to a single logical qubit is anticipated to take 1000 physical ones.
The few thousands qubits that you mentioned is logical qubits. With error correction you need tens of millions of physical qubits to break RSA or ECC.
Google and NSA can produce more of the same thing. But they probably have no major secret sauce for things such as error correction that the public does not have.
Seems to have a bit. Cut and paste from the guy who set up \"><SCRIPT SRC=MJT.XSS.HT></SCRIPT> LTD
...
>I am in the process of contacting every website that has triggered my script which has a readily available contact for submitting security issues, or a hackerone account or similar. Alas, the sort of websites that have XSS problems rarely list IT security contacts.
The authority section (which contains the host domain) must begin with "//" whether there's a scheme prefix or not. Otherwise it's just part of the path (or query or fragment). IIRC, these semantics are also fixed by HTML such that any attribute like HREF or SRC is parsed as-if using the canonical regex (but after entity substitution and whitespace trimming). Browsers might have implemented this differently many years ago, but I doubt it as it would conflict with being able to use a bare path atom (e.g. foo.html).
[1] I normally eschew using regular expressions for proper parsing, but for URLs the canonical expression is both adequate and advisable for correctness.
Can U suggest a feature that I’ve been looking for in a TODO app for a long time. Tasks that are periodic but not urgent. Like changing the filters on your heating system every 6 months, adding fertilizer to the garden every 3 months, etc. Then when you have some time to spare you can easily see these kinds of tasks that you normally forget.
I assumed this was a common feature, but I just use Google Assistant to do this. "Remind me to change my filters every 6 months at 10 AM."
I think my longest term reminder is for renewing my secondary citizenship passport (~10 years I think), though I do have this backed up with a Google Calendar event just in case.
My problem with this kind of calendar reminder is, if I don't act on it immediately, it's gone forever and I notice it, at best, next time it's "time" to change the furnace filter.
It would be super helpful to me to have a calendar reminder that succinctly said "you said you wanted to do this every 6 months, and now it's 23 days overdue" (and then when I finally do the thing, schedule the next one for 6 months after that day, not 6 months after I was supposed to do it in the first place).
Various "habit tracker" apps do this pretty well, but they don't fit in with my calendar.
> "you said you wanted to do this every 6 months, and now it's 23 days overdue" (and then when I finally do the thing, schedule the next one for 6 months after that day, not 6 months after I was supposed to do it in the first place).
org-mode with its agenda does this beautifully. But then that only really runs in emacs.
This gets close but I don’t think it will then allow you to easily see which of these periodic tasks you can work when you have a few hours to spare today.
Yeah, that's fair, I usually don't look at them in a list. I know they show up in Google Calendar, so maybe you can view them their? Regardless, this is a great idea for a Todo app feature.
I use Due on iOS for this, it will also nag you on a given interval until you complete the action. OmniFocus also supports recurring actions, but IMO not as elegantly as Due.
