WebSockets is a technique that allows XF to interact in real-time. However, as of now, it seems that each add-on developer on XF is going in their own direction without any collaboration or unified approach to share or develop together.
As for your initial question, no, I am not involved with the addon or author in any way on XF.
You'll find answers to these questions in the add-on's documentation.
- If I use Pusher do I use "beams" or "Channels" when I set up my account?
- Do I then set the port to 443 for Pusher?
- Also the only keys I see on Pusher is the "Instance ID" and "Primary key", no other keys. What keys do I use exactly?
This question is not directly related to the add-on at all. I'm a developer, not a Google Maps or a geography teacher. And besides, you didn't even say where you wereWhat is cluster closest to me as I don't see that either on pusher?
When you first enter Pusher.com and create an account, it asks you what kind, either Channels or Beams.You'll find answers to these questions in the add-on's documentation.
This question is not directly related to the add-on at all. I'm a developer, not a Google Maps or a geography teacher. And besides, you didn't even say where you were
In the near future, be possible to implement a real-time conversation similar to your real-time thread addons ?
This enhancement would greatly enhance the native system and provide users with the ability to engage in live conversations.
Oh I hadn't seen it! Sounds great! But will the system work with the native system, or have you created a separate messaging system?021 updated  XenForo WebSockets with a new update entry: 1.2.1 Removed check for installed soketi on the server when installing daemons Added /bin/bash prefix to avoid "Executable path is not absolute, ignoring" error Read the rest of this update entry...xenforo.com
* Some elements in the screenshots are no longer relevant.
Everything works on the basis of standard conversations with support for all forum functions. You can already test it on devsell.io
Please make this possible.There should be an option to disable this for guests - the Pusher Sandbox plan has a limit of 100 concurrent connections which can be blown right through if you include active guests.