You may have a network issue. The first suggestion you'd find on Google would be to restart your router!
>Linking tweets like this is not really helpful to building an understanding of the issue for outsiders.
The tweet threads in question have exactly the context needed to understand part of the reason why someone resigned in the GitHub thread, from someone who isn't anonymous in the rails community, unlike my hn account.
I could copy paste them into a Medium article but I had linked them because they are informative regardless of your opinion on Twitter as a medium.
No, twitter's frontend code is garbage. It routinely does this (at least on Firefox), and -sometimes- works on a refresh or a hard refresh. It's been this way for years.
Regardless if something is really serious, then compile the relevant/important stuff into a blogpost instead of making people wade through random tweets.
"A quick Google would recommend you turn router on and off again."
It's not a router issue, but thank you for assuming that I am unable to do basic internet searching. I have debugged this issue in the past as it occasionally occurs (for specific tweets only, twitter itself works well), and my conclusion is it's something on twitter's end.
"Why don't you do that if it's so necessary?"
I'm not the one submitting this on HN, am I? If I were, I wouldn't have linked random tweets. I wouldn't be tasking the commenters to compile the information into a usable format for me.
There's nothing actionable here, this just looks like some tuesday morning drama.
>Linking tweets like this is not really helpful to building an understanding of the issue for outsiders.
The tweet threads in question have exactly the context needed to understand part of the reason why someone resigned in the GitHub thread, from someone who isn't anonymous in the rails community, unlike my hn account.
I could copy paste them into a Medium article but I had linked them because they are informative regardless of your opinion on Twitter as a medium.