fiatjaf on Nostr: ...
This is the kind of example people use to say we should never expose any "internal" codes to users because they are dumb and will be frightened, it's not "good UX" and so on.
And yet phone apps do show the number that is calling, even if there is a name associated with it.
And they also show users a giant keypad where users can type numbers directly and -- surprise -- everybody understands and types numbers there all the time! (or at least they did when people used to use telephones.)
Published at
2023-06-26 17:00:33Event JSON
{
"id": "bf7ec43a5c0b022a32a7636bd81e2e0bb3e4554f78307f31b5fa9f238a77f1e6",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1687798833,
"kind": 1,
"tags": [],
"content": "https://nostr.build/i/d9abeaa14c8c8cadd04edce071b38a53c643cf308e9cfc0a13838a9df54e4d55.jpg\n\nThis is the kind of example people use to say we should never expose any \"internal\" codes to users because they are dumb and will be frightened, it's not \"good UX\" and so on.\n\nAnd yet phone apps do show the number that is calling, even if there is a name associated with it.\n\nAnd they also show users a giant keypad where users can type numbers directly and -- surprise -- everybody understands and types numbers there all the time! (or at least they did when people used to use telephones.)",
"sig": "efb2f2bcdfc4d2abc4955464adbec901208765fe1b51057901efa9f08320b7c71969efe54684c89edc2ae255c58e085823c963e84920061f731ce655540e9e33"
}