HellPie on Nostr: stand by me :flag: :flag: :flag: :flag: :flag: Well you still need some ...
stand by me :flag: :flag: :flag: :flag: :flag: (npub1vwr…fnzd) Well you still need some infrastructure work in the backend if you want that to behave nicely. Chats have inherit concepts that private threads don't handle and vice-versa threads have a bunch of shit that chats don't care about or sometimes don't want. Displaying a thread as a chat for example has issues, like what happens when I add new people to the chat? Older messages just don't show up? What happens when the thread is deleted? If a chat can be deleted or multiple chats can be started with the same person isn't that just a normal private thread like emails? You can disable some UI elements for example force the users to reply in chronological order, no nesting, but you still won't fix the fact that you just made a fancier email thread, which is not a chat. You could call them DMs because “technically not wrong” but nobody calls threads DMs and DMs are exclusively chat-like one-on-one channels in the eyes of most people so you'd be running into UX problems like how do you make an OOBE that explains what your unique definition of DM is without confusing the user, without going on for too long and without putting them off from ever using the feature... It's just a mess imo. AP can be used for chat, I just don't believe the higher level actors that already exist for the Mastodon-like Fediverse (Idk if PeerTube or Pixelfed has more "proper" chat-like data structures) can be used for chats without either kneecapping user experience or lots of very nasty hacks to brute force the data into the UI (and likely the database too).
Published at
2023-06-20 13:10:54Event JSON
{
"id": "fbaa252c7c0d434b8897d34aa6d15341bf4bee90609648caff81a289766ec11f",
"pubkey": "01e1ebb0d39fa82188a6f95fb56e8fa91738f76c43e24e9d1c732707a409ba5d",
"created_at": 1687266654,
"kind": 1,
"tags": [
[
"p",
"6387482bc4cbd27eab5eeb91f7f84eb3a17582c8291d331feb32bb089594b609",
"wss://relay.mostr.pub"
],
[
"e",
"379f9d9696d58fd316f11ce413ec775da45632b296dd2ba6d099e9e47d97ff97",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://raru.re/users/hellpie/statuses/110576707442158929"
]
],
"content": "nostr:npub1vwr5s27ye0f8a267awgl07zwkwshtqkg9ywnx8ltx2as39v5kcysu9fnzd Well you still need some infrastructure work in the backend if you want that to behave nicely. Chats have inherit concepts that private threads don't handle and vice-versa threads have a bunch of shit that chats don't care about or sometimes don't want. Displaying a thread as a chat for example has issues, like what happens when I add new people to the chat? Older messages just don't show up? What happens when the thread is deleted? If a chat can be deleted or multiple chats can be started with the same person isn't that just a normal private thread like emails? You can disable some UI elements for example force the users to reply in chronological order, no nesting, but you still won't fix the fact that you just made a fancier email thread, which is not a chat. You could call them DMs because “technically not wrong” but nobody calls threads DMs and DMs are exclusively chat-like one-on-one channels in the eyes of most people so you'd be running into UX problems like how do you make an OOBE that explains what your unique definition of DM is without confusing the user, without going on for too long and without putting them off from ever using the feature... It's just a mess imo. AP can be used for chat, I just don't believe the higher level actors that already exist for the Mastodon-like Fediverse (Idk if PeerTube or Pixelfed has more \"proper\" chat-like data structures) can be used for chats without either kneecapping user experience or lots of very nasty hacks to brute force the data into the UI (and likely the database too).",
"sig": "5770f405eee59c5a2cec29c7ffcd99699ec49c451d126cd97453e7ca856c76d35fd05ac9bc52e92752ac01f626d255f69c0ecde7e6be1f214bc34f2fb9ec1a32"
}
