5 ms·

I never relied on Twitter's API, since building stuff with it is akin to building your castle on other people's land. You're always going to be a tenant, and th

I never relied on Twitter's API, since building stuff with it is akin to building your castle on other people's land. You're always going to be a tenant, and the API gatekeepers play landlord and can rugpull you without notice. But I'm looking into Nostr[0] as an alternative, aswell as ActivityPub which seems to be working well these days. Dorsey's Bluesky Social[1] looks promising too, but it's a very late move since Twitter should have been a protocol from the outset. [0] https://nostr.com/ https://nostr.com/ [1] https://en.m.wikipedia.org/wiki/Bluesky_(protocol) https://en.m.wikipedia.org/wiki/Bluesky_(protocol)

x86x87 4y ago
This is not the first time twittet screwed developers. If you're olf enough to remember they did this shit in their early day when they had the real possibility of being social media's message bus. Corporate greed took over and capitalism won / they pulled the plug on developer apis. Up until that point they flourished. Now with new wind in their sails generated by 45 and more recently by the technoking they have forgot the lesson and doing the same mistake. Twitter is nothing without its ecosystem. They are killing the same env they need to survive.
- rsynnott 4y ago
  > they have forgot the lesson They haven't _forgotten_ it, Saint Car is _ignoring_ it. People in Twitter would absolutely be aware that the last attempt (which for all its problems was still infinitely more ordered and less user-hostile than this one, of course), didn't go so well.
  - x86x87 4y ago
    Saint Car? That induced a permanent chuckle.
kcplate 4y ago
> I never relied on Twitter's API, since building stuff with it is akin to building your castle on other people's land This is a wise attitude. I can’t imagine any company whose existence is wholly reliant on another single organization not entering into an agreement with the said single organization to protect itself. I feel sorry for them, but damn…you need to protect your product.
A4ET8a8uTh0 4y ago
I am glad you brought it up, but it is the reliance on API provided by any company can be changed, restricted or rescinded at will. The mere fact that APIs have become so commonplace has always struck me as problematic ( and became more apparent during some of FB depositions ). You are effectively relying on a goodwill of another entity. You can have zero to no expectation that it will serve you today or tomorrow just because. Can we return to dumb protocol designs? No? Oh well, I guess we did not suffer enough yet then. edit: All this twitter drama may actually result in useful changes to to the net.
sixothree 4y ago
Why would I even need a twitter client when the experience of using twitter is going downhill. I think the API being shut down should be the least of his worries.

x86x87 4y ago

This is not the first time twittet screwed developers. If you're olf enough to remember they did this shit in their early day when they had the real possibility of being social media's message bus. Corporate greed took over and capitalism won / they pulled the plug on developer apis. Up until that point they flourished. Now with new wind in their sails generated by 45 and more recently by the technoking they have forgot the lesson and doing the same mistake. Twitter is nothing without its ecosystem. They are killing the same env they need to survive.

rsynnott 4y ago
> they have forgot the lesson They haven't _forgotten_ it, Saint Car is _ignoring_ it. People in Twitter would absolutely be aware that the last attempt (which for all its problems was still infinitely more ordered and less user-hostile than this one, of course), didn't go so well.
- x86x87 4y ago
  Saint Car? That induced a permanent chuckle.

kcplate 4y ago

> I never relied on Twitter's API, since building stuff with it is akin to building your castle on other people's land This is a wise attitude. I can’t imagine any company whose existence is wholly reliant on another single organization not entering into an agreement with the said single organization to protect itself. I feel sorry for them, but damn…you need to protect your product.

A4ET8a8uTh0 4y ago

I am glad you brought it up, but it is the reliance on API provided by any company can be changed, restricted or rescinded at will. The mere fact that APIs have become so commonplace has always struck me as problematic ( and became more apparent during some of FB depositions ). You are effectively relying on a goodwill of another entity. You can have zero to no expectation that it will serve you today or tomorrow just because. Can we return to dumb protocol designs? No? Oh well, I guess we did not suffer enough yet then. edit: All this twitter drama may actually result in useful changes to to the net.

sixothree 4y ago

Why would I even need a twitter client when the experience of using twitter is going downhill. I think the API being shut down should be the least of his worries.