Event JSON
{
"id": "b14aefd5bd7d4e2b0cf7b025f9add282bb559ffe34e95613b85a0e25a1c050cb",
"pubkey": "b7dfbebf760efb2c756b3cae22baafdbbdf55abb782f85e93b4db804d5cba7e3",
"created_at": 1708037969,
"kind": 1,
"tags": [
[
"p",
"7d2e4a3c783f07b423f05778dc3d13c643f5bcfd97fa3a8a3396624b7af534d0",
"wss://relay.mostr.pub"
],
[
"p",
"49c53002591f6d1403d9a72f4bc37ab92ff82311308be1beeb1b6e72d196b3d9",
"wss://relay.mostr.pub"
],
[
"e",
"fb99c83dfdd7878e24791570b64bda43749ae74810fcd34045fe21195baff75d",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.rights.ninja/users/jeffalyanak/statuses/111937976378297264",
"activitypub"
]
],
"content": "nostr:npub105hy50rc8urmggls2audc0gnceplt08ajlar4z3nje3yk7h4xngq3v7pzg The state of the art may have changed in recent years, but historically TUIs have _not_ worked well with accessibility tools.\n\nHowever, I think best practice is for TUIs to wrap traditional CLI applications which can be much friendlier if implemented correctly. That means there should inherently be an accessible option for every function available in the TUI.",
"sig": "23c3a549628b718954376fb9667be74fefcb5de4f9b275d9fc28bd501d82f757320ed89da069f300fa0853d30573692a4922b83ceab7e2eccfd5479129da51e5"
}