I would say that banana is the property of the tree the gorilla "stole" it from.

And I don't think animals see this banana as "property of the gorilla" as you suggested.

I think they see it as "if I try to take this banana from that gorilla, I will get slapped"

The bananas weren’t stolen, they were sold to the gorilla in return for seed distribution services. The tree wants the gorilla to distribute the banana seed within a fertiliser package (poop) some distance away. And the gorilla wants calories, which the tree can endlessly produce using solar power. It’s a fair trade.

Didn't the banana plant (not a tree, technically) produce that banana using nutrients stolen from the soil, carbon dioxide stolen from the air, energy stolen from the sun, etc.?

Exactly: the whole system is based on theft, and should be stopped.

>> if you’re wrong, you’re not accountable to your actions because there was never any actual money on the line.

> I mean, that's the risk you run right?

> Either you're a regulated system where you can avoid this kind of thing, or you're an unregulated system where you go 'screw the man', but you don't get the protections that are associated with the traditional financial system.

He does not mean companies operating in the unregulated crypto space. He means the author of articles like this one.

When I visit the site, I get

  TypeError: Cannot read properties of undefined (reading 'reduce')
      at getTweets (/myapp/build/index.js:898:22)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at loader5 (/myapp/build/index.js:991:48)
      at Object.callRouteLoader (/myapp/node_modules/@remix-run/server runtime/dist/data.js:77:14)

Tbh that’s kinda ironic.

Oh, immediately fixed. Interesting

I'm still getting that

Should be fixed now

same

It just tried out all keys you have until it worked. If you run `ssh new@prose.sh -v` you should see something like this after you closed the TUI:

  debug1: Authentications that can continue: publickey
  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/tender_euler/.ssh/id_rsa RSA SHA256:F67gFVIydWnAVPU6HcYUD/tEjmmgOgwFPs+dzELhgD8
  debug1: send_pubkey_test: no mutual signature algorithm
  debug1: Trying private key: /home/tender_euler/.ssh/id_ecdsa
  debug1: Trying private key: /home/tender_euler/.ssh/id_ecdsa_sk
  debug1: Offering public key: /home/tender_euler/.ssh/id_ed25519 ED25519 SHA256:1H4mPO+WR0SMockqr+Vljy+1ht7bj/QIKL71d8nBIZk
  debug1: Server accepts key: /home/tender_euler/.ssh/id_ed25519 ED25519 SHA256:1H4mPO+WR0SMockqr+Vljy+1ht7bj/QIKL71d8nBIZk
  Authenticated to prose.sh ([2604:a880:800:10::8c1:e001]:22) using "publickey".

Do I understand this correctly that you need to safely store your random grid since only the pattern is in your head? Losing the grid would then essentially mean you can't access your keys anymore even though someone else also can't. But maybe I overlooked something. Will take another look tomorrow.

However, I want to mention the technique of making up a story to remember the seed words. I found this to be fairly easy so I am not sure how this grid can be more useful than that.

But still a very cool and interesting idea! Thanks for sharing. (You even made me create a HN account to post my first comment)

Yes, you are correct - you need to store your grid and you can do that via a physical print, digital storage (including a native encryption option), and a recovery phrase for deterministic grids (12 words). The latter provides the means to storage the grids in the same way you would a normal seed phrase, but with an added layer of security against evil maid attack. The provides the ability to use a decoy too. Gridception is also an option, explained on our website.