by LyalinDotCom on 12/18/20, 5:49 AM with 187 comments
by bArray on 12/18/20, 6:47 AM
> 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.
by nullify88 on 12/18/20, 8:27 AM
curl -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://google.com/bot.html)" "https://twitter.com/zarfeblong/status/1339742840142872577"
Peak SEO when users are faced with more friction than Googlebots and crawlers.
by shakow on 12/18/20, 11:27 AM
by bonoboTP on 12/18/20, 10:01 AM
I still gave it because I'm a little guy and want to get the benefits of being tapped into my professional community, to know what's up, to be visible myself etc. Such individual decisions result in this.
We users have a hard time coordinating as we have individual incentives while Twitter is one entity and can do whatever it decides.
by herbst on 12/18/20, 9:25 AM
by zarfeblong on 12/18/20, 7:37 AM
I know (in principle) how to use curl to send an authenticated API request via HTTP. That's authenticated; you have to log in. I already have a twitter client for that use case.
There's also unauthenticated API access (read-only public tweets only, as you'd expect). (I assume this is what nitter.net is doing.) Less tracking, but you still have to request an API key, so it is under Twitter's control and they could in theory cut it off. It's still not supporting the basic web principle of "you can GET the flippin' data".
Anyhow, I'm glad this is getting some public attention. I'm a little surprised that I was the first one to make a fuss about it.
by Tipewryter on 12/18/20, 6:53 AM
How hard would it be to write a centralized 1-to-many message pipe that replicates Twitters core functionality?
How hard would it be to run such a thing? The moral and legal needs to censor content would probably be a bigger task then the technical implementation?
by ThePhysicist on 12/18/20, 11:48 AM
For a while already I had the idea of building a "diet social media" software that would display information from e.g. Twitter, LinkedIn, Facebook and other platforms without gamified addiction mechanisms. Turns out this is impossible to do as all platforms have drastically restricted the way you can consume their data.
by cblconfederate on 12/18/20, 7:59 AM
by dvfjsdhgfv on 12/18/20, 10:44 AM
by kilroy123 on 12/18/20, 12:39 PM
by cyberCleve on 12/18/20, 11:56 AM
by ffpip on 12/18/20, 7:03 AM
by X-Istence on 12/18/20, 9:35 AM
It sucks, because it adds a new refresh cycle just to see the tweet.
by specialist on 12/18/20, 3:56 PM
I expect an RSS style newsreader. I just want to see what's new, in order.
IMHO John Carmacks' old school finger file updates was the pinnacle of human achievement. Just aggregate everyone's finger updates into a swanky offline mail reader style UI. Heaven.
I don't understand why links aren't links. eg Open this in a new tab.
I don't understand why pull quotes are images.
And tellingly, I don't care enough to figure it out, find a better way.
PS- One thing missing from Twitter is the drive-by downvote. Too bad.
by BlueTemplar on 12/18/20, 10:36 AM
by rhn_mk1 on 12/18/20, 9:30 AM
by ArcVRArthur on 12/18/20, 5:46 PM
Just replace the twitter.com part of the tweet URL.
by throwawaysea on 12/18/20, 8:02 AM
by known on 12/19/20, 7:12 AM
by mellosouls on 12/18/20, 6:56 AM