Conversation:
Notices
-
@lnxw48 I'm mostly curious about the exploitability of this. Can I tell a remote server to start fetchibg a bajillion fake notices and effectively DDoS a third party? And how do we minimize this risk _in_ the protocol/best practices?
-
@mmn Don't retrieve the entire conversation tree unless the user chooses to. And rather than retrieving parent messages back to the original and then retrieving the entire tree below, retrieve only the first [three|four|five|x] parent levels, and then [x] levels of children below. In most cases the context of a conversation needs only one or two levels. The UI could implement this …
-
It was really cool to see !andstatus retreive 18 post from this conversation little by little. Still not grasping how this conversation thing works but it seems to mostly work for me.