> We've detected that JavaScript is disabled in this
> browser. Please enable JavaScript or switch to a supported
> browser to continue using twitter.com. You can see a list
> of supported browsers in our Help Center.
So long then, Twitter.
Consider for a minute the number of services/programs that just got screwed, the number of people on slow internet connections they just cut off, the number of people on low-end mobile devices that just lost access to local community discussions - the list goes on.
Was it really so much to ask for a basic HTML interface to display text and images? In terms of resources, surely this is quite easy to support? I've been using mbasic.facebook.com without JS for years, for example. Sure, some features are screwed, but for the most part it works.
You can use this [0] browser plugin to automatically redirect to Nitter. You can also choose which instance to redirect to, or to choose an instance randomly every time (for load balancing). Also supports:
Open Street Map is not a replacement for Google Maps. Not even close. It's a different product with overlapping features. As a detailed map, it's vastly superior. As a way to find locations and information about them, it's not nearly as good.
+1 for nitter.net. In recent years, Twitter started to block public proxies and Tor aggressively, if an IP address is rate-limited, all accesses are denied. Worse, because of JavaScript, it only denies access after the script has given up after spending 60 seconds. And even when I'm not blocked, the script is still slow, and if you accidentally refreshed the page while in the middle of an endless scrolling, you'll have to try again. Nitter.net solves all the problems at once. I don't use Twitter but I do maintain a list of people in tech, which I check from time to time.
You don't even have to be using Tor to get blocked like this; I get rate limited fairly regularly just following Twitter links on my phone while on mobile data. I suspect it's because my carrier is doing CGNAT and I share an IP with several other users.
Makes it annoying when someone links to Twitter as usually I'll have to sit there refreshing a few times before I can actually see it.
There are a bunch of different instances running the nitter software too, so please consider choosing another one to avoid hugging nitter.net too much. Here's the list: https://github.com/zedeus/nitter/wiki/Instances
nitter is really the way I want to consume tweets (I'm not even on twitter but have my bookmarks to existing topics e.g. twitter lists and users that I tune into still - users that I used to follow when there - I used to follow hundreds but those that keep me coming back aren't more than 5). twitter without an account is twitter without the noise or risk of getting sucked into "contributing" (e.g. riling myself up lol)
Sadly, when you submit links from nitter to HN they get automatically demoted (they won't even have a discuss link and will never see the frontpage).
I don't know the reasoning but I guess the argument could be that
- it violates original content rule (that official sources must be used).
- some engineering just went into HN to show the user-name part of twitter posts in submitted links. (I took that as a reasoning why HN prefers twitter links rather than nitter - suppose that could easily be expanded though).
- potential legal reasons (? I can't think of any but maybe HN respects the claim of twitter that the data belongs to them etc ...)
just speculation but fact is there is no nitter support on HN.
I love Nitter, but I can't help but feel like it's on borrowed time. Eventually Twitter is going to decide it's a problem.
The day Nitter is killed is likely the day I stop using Twitter. Yes, I know you can host your own, but if Twitter decides to actively fight against it the best case scenario is an annoying cat and mouse game that makes the service unreliable.
That's not fair. Someone put a lot of time and effort into that spinning wheel animation. By removing the need for JS the tweet now loads too quickly for it to be seen!
BTW messenger over mbasic.facebook.com stopped working for me last week and throws errors. Am I the only one? The only web way to use FB messages for me now is the bloated desktop web experience (which takes 10s+ to load)
You are not the only one. I've used other browsers on my android to use facebook over m.facebook.com, but about a week ago Facebook Messenger messages was disabled with an error message and also the alternative mbasic.facebook.com was crippled for me. So anyone messaging me have to wait until I'm at home.
Their ordinary web experience since the latest(?) change of UI is horrible, notifications takes forever to render forcing a full page refresh to get back working.
Thx for data point. Android 11, Chrome 87, "content not found" for me at the same URL.
I'm connecting from France, I'm wondering if it's maybe EU-only thing related to FB's latest rollout of "we disable some stuff for EU users to be GDPR compliant"...
There's Messenger Lite, I think meant for low internet connection speeds and free of a lot of bloat. Hopefully the antitrust lawsuit will keep Zuck from getting too egregious and getting rid of that too, but who knows.
mbasic not working here either. I suspect it's connected to the "Some features are not available" shown on the desktop-browser messages UI. Something to do with complying with European legislation.
I'm currently based outside the EU and US, perhaps it is as you say. I'm not entirely sure why the privacy rules would change so drastically on a HTML based page though...
> Was it really so much to ask for a basic HTML interface to display text and images?
Yes; it allows automated mass aggregation of hard, accurate, and current information, which is not only non-ideal from profit perspective but also for maintaining community active and/or engaging
> browser. Please enable JavaScript or switch to a supported
> browser to continue using twitter.com. You can see a list
> of supported browsers in our Help Center.
So long then, Twitter.
Consider for a minute the number of services/programs that just got screwed, the number of people on slow internet connections they just cut off, the number of people on low-end mobile devices that just lost access to local community discussions - the list goes on.
Was it really so much to ask for a basic HTML interface to display text and images? In terms of resources, surely this is quite easy to support? I've been using mbasic.facebook.com without JS for years, for example. Sure, some features are screwed, but for the most part it works.