It‘s a general problem with AI, no? It has no stakes and feels no pain. At least the slaves of Ancient Rome were threatable by punishment for mistakes.
When this film of his village was recorded, he was 46 years old:
Definitely keep asking!
What trajectory would Ray Kurzweil project for the Roman Empire in AD 50? Probably one disregarding the growing complexity and corruption of big interwoven systems.
My grandfather lived from 1916 to 2012. From before commercial radio to the iPhone. That‘s crazy.
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 doesn‘t like lightning.
„Tests need to be designed. Principles of design apply to tests just as much as they apply to regular code. Tests are part of the system; and they must be maintained to the same standards as any other part of the system.“
nostr:npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnft I think, this is your best line. I often return to this as a first-principle of testing.
I‘m a content creator and I can live of it. I create code read by machines.
Ha, never thought about that. So kind could also just be a name.
Alright. Makes sense.
😁 now I am at a loss.
„Everything gets exponential“ is an advantage in this case. Storing bigger numbers becomes cheaper and cheaper the bigger they are.
No, just allowing bigger numbers.
Maybe an example helps:
- 0..65534 uses 16bits
- 65535..2^32-2 uses 32 bits
- 2^32-1..2^64-2 uses 64bits
and so on. Small numbers use up less space than big ones. This is complicated for binary protocols, but not for nostr.
There‘s one misconception here: the amount of available numbers grows exponentially with space, not the other way round. So kind-bitsize grows logarithmically with each number added. That’s quite nice.
It kind of works with Unicode (see https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/).
And compared to note text, hash and pubkey, the amount of bytes used for a kind doesn‘t really matter.
Almost: nostr is not a binary protocol, so it‘s quite easy to make 65535 an indicator of a „long-kind“ event.
nostr trust experiment:
If I reference a nostr event id which never existed, will people assume that they miss relay access and continue discussing the (heated/dramatic) topic, or will they do the right thing: ignore the missing source?
The idea is a falconry but for nostriches. It makes the not flying bird fly I guess. 🤷♂️
Hm… nostrichcote 🤔
Well, or continue 😄
Feel free to have a look at my little mess here: https://github.com/schmijos/nostr-voliere/tree/main/features
Maybe you‘ve got a better idea on how to structure the specs.