-
-This is a public message with no conversation members so no private transport is used. There are two paths it can take - as a bbcode path to DFRN clients, and converted to HTML with the server's PuSH (pubsubhubbub) hubs notified. When a PuSH hub is operational, dfrn-poll clients prefer to receive their information through the PuSH channel. They will fall back on a daily poll in case the hub has delivery issues (this is quite common when using the default Google reference hub). If there is no specified hub or hubs, DFRN clients will poll at a configurable (per-contact) rate at up to 5-minute intervals. Feeds retrieved via dfrn-poll are bbcode and may also contain private conversations which the poller has permissions to see.
-
-Scenario #2. Jack replies to Bob's public message. Jack is on the Friendika/DFRN network.
-
-Jack uses dfrn-notify to send a direct reply to Bob. Bob then creates a feed of the conversation and sends it to everybody involved in the conversation using dfrn-notify. PuSH hubs are notified that new content is available. The hub or hubs will then retrieve the latest feed and transmit it to all hub subscribers (which may be on different networks).
-
-Scenario #3. Mary replies to Bob's public message. Mary is on the Friendika/DFRN network.
-
-Mary uses dfrn-notify to send a direct reply to Bob. Bob then creates a feed of the conversation and sends it to everybody involved in the conversation (excluding himself, the conversation is now sent to both Jack and Mary). Messages are sent using dfrn-notify. Push hubs are also notified that new content is available. The hub or hubs will then retrieve the latest feed and transmit it to all hub subscribers (which may be on different networks).
+---
+This is a public message with no conversation members so no private transport is used.
+There are two paths it can take - as a bbcode path to DFRN clients, and converted to HTML with the server's PuSH (pubsubhubbub) hubs notified.
+When a PuSH hub is operational, dfrn-poll clients prefer to receive their information through the PuSH channel.
+They will fall back on a daily poll in case the hub has delivery issues (this is quite common when using the default Google reference hub).
+If there is no specified hub or hubs, DFRN clients will poll at a configurable (per-contact) rate at up to 5-minute intervals.
+Feeds retrieved via dfrn-poll are bbcode and may also contain private conversations which the poller has permissions to see.
+
+Scenario #2. Jack replies to Bob's public message. Jack is on the Friendica/DFRN network.
+---
+Jack uses dfrn-notify to send a direct reply to Bob.
+Bob then creates a feed of the conversation and sends it to everybody involved in the conversation using dfrn-notify.
+PuSH hubs are notified that new content is available.
+The hub or hubs will then retrieve the latest feed and transmit it to all hub subscribers (which may be on different networks).
+
+Scenario #3. Mary replies to Bob's public message. Mary is on the Friendica/DFRN network.
+---
+Mary uses dfrn-notify to send a direct reply to Bob.
+Bob then creates a feed of the conversation and sends it to everybody involved in the conversation (excluding himself, the conversation is now sent to both Jack and Mary).
+Messages are sent using dfrn-notify.
+Push hubs are also notified that new content is available.
+The hub or hubs will then retrieve the latest feed and transmit it to all hub subscribers (which may be on different networks).