Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What if there were no "thread" rooms? #47

Open
vwkd opened this issue Jul 28, 2021 · 0 comments
Open

What if there were no "thread" rooms? #47

vwkd opened this issue Jul 28, 2021 · 0 comments

Comments

@vwkd
Copy link

vwkd commented Jul 28, 2021

Could the single "user timeline" room be enough or are "thread" rooms necessary?

It would require members of Bob's "timeline room" to be able to reply to messages (replies to tweets) without being able to write new standalone messages (tweet in Bob's name). I guess these granular permissions aren't possible, but maybe that could be a MSC?

I tried to think about more differences. Please correct me where I'm missing something.

Pros:

  • Just one single room on the homeserver whose number of messages grow instead of many rooms whose number grows. Not sure if this buys anything, or if one room or many rooms scale equally well?
  • Search across a user's tweets with all replies just searches a single room instead of many, probably easier (?)
  • No illogical separation between Tweets (currently, message in "user timeline" room) and their replies (messages in "thread" room), they would all be messages in a single room just separated by their hierarchy
  • No lost messages, e.g. currently writing into a "thread" room from a normal chat client without it being a reply is lost in Ceruleum
  • No distinction between peeking/joining a room depending on if viewing/replying to a Tweet
  • Protected posts, e.g. can't reply to a Tweet without following the user, currently doesn't verify if the user is also member of the "user timeline" room before allowing them to join the "thread" room (?)

Cons:

  • Everything scoped to a single Tweet becomes more difficult since it's just a thread, e.g.
    • can't set permissions for a single Tweet, e.g. block users from replying to one tweet but not others
    • can't send notifications for a single Tweet, e.g. notify user that the Tweet they replied to earlier got new replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant