Does anything stops devs from using the Web interface instead of the API? Sure it makes it a bit more challenging because parsing is involved but AFAIK it is completely legal to parse and display HTML output however you want. It's essentially like a browser add-on.
I wonder if Twitter can be killed by the "embrace, extend, extinguish" strategy?
So:
1. Make a client that combines Mastadon/Others and Twitter feeds, making it switching out of Twitter frictionless.
2. Provide extra functionality for non-Twitter posts, encouraging the use of the non-Twitter services.
3. Once have a good traction, penalize Twitter post to further push non-Twitter adoption. Eventually remove Twitter support completely.
I wonder if Twitter can be killed by the "embrace, extend, extinguish" strategy?
So:
1. Make a client that combines Mastadon/Others and Twitter feeds, making it switching out of Twitter frictionless.
2. Provide extra functionality for non-Twitter posts, encouraging the use of the non-Twitter services.
3. Once have a good traction, penalize Twitter post to further push non-Twitter adoption. Eventually remove Twitter support completely.
4. Profit??