Twitter About to Kick out Tweetro from Windows Store?


Recommended Posts

Let me just start by saying that I am very disappointed in Twitter. Well, we know that with Twitter?s updated version of the API, new developers are limited by Twitter?s new and strict API rules. As I understand it, the new API only allows up to 100 thousand user tokens, after which a program trying to access additional user tokens must consult twitter for permission. This means for third party twitter clients, it can only have up to 100 thousand registered users without needing Twitter?s approval. The latest victim of this new enforcement appears to be the very popular Windows 8 app, Tweetro.

Richard Hay, a Microsoft MVP, reports that Tweetro has sent out emails to subscribers notifying that they can no longer accept additional users. You can read the full content of the letter on his post.

Tweetro developers contacted twitter, but, so far, they have not received a response. They are considering pulling the app from the Windows Store and resubmitting it as a ?premium?, and likely expensive, app. This will limit the number of users. They explain that while they ?would have been more than happy to continue distributing Tweetro for free as the exposure [they?ve] been receiving from it has been fantastic however being limited by twitter to a maximum of 100,000 users would mean [they?d] have to justify development via financial means.?

Windows%20Store%20Reviews.png

Anyway, as you can see from the screenshot of the user reviews of the Tweetro app on the Windows Store, users are rating it one star because they can?t connect to twitter. Granted, they don?t know that it?s not Tweetro?s fault, but Twitter?s, but they shouldn?t have to. The ultimate goal for consumer technology is following the motto ?it just works?. It?s not the user?s job to decide who is at fault. If it doesn?t work, the users are not happy. I feel deeply sorry for the Tweetro developers, as they have done an amazing job in creating this app, only to be crippled by Twitter. I also feel bad for users because in the end, the users loose.

Anyway, here are some pictures of Tweetro for those who hadn?t been lucky enough to be the first 100 thousand users.

2%20Home%20Screen.png

4%20Built%20in%20Web%20Browser.png

7%20Options.png

Damn bro, calm down, go take a couple chill pills.

/thread.

Nothing he said requires calming down or the taking of any "chill pills".

  • Like 3

Pretty annoyed about this as well. No app - minus the official app - is immune to this silly 100K user limit until Twitter smartens up. The premium app is simply there to artifically cap the user limit, and it too will be in trouble over time.

Really if Twitter would get their heads out of their arses and have some condition in their API like make third party apps relay sponsored tweets or else they face the 100K limit, then we wouldn't be here, with Tweetbot charging $20 for their Mac OS X app for instance.

Tweetro works fine for me. Am I missing something?

Yeah, don't ever log out or uninstall the app. If you do then you'll see the problem. :p

If Tweetro becomes a "premium app" many users will switch to MetroTwit and then they will end up hitting the token limit. :/

MetroTwit will end up hitting the token limit regardless of Tweetro being paid or not. Since they're already at the limit, and people are having problems connecting, they'll move onto the next app until that next app hits its limit and so on.

Why doesn't either one of them just sell-out to Twitter so they can be the official Windows 8 app? It happened to Tweetie, remember?

That isn't really up to them to sell to twitter, twitter would need to want to buy them which they don't as AFAIk they already have an official client in the works.

Also weren't both of these apps out before the 100k limit?? If they were then aren't they allowed to double whatever their numbers were at the time the limit came into play if they already had more than 100k users?

This topic is now closed to further replies.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!