Someone has probably mapped out some sort of cycle to this ......<p>Stage 1: new product, hungry competitor wanting eyeballs and users opens up their platform to developers....<p>Stage 2: developers embrace the attitude and start building amazing things...<p>Stage 3: the company starts to not like seeing all these products make use of its user base and platform<p>Stage 4: API features wound back<p>Stage 5: developers uncermemoniously dumped, API closed<p>Stage 6: platform hits rocky times, new management arrives, claims to be reborn, reopen platform API to developers<p>Stage 7: skeptical developers hold back<p>Stage 8: platform charges $30,000/month for bottom level access<p>Fool me once, etc etc
Such a weird timewarp feeling around this stuff. It's like you could go dig up an archived Twitter dev post from 2008, find and replace and post. What a time to be alive (again)
This could be interesting.<p>Twitter effectively doesn't have an API any more (what they do have is prohibitively expensive for tinkering).<p>Mastodon has a culture that actively pushes back against many of the things people might want to build - any experiments with things like search or discovery improvements or even potentially algorithmic feeds tend to get a very hostile reaction from long-time Mastodon users.<p>Bluesky's API is wide open for innovation right now - and you can even connect directly to a WebSocket stream (from JavaScript running on any page) for direct firehose access, like in this demo <a href="https://firehose3d.theo.io/" rel="nofollow">https://firehose3d.theo.io/</a> discussed previously: <a href="https://news.ycombinator.com/item?id=42159786">https://news.ycombinator.com/item?id=42159786</a><p>Here's my own quick firehose demo: <a href="https://tools.simonwillison.net/bluesky-firehose" rel="nofollow">https://tools.simonwillison.net/bluesky-firehose</a> - code here: <a href="https://gist.github.com/simonw/af2e50446f6dfc5cb514a7d6aadbbc03" rel="nofollow">https://gist.github.com/simonw/af2e50446f6dfc5cb514a7d6aadbb...</a>
How do you crawl or backfill the existing data?<p>Like if you wanted to implement a search engine or recommendation system it’s not clear to me how you retrieve a training set.
Nope. They want the all in one app/solution.
And they want people to work for free to essentially build that one app to rule them all.<p>This is a nightmare for every still independent software/web developer.