Matt

No, live topics are not cached.
The vast majority of traffic for any forum is guest traffic. This can be from bots, as well as people coming in from external links. We have some communities that may have 1500 people online, but 10,000 guests. Caching via CDN allows us to serve that traffic without touching any processing (PHP/MySQL/Redis, etc) for maximum efficiency. The cache lasts for around 15 minutes which is absolutely fine for communities. If your guests want 'live' updates, then simply encourage them to sign up. Logged in members will be served the live pages, not the CDN cache.

As an addendum, I would say that a core part of any community strategy is to convert guests into members. Members have more tools including notifications to make your site more 'sticky'.
Allowing guests too much scope will reduce the number of sign-ups you ultimately get. There is a balance of course, I dislike things like restricting viewing attachments (often photos) to members only and restricting the number of topics they read, but finding ways to encourage registration is a good long term strategy.

No, live topics are not cached.
The vast majority of traffic for any forum is guest traffic. This can be from bots, as well as people coming in from external links. We have some communities that may have 1500 people online, but 10,000 guests. Caching via CDN allows us to serve that traffic without touching any processing (PHP/MySQL/Redis, etc) for maximum efficiency. The cache lasts for around 15 minutes which is absolutely fine for communities. If your guests want 'live' updates, then simply encourage them to sign up. Logged in members will be served the live pages, not the CDN cache.

Just for clarification, Pages is getting a substantial update for v5 and is a core part of our community platform strategy.

Just for clarification, Pages is getting a substantial update for v5 and is a core part of our community platform strategy.

Just for clarification, Pages is getting a substantial update for v5 and is a core part of our community platform strategy.

Just for clarification, Pages is getting a substantial update for v5 and is a core part of our community platform strategy.

As an addendum, I would say that a core part of any community strategy is to convert guests into members. Members have more tools including notifications to make your site more 'sticky'.
Allowing guests too much scope will reduce the number of sign-ups you ultimately get. There is a balance of course, I dislike things like restricting viewing attachments (often photos) to members only and restricting the number of topics they read, but finding ways to encourage registration is a good long term strategy.

Just for clarification, Pages is getting a substantial update for v5 and is a core part of our community platform strategy.

Just for clarification, Pages is getting a substantial update for v5 and is a core part of our community platform strategy.

Time machine to 2025 and download v5.1 🤣

Yeah, until they scrap pages too 😄

No, live topics are not cached.
The vast majority of traffic for any forum is guest traffic. This can be from bots, as well as people coming in from external links. We have some communities that may have 1500 people online, but 10,000 guests. Caching via CDN allows us to serve that traffic without touching any processing (PHP/MySQL/Redis, etc) for maximum efficiency. The cache lasts for around 15 minutes which is absolutely fine for communities. If your guests want 'live' updates, then simply encourage them to sign up. Logged in members will be served the live pages, not the CDN cache.

As an addendum, I would say that a core part of any community strategy is to convert guests into members. Members have more tools including notifications to make your site more 'sticky'.
Allowing guests too much scope will reduce the number of sign-ups you ultimately get. There is a balance of course, I dislike things like restricting viewing attachments (often photos) to members only and restricting the number of topics they read, but finding ways to encourage registration is a good long term strategy.

As an addendum, I would say that a core part of any community strategy is to convert guests into members. Members have more tools including notifications to make your site more 'sticky'.
Allowing guests too much scope will reduce the number of sign-ups you ultimately get. There is a balance of course, I dislike things like restricting viewing attachments (often photos) to members only and restricting the number of topics they read, but finding ways to encourage registration is a good long term strategy.

Interesting. Thank you for the clarification.

No, live topics are not cached.
The vast majority of traffic for any forum is guest traffic. This can be from bots, as well as people coming in from external links. We have some communities that may have 1500 people online, but 10,000 guests. Caching via CDN allows us to serve that traffic without touching any processing (PHP/MySQL/Redis, etc) for maximum efficiency. The cache lasts for around 15 minutes which is absolutely fine for communities. If your guests want 'live' updates, then simply encourage them to sign up. Logged in members will be served the live pages, not the CDN cache.

No, live topics are not cached.
The vast majority of traffic for any forum is guest traffic. This can be from bots, as well as people coming in from external links. We have some communities that may have 1500 people online, but 10,000 guests. Caching via CDN allows us to serve that traffic without touching any processing (PHP/MySQL/Redis, etc) for maximum efficiency. The cache lasts for around 15 minutes which is absolutely fine for communities. If your guests want 'live' updates, then simply encourage them to sign up. Logged in members will be served the live pages, not the CDN cache.

No, live topics are not cached.
The vast majority of traffic for any forum is guest traffic. This can be from bots, as well as people coming in from external links. We have some communities that may have 1500 people online, but 10,000 guests. Caching via CDN allows us to serve that traffic without touching any processing (PHP/MySQL/Redis, etc) for maximum efficiency. The cache lasts for around 15 minutes which is absolutely fine for communities. If your guests want 'live' updates, then simply encourage them to sign up. Logged in members will be served the live pages, not the CDN cache.

Glad you were able to resolve the issue 🙂 .

In case anyone else has this issue, I figured it out. There is a separate Logo setting for e-mail headers. I was thinking it was sharing the same header as the forum theme -- this is not the case.
Found this in General > Settings > E-mail Settings when looking for something unrelated. 😄 I believe the behavior is it pulls in the first logo you upload and keeps that setting, as when I changed the forum theme to a smaller logo, the large email header remained. Then I uploaded the smaller logo here. Just make sure to hit Save!

Now a normal size!!

This is the support forum and we can only inform you on what is possible today. If you want to request things for the future, please use the Feedback forum as mentioned. In order to separate types of requests and ensure they are properly reviewed, they need to go in the proper places. I am sorry you do not like that but it is the current steps. You don’t want feature request cluttering up support requests and potentially missing something important like a site being down, right? So organization is important.  
Please remember that our developers do not work on projects out of thin air. There is quite a significant amount of planning involved to build a software like ours. To voice your suggestions, the Feedback forum is how you get your idea started. 

Ah, ok. I can disable it programmatically for cloud clients.

Awesome changes as usual, very well made.
Looking forward to them

Yeah, I think we can stick in a bug report for this. It does make a pretty big loophole for spammers and bad actors.