In case you're a Twitter client, you've seen the t.co area the organization utilizes: It reworks all URLs in tweets to go through this diverting space to track "engagement." It needs to know how often connections are passed—apparently, it could likewise channel against malware and spam, however I've never seen such a system locked in.
However, for a considerable length of time, some Twitter clients in OS X have had an issue with t.co in Safari. Rather than diverting, the connection results in an interminably stacking page that times out. Reloading the page results in a non-existent area. Reload once more, and the destination URL at last loads.
What's up with that? No one knows! Or possibly, no one did. I took a gander at years of discussion postings all over in which individuals noticed the issue, and nobody had a reliable arrangement. That shows up going to change.
An Apple architect who chips away at the WebKit group—the innovation underneath Safari—as of late tweeted because of surely understood Mac designer Rich Siegel and engineer and podcaster John Siracusa that the issue has been distinguished, and a fix is in progress. So alleviation is coming.
Meanwhile, designer Stef Pause prescribes a charge line fix you can issue in Terminal, in the event that you have the stomach for it! Enter the accompanying and squeeze Return:
dscacheutil - flushcache
This charge dumps the area name framework (DNS) reserve, which is a provisional vault of generally as of late recovered qualities for connecting comprehensible space names with the genuine numbers and different bits of Internet pipes required for associations. Delay composes that it may should be entered different times.
Another alternative, in case you're utilizing Tweetbot for OS X is to change a setting by means of Terminal that turns off URL revamping. (This tip by means of Dermot Daly on Twitter.) Enter this summon and squeeze Return:
defaults write com.tapbots.TweetbotMac OpenURLsDirectly YES
No comments:
Post a Comment