3 ms·
I'm glad somebody looked, because basics like when messages are actually passed around is something I didn't see in the atproto docs either. Alice on server X
by tedunangst 3y ago
I'm glad somebody looked, because basics like when messages are actually passed around is something I didn't see in the atproto docs either.
Alice on server X follows Bob on server Y. When are Bob's posts delivered to X such that Alice may see them? Are they pushed from Y? Are they pulled by X?
Polling seems like an absolute disaster in an environment where people have an expectation of semi real-time communication.
- justguessing7 3y agoThe post alleges Bluesky pull based, which would imply it's like RSS but with signatures: > It uses pull-based federation instead of push-based like Mastodon. I was hoping they would employ both: push and pull. Some scenarios I could imagine pull being more efficient, and sometimes push. For instance if I run my own server I don't need to be pushed all content when I sleep. However when I return it could do pulls and then continue pushing. It doesn't look like it's clever like that.
- eropple 3y agoThere are likely scenarios where some level of push-based comms will be necessary, as I understand it. Direct messaging, for example, seems like it'll require pinging a server to pull an asymmetrically encrypted message, or similar.
- afiori 3y agoDMs are not a planned feature of this protocol