4 ms·
You're not paying for the feature, you're paying for the UX, which is gated behind their unusable API (so it's impossible for a 3rd party app to achieve parity
by Nav_Panel 5y ago
You're not paying for the feature, you're paying for the UX, which is gated behind their unusable API (so it's impossible for a 3rd party app to achieve parity with the 1st party app).
- manquer 5y agoIn this case it is quite easy, like delayed send third party app need not make the API call until n seconds after the tweet to give you time to undo the change. Sure twitter may not do it client side and have special APIs etc, however ultimately they can also really do only limited time changes, other wise the tweets already read by others would start changing. Of course they can still pull API access for violating ToS etc, however from technology context there is nothing they can do .
- Nav_Panel 5y agoThe point isn't that a third party UI can't do this, it's that it can't do many other things that the native UI can, so people won't even switch.