If a service can't keep its own status page up (Twitter's has been an SSL cert error for months), you should perhaps consider not using it for yours.
If a service can't keep its own status page up (Twitter's has been an SSL cert error for months), you should perhaps consider not using it for yours.
Enter through an alternative front-end (https://nitter.com/SlackStatus) and you should see more status from this year.
Would be nice if they were adding a Mastodon account, but I can't blame any company that chooses to retire Twitter presence at this point.
The algorithmic stuff was only ever for users' feeds, not Twitter profiles.
It's made the whole business of status updates completely unusable. If I want to find out why the fire helicopters are out, I can no longer see that on the fire department's Twitter page (even though they do post it!). If I want to find out if my local lake is closed due to algae, I can no longer see it on the park's page (even though they do post it!).
Pretty soon all these organizations are going to realize that their pages are worthless and leave Twitter.
a) Favouring blue-tick comments and post over those with higher engagement.
b) Paying people to comment which has meant more click-bait, hate etc. content.
I don't think this is a very fair and honest take on the toilet flush spiral where Elon Musk placed Twitter. Screwing up the timeline made available to non-registered users is a recent development, and one that lands squarely on Elon Musk's rule over Twitter. So does the shitshow that was the verified badge policy changes and opening the floodgates to racist and anti-semitic content.
In fact, I dare say that there was not a single change to Twitter that spawned from Elon Musk's takeover that had any positive or neutral impact on the company in general and service in particular.
Providing a status monitor/canary page does not force anyone to register an account or subscribe to a service. They can provide all sorts of push/pull notification options they can conceive. Once Elon Musk's Twitter restricted access to their API I'm afraid Twitter lost any relevance for this type of use case.
When I go to most Twitter pages, now, I see completely random posts from years ago at the top.
Slack users should be using https://status.slack.com/ in any event.
The real problem with walled gardens is that people actively avoid going outside the wall. Who is actually not going to Slack's own status page when slack is down? People who would rather be wrong than inconvenienced.
There are many bad things about how Musk is running Twitter, but the UX for people not logged in is pretty low on the list.
If I'm a random person who just heard that Joe Biden tweeted something, I can't see that tweet by going to his Twitter page. That's a pretty goddamned terrible experience right there.
It's also not clear that I'm just seeing the most popular tweets — no other social network has that experience for logged-out users.
I agree wholeheartedly that Twitter shouldn't be the primary vehicle for official communication from just about anything (except maybe Twitter itself).
This can be anything from websites announcing maintenance to a public safety announcement. For example, the district I live has a disaster announcement account on Twitter.
At least for people here, using Twitter only for status updates while not logged in is a very common thing.
Not just in Japan.
But the practice, much like the one of using Facebook or other such service exclusively, has always been a Very Bad Idea. Perhaps such entities will finally abandon it entirely.
Very assuring to know Elon jeopardized the reliability of the service for cost savings
Although I do enjoy the sublime wonder of how between Twitter and the Twitter clones everyone in this space has concluded that to display a 280 character text message they require somewhere between a full Javascript web app or that and an account. It is a pity that HTML is not up to the challenge of these hard times.
This is blatantly false. In the past, Twitter links, both to tweets and to user timelines, were widely shared through third-party services, including major news outlets.
I don't want to use a third-party client to access a fucking website for it function logically.
I want X to always show me the most current post someone has made. I'll decide to scroll down on my own if I want.
This is also why I don't use it much. To be fair, Twitter had this same problem - at least so far as I can remember, it did. I didn't see much value in Twitter and I don't see much value in X, at least not in it's current state.
Maybe that'll change.
The issues you mentioned were not engineering problems. They are all Product Manager diktats. Screwing over the timeline of non-authenticated users is a business requirement, and one which Elon Musk's Twitter decided to change recently.
They started doing this a few months ago. It means if you want to see a persons latest tweets, you have to login/create an account. It's infuriating. A stupid growth tactic. My workaround for now is using Nitter. I can see how businesses linking to their Twitter (e.g. as a source for 'updates' on anything) would have issues with this.
It's a dark pattern, and one which only the most desperate services implement as their last desperate attempt to force users to register and login at the expense of eliminating any value the platform has to them.
9/10 times TLS cert errors are bad cacheing, clashing between browser cipher suites, bad intermediates/roots being on devices etc. Especially on mobile, more especially on android.
But, I also can't find this status page you mentioned. So maybe I'm missing it and twitter actually is incompetent?
This one? https://api.twitterstat.us/
Seems fine now.
Looks like Twitter have just quietly deprecated this page, given that it's powered by a completely different service.
Is there anyone left working there at all, or is it just Elon roaming the empty corridors as Jason Calacanis follows him telling him how marvellous he is?
The company renowned for their CEO using a pocket knife to unplug servers straight from the server room is not expected to do stellar work managing certificates.
I saw the common name on the cert and the redirect and was like, oh ok so they wanna move away from this domain then, makes sense.
It didn't cross my mind that what they were redirecting to could have an invalid cert as well...