You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the seconds to feed entries (maybe it is hidden in payload. It would also be nice to add contact address to join/leave payload if not there (see ticket above for not knowing)
In textile.thread.peers it would be nice to include their join time for that thread in the response.
It seems pretty common in chat interfaces that you want to include Join announcements. It might be handy to create a join/leave message type that can be folded into that single textile.messages query
The text was updated successfully, but these errors were encountered:
I vote #2. The join item will be in the feed for if/when it needs to be displayed, and having this kind of metadata about thread participants seems to fit perfectly into the response from textile.thread.peers
Also, I can see how having join items in the results of textile.messages, but I think the right solution is to have a single method that lets you get all items from a thread with a filter. So getting all message and joins and leaves would be easy.
Right now the easiest way is to look for when they first share or message.
Related: #118
Three possible fixes
seconds
to feed entries (maybe it is hidden in payload. It would also be nice to add contact address to join/leave payload if not there (see ticket above for not knowing)textile.thread.peers
it would be nice to include their join time for that thread in the response.The text was updated successfully, but these errors were encountered: