![]() ![]() ![]() This initial version of ChromeDeck, though not yet as fully-featured as the current desktop client, is the start of an exciting new venture for us and we really hope you love it. We have taken some of the best aspects of our award-winning desktop client and melded them with the best design and features from our hugely successful Android app, to make a state-of-the-art app web app, built on technologies such as HTML5, CSS3 and Javascript, that marks the beginning of a new phase for TweetDeck. And of course, it’s totally free!Ĭhrome TweetDeck, or “ChromeDeck” as we have dubbed it, is a huge step forward in terms of design and flexibility. Users of Google’s Chrome web browser can now visit the Google Web Store and download a brand-new, built-from-scratch, Chrome-specific TweetDeck app. We are thrilled to announce that today, with the launch of the brand new Google Web Store, we are starting to realise that ambition. We wanted a full-blown TweetDeck experience that brings the power and feature set of the desktop client but in a really cool web framework. I have heard things not working because of the clock being more than an hour or day or year off, but not 5 minutes.For a long time we have had an ambition to create a web-based version of TweetDeck, but only if we could make it totally awesome. Nothing, and I mean nothing has ever prevented me from doing anything because my computer time was 5 minutes off. The network time is 5 minutes fast, and every so many hours, the network does a sync refresh causing my computer to be off 5 minutes again. Ensure that you have set valid consumer key/secret, access token/secret, and the system clock is in sync.Ĭould it be that simple? I do have an issue with the time on this computer that is connected to a network. The following ( yellow highlighted part of the) sentence stood out like a sore thumb.Ĥ01: Authentication credentials () were missing or incorrect. ![]() a 401 Authorization Error? Wait! What?ģ) I then started Googling the issue, and upon my second website visit, I found the issue. It was defaulted already to Console and was monitoring the extension. I then clicked the background.html link.Ģ) This brought up the Chrome Developer Tools Window. Here is what I did that helped determined my problem:ġ) I right-clicked the plugin and clicked Manage extensions. I remembered that the problem started happening when Twitter announced changes on February 7th, 2017. The problem always existed (on my end), so it had something to do with a change to Twitter’s website that introduced the error. After 30 minutes of trying other things, I FINALLY figured out the problem. Very annoying! I mean, I read fast, just not that fast.ġ week later, I decided to reinstall the plugin again thinking that maybe Twitter fixed something at their end. I liked it except for the fact that I always had to have it up and running in Chrome to get my notifications, and I couldn’t lengthen the notification timeout to more than 2 seconds. I won’t bore you with everything else I tried.Īfter 3 days, I decided to use the Chrome TweetDeck. NOTHING!Īnd worst of all? It works on my other computer that has the same operating system. I uninstalled the plugin and reinstalled the plugin. Within the plugin options, I clicked the Logout button, and then reauthorized the app. Instead of a notification for a tweet, I got this instead:Ĭlicking the tweets in the plugin worked okay. Okay, so I got this plugin for Google Chrome.Īfter a year of using the plugin, the Notifier for Twitter plugin stopped working. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |