-
Notifications
You must be signed in to change notification settings - Fork 40
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
Temp subscriptions #237
Comments
I'm not sure any of the current contributors worked on temporary subscriptions, so no idea. Do you know how they worked? |
Clients send directed presence to the pubsub service, and then include the pubsub#expire option when subscribing to a node. Details here: By the way, temporary subscriptions are useful even for authed users. They can be used to receive updates from a channel without an explicit "follow". The webclient supported this. Users could browse to any channel and see realtime updates, whether logged in or not, without having to follow first. |
Pretty much as described in XEP-0060:
The trickiest part was to get federated servers to notify the current servers of changed in a remote channel where the only local subscriber has a temporary subscription. I don't remember how I did that; perhaps it's a corner case that can be ignored to begin with. |
Sitting here with @jkarneges and talking about fanout and temporary subscriptions.
The node server had temp subscriptions to show realtime updates to non-auth'd users (webpage continuously updating). Incidentally it's also what Fanout uses for scaling requests.
What's involved in getting this functionality back?
The text was updated successfully, but these errors were encountered: