[chore] Replace pinafore with semaphore (#1801)

* Replace pinafore with semaphore

* Typo

8 files changed, 11 insertions, 11 deletions

diff --git a/README.md b/README.md
index 604f8192d..a25224126 100644
--- a/README.md
+++ b/README.md
@@ -89,13 +89,13 @@ For a detailed view on what's implemented and what's not, and progress made towa
 
 The Mastodon API has become the de facto standard for client communication with federated servers, so GoToSocial has implemented and extended the API with custom functionality.
 
-In short, this means full support for modern, beautiful apps like [Tusky](https://tusky.app/) and [Pinafore](https://pinafore.social/).
+In short, this means full support for modern, beautiful apps like [Tusky](https://tusky.app/) and [Semaphore](https://semaphore.social/).
 
-Tusky                                                        |  Pinafore
+Tusky                                                        |  Semaphore
 :-----------------------------------------------------------:|:------------------------------------------------------------------:
-![An image of GoToSocial in Tusky](./docs/assets/tusky.png)  | ![An image of GoToSocial in Pinafore](./docs/assets/pinafore.png)
+![An image of GoToSocial in Tusky](./docs/assets/tusky.png)  | ![An image of GoToSocial in Semaphore](./docs/assets/semaphore.png)
 
-If you're used to using Mastodon with Tusky or Pinafore, you'll find using GoToSocial a breeze.
+If you're used to using Mastodon with Tusky or Semaphore, you'll find using GoToSocial a breeze.
 
 ### Granular post settings
 
@@ -183,7 +183,7 @@ Since GoToSocial is still in alpha, there are plenty of bugs. We use [GitHub iss
 
 ### Client App Issues
 
-GoToSocial works great with Tusky and Pinafore, but some other client applications still need work or have issues connecting to GoToSocial. We're tracking them [right here](https://github.com/superseriousbusiness/gotosocial/projects/5). It's our goal to make any app that's compatible with the Mastodon API work seamlessly with GoToSocial.
+GoToSocial works great with Tusky and Semaphore, but some other client applications still need work or have issues connecting to GoToSocial. We're tracking them [right here](https://github.com/superseriousbusiness/gotosocial/projects/5). It's our goal to make any app that's compatible with the Mastodon API work seamlessly with GoToSocial.
 
 ### Federation Issues
 
diff --git a/docs/assets/semaphore.png b/docs/assets/semaphore.png
new file mode 100644
index 000000000..894ed35e1
--- /dev/null
+++ b/docs/assets/semaphore.png
diff --git a/docs/faq.md b/docs/faq.md
index b113bc676..1622e13a1 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -1,6 +1,6 @@
 # Frequently Asked Questions
 
-- **Where's the user interface?** GoToSocial is just a bare server for the most part and is designed to be used thru external applications. [Pinafore](https://pinafore.social) and [Tusky](https://tusky.app/) are the best-supported, but anything that supports the Mastodon API should work, other than the features GoToSocial doesn't yet have. Permalinks and profile pages are served directly thru GoToSocial as well as the settings panel, but most interaction goes thru the apps.
+- **Where's the user interface?** GoToSocial is just a bare server for the most part and is designed to be used thru external applications. [Semaphore](https://semaphore.social/) and [Tusky](https://tusky.app/) are the best-supported, but anything that supports the Mastodon API should work, other than the features GoToSocial doesn't yet have. Permalinks and profile pages are served directly thru GoToSocial as well as the settings panel, but most interaction goes thru the apps.
 
 - **Why aren't my posts showing up on my profile page?** Unlike Mastodon, the default post visibility is Unlisted. If you want something to be visible on your profile page, the post must have Public visibility.
 
diff --git a/docs/index.md b/docs/index.md
index df9383766..01c994f0a 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -38,7 +38,7 @@ Since GoToSocial is still in alpha, there are plenty of bugs. We use [GitHub iss
 
 ### Client App Issues
 
-GoToSocial works great with Tusky and Pinafore, but some other client applications still need work or have issues connecting to GoToSocial. We're tracking them [right here](https://github.com/superseriousbusiness/gotosocial/projects/5). It's our goal to make any app that's compatible with the Mastodon API work seamlessly with GoToSocial.
+GoToSocial works great with Tusky and Semaphore, but some other client applications still need work or have issues connecting to GoToSocial. We're tracking them [right here](https://github.com/superseriousbusiness/gotosocial/projects/5). It's our goal to make any app that's compatible with the Mastodon API work seamlessly with GoToSocial.
 
 ### Federation Issues
 
diff --git a/docs/installation_guide/binary.md b/docs/installation_guide/binary.md
index 0a5e21b81..81410d8c8 100644
--- a/docs/installation_guide/binary.md
+++ b/docs/installation_guide/binary.md
@@ -103,7 +103,7 @@ Replace `some_username` with the username of the account you just created.
 
 ## 6. Login
 
-You should now be able to log in to your instance using the email address and password of the account you just created. We recommend using [Pinafore](https://pinafore.social) or [Tusky](https://tusky.app) for this.
+You should now be able to log in to your instance using the email address and password of the account you just created. We recommend using [Semaphore](https://semaphore.social) or [Tusky](https://tusky.app) for this.
 
 ## 7. \[Optional\] Enable the systemd service
 
diff --git a/docs/installation_guide/websocket.md b/docs/installation_guide/websocket.md
index cc5a56c69..1cbff952a 100644
--- a/docs/installation_guide/websocket.md
+++ b/docs/installation_guide/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 Pinafore.
+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.
 
 In order to use this functionality, you need to ensure that whatever proxy you've configured GoToSocial to run behind allows WebSocket connections through.
 
diff --git a/internal/api/client/streaming/streaming.go b/internal/api/client/streaming/streaming.go
index 35f8a1aed..71b325089 100644
--- a/internal/api/client/streaming/streaming.go
+++ b/internal/api/client/streaming/streaming.go
@@ -54,7 +54,7 @@ func New(processor *processing.Processor, dTicker time.Duration, wsBuf int) *Mod
 			ReadBufferSize:  wsBuf, // we don't expect reads
 			WriteBufferSize: wsBuf,
 
-			// we expect cors requests (via eg., pinafore.social) so be lenient
+			// we expect cors requests (via eg., semaphore.social) so be lenient
 			CheckOrigin: func(r *http.Request) bool { return true },
 		},
 	}
diff --git a/internal/middleware/cors.go b/internal/middleware/cors.go
index 22e2e81d5..caa091e62 100644
--- a/internal/middleware/cors.go
+++ b/internal/middleware/cors.go
@@ -25,7 +25,7 @@ import (
 )
 
 // CORS returns a new gin middleware which allows CORS requests to be processed.
-// This is necessary in order for web/browser-based clients like Pinafore to work.
+// This is necessary in order for web/browser-based clients like Semaphore to work.
 func CORS() gin.HandlerFunc {
 	cfg := cors.Config{
 		// todo: use config to customize this