Thus, a construct like hash(key + message) can be used similar to SHA3 [1]
3,789 karma · joined December 9, 2009
Thus, a construct like hash(key + message) can be used similar to SHA3 [1]
(I suspect this would be a good compromise for git, since so much tooling assumes a 160 bit hash, and yet we don't want to continue using SHA1)
If you buy a pre-2021 Tesla with a round steering wheel, it can mostly function as a normal car.
Ferraris probably aren’t know for having sufficient cup holders.
That seems quite implausible. Not that the managers there weren’t jerks, or that this didn’t contribute to the conflict, but there seems to be a lack of reflection on this story because there is almost certainly more to it than that.
You mean because then it would be in their back yard? Or why?
If the index had cardinality metadata, it could jump directly to the leaf node containing the first row in the result set.
Which connector was that?
You can turn off tables you’re not interested in, but perhaps this was a bug.
The comment “there was no product here” is referring to a specific (very lucrative) market segment.
The rest of the product was and still is selling just fine.
They didn't feel the need to provide multiple recommendations during the AES, or the SHA-3 process, even though Rijndael and Keccak used different constructions relative to RC6/TwoFish and SHA-2/Blake2. Why now?
> Both BIKE and HQC are based on structured codes, and either would be suitable as a general-purpose KEM that is not based on lattices
What's up with this caveat? Why would the standard require algorithms not based on lattices assuming there is confidence in the lattice based approach?
Is this a security concern, or is there some performance (ops/sec or size) related trade-off?
Of course, just making an IDE multi-player would introduce chaos. What if the tool solved that chaos?
> 54% — said they would be willing to take a pay cut to work at a company that shares their values.
> And 56% said they wouldn’t even consider a job at a company that has values they disagree with
So, for a company that doesn't go around taking sides, there may be less willingness to take a pay cut for a good cause, but presumably the full talent market is open for them.
That process starts from a lower energy level than starting from methane or oil, and so overall its more expensive. We would have to be willing to commit to generating a "surplus" of carbon-free power (e.g. nuclear, wind, solar) to support that sort of manufacturing, but it would be possible.
Also, a great thing about running electrochemical processes off of a periodic energy source like solar or wind is that the economics are easy to load-shift -- you care about the aggregate work output, not the consistency of work output.
See also: https://en.wikipedia.org/wiki/Go_(programming_language)#Omis...
Go is the most popular of this set, but to me seems like it barely qualifies as "high level". On Tiobe, the next most popular language from this set after Go is Haskell.
I like Haskell just fine, but what I really care about is "a more high level GC'd language than Go that ships binaries".
Does this not meet your requirements?
Allow some facebook supplied javascript to set a first party cookie when the user hits website.com/ad-34, and then reference that 1st party cookie the next day when the user returns. Phone home when they buy something. Facebook can now correlate (1) the ping they received to begin with, (2) the user session cookie they initiated on the first visit, and (3) the user session they observed when a purchase was made.
I'm sure things get easier with 3rd party tracking, but fundamentally you can do it without cross-site tracking.
IIUC, you can do attribution with a very basic ad: <a href="website.com/ad-34" ping="fb.com/my-product/ad-34/ping"><img src="fb.com/my-product/ad-34/img.jpeg" /> Come buy my product, you'll love it!</a>
Then you sum up all the "/ad-34" hits, and figure out how many of those user sessions (which are now on your own site -- single domain, but perhaps leveraging a script supplied by the ad network) went and actually bought something. The ad network can correlate those sessions with the "ping" it receives to determine clicks vs. conversions.
- If a site is attacked, there is no risk that password material was extracted from application memory — site operator can dump session tokens and safely re-auth users.
Sending the password over HTTPS doesn’t expose the password to passive observers, but it does unnecessarily expose the password to the server.
https://en.m.wikipedia.org/wiki/Password-authenticated_key_a...