Pretty sure it's less weird than venting about an error message by singling out one browser among many, not even showing what happens for the same thing in one of the various Chromes. https://twitter.com/sebmck/status/1155837966763229185 …
-
This Tweet is unavailable.
-
Replying to @nokusu
Try the same scenario in Chrome and you’ll find the same error message references the websockets connecting state. Much more descriptive and actionable. Firefox is my main browser. I use it on all my devices. My tweet isn’t even worded aggressively.
1 reply 0 retweets 3 likes -
Replying to @sebmck
Your original tweet compared Firefox to Chrome without showing what Chrome does, making it pointless, undescriptive and non-actionable. Heck, it didn’t even say in which context the error happened. Could have been a userland throw for all we knew.
1 reply 0 retweets 0 likes -
Replying to @nokusu
I will reply to my tweet with the Chrome error when I get a chance. I’d encourage you to reevaluate how you engage with people. It’s unnecessarily hostile and doesn’t assume good intent. I don’t even know why I replied to your first bait tweet.
1 reply 0 retweets 3 likes
Sebastian Retweeted Sebastian
There you go buddyhttps://twitter.com/sebmck/status/1155854708180783104 …
Sebastian added,
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 