From dbef5ee03b61d630b46696cfd04c08fcd5b702ce Mon Sep 17 00:00:00 2001 From: Phil Hagelberg Date: Mon, 2 Dec 2024 01:47:05 -0800 Subject: [chore] Replace Semaphore recommendation with Pinafore. (#3586) Neither Semaphore nor Pinafore are under active development, but Semaphore has archived its repository while Pinafore still gets occasional minor maintenance. Enafore has newer features, but it has accessibility bugs affecting screen readers that prevent it from being recommended at this time. --- docs/getting_started/reverse_proxy/websocket.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/getting_started') diff --git a/docs/getting_started/reverse_proxy/websocket.md b/docs/getting_started/reverse_proxy/websocket.md index ec7c107a9..68d28bc5c 100644 --- a/docs/getting_started/reverse_proxy/websocket.md +++ b/docs/getting_started/reverse_proxy/websocket.md @@ -1,6 +1,6 @@ # WebSocket -GoToSocial uses the secure [WebSocket protocol](https://en.wikipedia.org/wiki/WebSocket) (aka `wss`) to allow for streaming updates of statuses and notifications via client apps like Semaphore. +GoToSocial uses the secure [WebSocket protocol](https://en.wikipedia.org/wiki/WebSocket) (aka `wss`) to allow for streaming updates of statuses and notifications via client apps like Pinafore. In order to use this functionality, you need to ensure that whatever proxy you've configured GoToSocial to run behind allows WebSocket connections through. -- cgit v1.2.3