Twitter's website is absolute garbage, the feed is unresponsive, tweets fail to load, it's just terrible. If you're modeling your frontend off of anything please do not pick Twitter because their web experience is awful.
I rarely experience any of these issues and think their front end is quite good. Just their a11y / keyboard nav stuff is some of the best I've seen. Some questionable design choices but that's more of a product thing
I was under the impression this was an intentional dark pattern to get users to sign up / log in to twitter? The reason I believe this is because if you get that failure and back out and click the link again it works 100% of the time.
I would think that your first visit loaded a resource/set a state somewhere which let's the second visit go through.
Much more likely to be a programming error then a purposeful decision by a PO as the end result is objectively terrible. I cannot imagine anyone getting convinced to register to a webpage that cannot even load. It's not that content is hidden behind a pop-up or anything, it just errors out (at least for me, but I'm not the parent comment author)
GTA online has had slow loading times for years until a fan reverse engineered the game to find a bad serialization issue which basically created a n*n computation.
Some issues are fucking hard to detect and an initial page load breakage that only happens sometimes (likely a race condition that cannot be replicated in testing) is an example of that
Tweets not loading, with an error, except after several tries, is a commonly-reported problem. I've seen it for years, across multiple browsers & devices, happens all the time.
You literally can't use the site properly when you're not logged in (and I mean basic clicking on retweeted/quoted stuff shows a login page, clicking on people's names shows a login page etc.) - how is that good? (I mean sure, build your walled garden as you please, but then you have no business showing in search engine results.)
I've been encountering this a lot today, because apparently the MTA (and the Metro North) have decided that Twitter is their official news distribution channel [0]. They're posting updates there more frequently than they are on their official website, and because we're in the middle of dealing with a hurricane, they're pushing me to interact with Twitter to figure out how to get home tonight.
Apropos of that: the MTA is using threads now, and I can't click 'show thread' without being redirected to a login screen. I don't want to create an account because I find twitter painfully shallow but also addictive, as well as generally untrustworthy (I don't want them to have my phone number).
I don't think that any part of the government should be using twitter the way the MTA is; but so long as they are, I think Twitter would do well to get out of the way of the distribution of vital info.
governments should be strictly prohibited from requiring privacy-invasive (tracking, deanonymizing) technology for any service, let alone emergency services. a gov website requiring google fonts, apis, captcha and tracking is not in accordance with the basic civil right of being free of government surveillance (via said 3rd-parties).
It's close, but browser support & integration was never good enough, and that lacks the ability to carry on a dialog or to attach one's own post to someone else's, which people clearly want.
Any move to develop it further to add those sorts of things would have run into the same problem other protocols have for the last 20+ years, which has made them even more difficult to develop and promote than they already were: keeping huge numbers of users captive has become per se valuable, thanks to having as-complete-as-possible spying-generated profiles on people and massive datasets being important both to the money-spigot of the modern online ad market, and for developing machine-learning solutions to dominate other "verticals" (against any competitor who lacks the same massive, spying-obtained datasets, so is at a huge disadvantage). Application-level open protocols make tracking & spying harder, so companies chasing those datasets really don't want them around. The few that survive in common use do so under constant threat, protected only by luck, by already being "good enough", and by having already established a large presence before that sort of business model really took off.
[EDIT] incidentally, pioneering the inclusion of an open, cross-site social network as a first-class browser feature is one of my crazy ideas for how Firefox could save itself from irrelevance—but like most of the other ideas I have to save them, it's probably too late anyway.
Agreed, it's very heavy for no reason given it's doing pretty much nothing. It's buggy, slow, sluggish at times, with delay on clicks and scroll. It's really a terrible UI given how simple the problem is, and how much money they got.
It's not like they have 1000 of concurrent events like facebook, and their frontend should have nowhere the complexity of their backend. I don't understand how it's even happening.
The most absurd aspect of it is that how slow loading a single tweet is. The timeline could have the excuse of a slow and complicated backend call (but it doesn't, the backend is actually doing ok), but several seconds for one single tweet?
The thing that drives me crazy is that it breaks a basic feature of the browser, which is that if you load a bunch of tweets in your feed and then ctl-f to search for something, it doesn't work (on Chrome, at least); it doesn't find stuff that's on the page.
This is particularly frustrating, because my normal use case for this is that a bunch of new stuff loaded, which throws everything that's on the page already out of order, so then I can't see something that I know was there, that I was just looking at, and now searching for it doesn't work, either.
Yep, it breaks a ton of standards and UI expectations, I don’t know where people get off saying it’s good for accessibility. (Sorry, a11y.) Don’t reinvent the back button!
You're so right about this. Also their UX is absolutely horrible in my opinion. It's one of the worst designed sites both in terms of usability and load time (half the time it doesn't even load on my mobile on kiwi browser).
The biggest irony is they have the best designers in the world (i.e. the guys who created bootstrap) but god I hate the tech they have used to make twitter.com because of that "something went wrong" retry button error message .
My only complaint about Twitter on desktop web is that the feed auto updates itself. And it always happens just when I'm watching a video or I'm about to click on something...
I wish they still did server side rendering for your feed. They switched to all client rendering a while ago and it takes a lot longer to load now. I wonder if the loading speed tradeoff was consciously made or if it was just a fait accompli after some rewrite or another.
I feel like an idiot trying to read threads on Twitter. I seriously get confused on where one begins, ends and everywhere in between. It's WAY too complicated of a layout for nothing more than a chronological list of text.
I have no affiliation with this site(1) but it is godsend if you're trying to read twitter threads. Makes you wonder why they can't have this in-built in twitter instead of what it is now.
Which is probably a good thing. Neither of those sites wants you to "stay engaged" and keep scrolling forever. Old reddit was the same, but of course the redesign is infinite scroll.
They have been trying to kill their web experience longer than most other modern platforms have been alive. The latest iteration of that is requiring a Twitter account to see any posts at all now.
Can't find the tweet now. Someone created a static HTML page with all their tweets, over 8 MB of HTML. It rendered faster than a single tweet by Twitter.
I pulled some raw twitter yesterday for the first time in a very long while. The amount of general purpose, world-wide javascript junk was hard to look at.. not as densely scrambled as Google js output in the past, but the number of special cases for "media in Taiwan" or whatever else, just went on and on.. per-tweet
The tweets not loading is clearly intentional. They want you signed in, preferably on a native client where they can track more invasively.
That said, I fully agree - the website is literal garbage despite its insane simplicity, and there would be 0 reason to trust that their web tech works well because they have never demonstrated such a thing.
I built one of those. Twitter's API isn't going to do you any favors. There is no publicly available API to get the replies to a tweet. So building out a full thread is hard. Then once you figure out how to use their internal API you'll quickly hit rate limits </3