Websockets - Locally Hosted Alternative for Pusher (Now Free)

Wadera

Thank you for quick reaction on Discord! It's fixed now, by temporary script adjust (should be released soon on official update)

Kyrne

matteocontrini no, guests will not see the button, this is an oversight and I'll release a patch (along with that other fix) in an update.

It stores some values in localstorage which allows it to save connections.

Kyrne

Just pushed an update in anticipation of beta 15. When you update Flarum with the provided instructions on the release announcement, WebSocket will be updated in tandem and be ready to go!

Fantomen

I´m facing an issue on Beta 15, websocket version 2.1.1.

Posts are not loaded automatically as they should but are very delayed. They are seen instantly if you click the little arrow to the right to go to the end of the discussion. Console looks normal and shows no error.

Anyone had the same issue? See gif below;

https://imgur.com/a/tINc6Aw

Kyrne

2.2.0

Added a check when starting the server to ensure the certs are accessible
Added some code to allow an upcoming extension of mine to work

Fantomen

Kyrne
Cheers for the Update. Unfortunately I’m still having issues with posts not being displayed immediately in real time as my gif above shows.

[deleted]

Fantomen Cheers for the Update. Unfortunately I’m still having issues with posts not being displayed immediately in real time as my gif above shows.

I seem to have a similar issue. I need to reload the page for the discussion to appear.

Kyrne

[deleted] danielunited Fantomen

Thank you all for being awesome customers! I hope this version solves everything for you.

2.3.0

Fixed events not triggering when using the non-Nginx method
Fixed new posts not showing up until a button is pushed (grey loading bars)
Posts in private discussions/tags will now update across tabs. (Wouldn't be pushed to the posting user before the update)
Added option to have discussions refresh without the yellow banner popping up or needing to be clicked. (Setting on admin page)

Clear cache after updating.

danielunited

Is there a demo/community that uses this? Would love to test how it works before buying

askvortsov

danielunited discuss.flarum.org 😃

danielunited

Just a suggestion - but would be great if discussions could be updated automatically - without the need to press this button:

That's the main reason I'm looking to switch from Pusher

[deleted]

Kyrne Thank YOU for addressing this so quickly, and for being so accommodating 🙂

Fantomen

Kyrne Thank you! It works well now and posts were updated quickly yesterday on my forum (280 posts in one discussion in 3h).

JAC

Is there a way to change the colour of new discussion bar?

Thanks

Kyrne

JAC you can via css.

Kyrne

I just wanted to quickly say from the bottom of my heart how much it means to me that you guys all support my development work. It's been a crazy start to my year and it gives me so much joy every time I see one of you subscribing to Websocket (or ReCache)! I'm not going to tag all 15, but you know who you are, thank you!

I can't wait to bring you the latest expansion to the Websocket ecosystem of compatible extensions in the near future.

DursunCan

@Kyrne Can ReCache and this extension be made to work on all platforms? Shared hosting (cPanel, Plesk), virtual servers, web servers (litehttpd, apache, litespeed)

Kyrne

DursunCan WebSocket and ReCache can be made to work on any web server. They can both potentially work on shared hosting depending on the privileges your host gives you. If you only have Plesk or cPanel you are SOL. There's no reason to use ReCache on shared hosting anyway, you're putting your money in the wrong place.

mekici

Kyrne While the Websocket extension is active and there are 1500 people in the forum instantly, the CPU usage is around 50% -60%. When you close the Websocket plugin, this value drops by 20%. Updating 10-15 discussions on the home page starts giving "opps ..." error.

We use 32 CPU dedicated servers in Digitalocean.

askvortsov

mekici For enterprise-grade communities, perhaps it might make sense to include support for pusher alternatives that can be hosted efficiently on a separate process like Poxa? Although it'd be a little bit more complex to set up, a small isolated program written in a websockets-optimized language like Elixir might scale better.

@Kyrne maybe support for that could be included in websockets? I'm hoping to eventually support it in regular Pusher as well, but websockets comes with the benefits of pushing events for private (or generally non-public) discussions.

Kyrne

askvortsov As far as my testing has gone, the websocket server is completely built-in as an option. It should work with any websocket server that uses the pusher protocol without any changes from me.

« Previous Page Next Page »