I’m curious about the decision to “aim for sub second transaction times”, rather than using something cryptography-based, such as a verifiable oblivious pseudorandom function.
That is,
- as a client I could obtain a bunch of credits/tokens from my payment processor
- these tokens have the cryptographic property of being verifiable (ex: “that’s definitely a stripe-verified token worth $0.001”)
- these tokens also have the cryptographic property of being anonymous. (ex: neither stripe, nor the payment recipient know that I am Bob)
With this sort of cryptography based approach, cloudflare could verify my payment token without any cryptocurrency proof-of-work kerfuffle?
It really feels to me like there’s some low hanging fruit with voice that no one is capitalizing on: filler words and pacing.
When the llm notices a silence, it fills it with a contextually aware filler word while the real response generates.
Just an “mhmm” or a “right, right”.
It’d go so far to make the back and forth feel more like a conversation, and if the speaker wasn’t done speaking; there’s no talking over the user garbage. (Say the filler word, then continue listening.)
A few weeks ago I noticed some mysterious app was killing my (poor) internet downloading a large file.
It was chrome, downloading a multi GB file without any sort of UI hints that it was doing so. A generative AI file.
Is this why chrome uses so much ram? They’ve just been pushing up the memory usage in preparation for this day, hoping I wouldn’t notice the extra software now running on my (old, outdated) system?
If I understand the original theory, we can work out the math with a little more detail... (For clarity, the berlin wall was erected in 1961.)
- In 1969 (8 years after the wall was erected): You'd calculate that there's a 50% chance that the wall will fall between 1972 (8x4/3=11 years) and 1993 (8x4=32 years)
- In 1989 (28 years after the wall was erected): You'd calculate that there's a 50% chance that the wall will fall between 1998 (28x4/3=37 years) and 2073 (28x4=112 years)
- In 1961 (when the wall was, say, 6 months old): You'd calculate that there's a 50% chance that the wall will fall between 1961 (0.5x4/3=0.667 years) and 1963 (0.5x4=2 years)
I found doing the math helped to point out how wide of a range the estimate provides. And 50% of the times you use this estimation method; your estimate will correctly be within this estimated range. It's also worth pointing out that, if your visit was at a random moment between 1961 and 1989, there's only a 3.6% chance that you visited in the final year of its 28 year span, and 1.8% chance that you visited in the first 6 months.
I really like the approach of nostr, but when I tried to use it, each client I tried would start me off following ecoin pump and dump influencers. It was really off putting.
I would’ve preferred starting off in an empty room, an experience more like using signal.