The old style Ajax polling has been removed in v5. It is not terribly efficient and it's generally better to push when there is new data rather than constantly pull. This is what we do with Invision Community Cloud.

Changed Status to Not a bug

41 minutes ago, Matt said:

The old style Ajax polling has been removed in v5. It is not terribly efficient and it's generally better to push when there is new data rather than constantly pull. This is what we do with Invision Community Cloud.

I thought it worked well, but there was a clear issue I saw on a forum using cloud and it was a busy topic I noticed the notification was popping up constantly.

Does it still notify you of new replies now?

Edited January 31Jan 31 by marklcfc

4 hours ago, marklcfc said:

Does it still notify you of new replies now?

No, it doesn't. Looks like I need to remember to refresh each tab before I reply now. For example, I wouldn't have replied to the topic I linked above since the user clarified in newer replies that it was actually HTML/JS rather than PHP.

I don't remember this feature removal being discussed anywhere. It's a rather 'annoying' change. 😒

Edited January 31Jan 31 by teraßyte

This looks like a secret migration of all community functionality to the cloud over time.

58 minutes ago, teraßyte said:

No, it doesn't. Looks like I need to remember to refresh each tab before I reply now. For example, I wouldn't have replied to the topic I linked above since the user clarified in newer replies that it was actually HTML/JS rather than PHP.

I don't remember this feature removal being discussed anywhere. It's a rather 'annoying' change. 😒

You are right, this is a feature that must be present in the script forums, see Beta 1 where this feature was removed starting from Beta 2

1 hour ago, teraßyte said:

29 minutes ago, Kirill Gromov said:

This looks like a secret migration of all community functionality to the cloud over time.

That's very annoying🤦

Edited January 31Jan 31 by EliasM

1 hour ago, Kirill Gromov said:

This looks like a secret migration of all community functionality to the cloud over time.

It sure feels that way. If nothing else release it as a first party addon or something.

On 1/31/2025 at 10:12 AM, Matt said:

The old style Ajax polling has been removed in v5. It is not terribly efficient and it's generally better to push when there is new data rather than constantly pull. This is what we do with Invision Community Cloud.

Matt, would there be any chance this could return for self-hosted at some time?

5 seems so up-to-date compared to 4, but it feels like we are taking a step back to 2004 in this area having to keep refreshing the page to see if there are new replies.

I can see it would be okay if there were a new post to a topic every hour or so, but during times when topics get busy, it feels archaic and a long way around to see new replies.

3 hours ago, LemonGrenade said:

Matt, would there be any chance this could return for self-hosted at some time?

5 seems so up-to-date compared to 4, but it feels like we are taking a step back to 2004 in this area having to keep refreshing the page to see if there are new replies.

I can see it would be okay if there were a new post to a topic every hour or so, but during times when topics get busy, it feels archaic and a long way around to see new replies.

Fix that already.

I’m also in favor of restoring this type of functionality. In very active communities, when many people are engaged in a discussion, no new messages are visible until the page is refreshed. A user writing a post doesn’t know what others have written before them.

This is a really necessary feature for any type of client.

Manually reloading pages to see new responses is a bad.

Since they got rid of the poorly optimized AJAX-based code, there's basically zero chance that we’ll get such a feature on self-hosted. I’d bet that on the cloud, they’re using WebSockets or something similar, so it’s just too much work for a couple of percent of customers to deliver something like that.

I’m happy with what we got, and I understand the business model and the division of new features like live courses and topics—that’s okay. However, this type of functionality really makes it much harder for highly active large communities to function.

Leaving aside the fact that we’ll never see real-time post refreshing, you really could have kept the less optimized version that at least allowed new replies to be se