I just append everything after the twitter.com domain name to https://nitter.net to read the tweet in question.
For example, the tweet this HN post links to could be read without javascript here:
YouTube -> Invidio.us
Instagram -> Bibliogram
Google Maps -> OpenStreetMap
reddit.com -> old.reddit.com or i.reddit.com
[0]: https://addons.mozilla.org/en-GB/firefox/addon/privacy-redir...
This domain is dead, I currently am using invidious.xyz
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.
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.
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.
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"...
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.