Freedom to run 3rd party clients

The concept of client freedom refers to the ability to use third-party clients with APIs, akin to the open protocols of the past like email and IRC. This freedom has diminished since the 1990s, particularly with the rise of closed protocols in platforms like Twitter and Discord, which explicitly prohibit third-party clients. The author reflects on the loss of client freedom, recalling a time when services like Facebook Messenger allowed third-party access through XMPP. The current landscape poses risks for users of third-party clients, as companies can implement traffic analysis and ban accounts without recourse. The author expresses a desire for Twitter to embrace client freedom, suggesting features like RSS feeds for lists, batched notifications, and a simplified tweeting experience. They are willing to pay for a tier that allows the use of third-party clients against a stable API. The preference for native apps over single-page applications (SPAs) is highlighted, emphasizing performance and uniformity in design. The author critiques the trend of companies prioritizing control over user experience, noting that while closed protocols can evolve quickly, they often lead to a decline in user satisfaction as monetization strategies worsen the experience. Ultimately, the author longs for a return to a more open and user-friendly digital environment.

- Client freedom has declined since the 1990s, with many platforms now using closed protocols.

- Users face risks when using third-party clients, including potential bans without appeal.

- The author desires features that enhance user experience on platforms like Twitter.

- There is a preference for native applications over SPAs due to performance and design consistency.

- Companies prioritize control and monetization, often at the expense of user satisfaction.