Twitter Killing Its Mac App

Where do I go to add my "this is a dumb decision, Twitter should fix its botting/fake account problem" take?

For me at least the killer feature in the twitter app is the global hotkey I can press to hide/show it: when I have 5 seconds of downtime I can press the hotkey, read three tweets, and then send it away. Great for filling short pauses while other things load or I'm waiting for a response from someone.

Fortunately Tweetbot has that same feature now, so I've switched to it.

A better UI. As every native app does. Yes, in principle web apps can do more, from drag & drop to .. stuff. But in practice they never do, they never go the extra mile but instead just building for the lowest common denominator.

Also the dock spot is important for my method of using windowing. The browser is for websites. I wouldn't want to mix it. I could banish twitter.com to a wrapper window with Fluid, but it's still just a crappy web app. I use Tweetbot instead. And before that Tweetie for Mac. Which was killed today. Fingers crossed that the API survives.

Native app launchers (which you can stick into the taskbar/dock/etc.) are built into Chrome.

• Windows: https://www.laptopmag.com/articles/how-to-create-desktop-sho...

• Mac: https://productforums.google.com/forum/#!topic/chrome/3A5ZTe...

What this feature doesn't do, is to track the tabs spawned by launching the application shortcut using that taskbar item/dock icon/etc. Instead, you just get a new window spawned in the Chrome application's window-group.

This is really a failing of our desktop window managers, not of web browsers: we need to separate the semantic concepts of "process" and "application", such that one process can be responsible for driving several applications, and choosing to "quit" an application can just result in an IPC message being sent to the process telling it that the user wants that window-group-context gone, rather than telling the window manager to go terminate the entire process.

(Such a feature would also greatly help with things like managing "non-rooted" Remote Desktop or X11 or virtual-machine windows. Right now, some of these use a workaround of generating a stub binary to register each foreign application for the local DWM's sake. But it's a leaky abstraction: Alt+Tab/Cmd+Tab to the proxy "application", and the RDP client/X server/VM "app" gets focus instead. If window-groups—with metadata for the name and icon of the "application" they represent—were something a process could publish to a DWM, rather than something the DWM tried to determine heuristically about an application process, all of these problems would go away. And, even without offering this up for webapps to use, browsers would benefit from this change: Chrome's "profiles" are exactly separate "application" window-groups in the same sense as apps under an X server or VM process.)

> Chrome

I'd rather not, thanks.