Twitter effectively doesn't have an API any more (what they do have is prohibitively expensive for tinkering).
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.
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 https://firehose3d.theo.io/ discussed previously: https://news.ycombinator.com/item?id=42159786
I've always felt like the API enabled us to make Twitter a ~success, back before it had critical mass.
I built a small literary journal on early Twitter, and knowing we had a simple way to archive what we were publishing and do stuff like bio-driven contributors notes was a big part of why it made sense to bother investing creative energy on a new platform and social capital convincing writers to make accounts.
It's been frustrating to watch the past few years. I haven't fully decided if I have the energy to reinvent it for a new platform, but poking around at atproto stuff earlier this fall made me more hopeful about the prospect than a similar draft I have on top of gotosocial (even though thw former ia much further from complete).
> I wish there was a way to force users to use 1 hashtag per post and then I could unfollow hashtags - but I suspect it would be playing wack-a-mole.
I built something like this in a slightly different context for myself.
I doubt it'll ever really catch on widely, but I have a bunch of people who want to read my highlights about tech and nothing else who appreciate my software dev feed.[1]
I was thinking something similar. I want to post #PRQL #dataBS #DataEngineering #OpenSource #Excel #PowerQuery ... I assume each of my followers is only interested in a subset of those tags. I've been considering setting up separate accounts that probably fragments too much.
Great thing about Bluesky is that you can easily create your own custom feeds so I guess we can just start doing it and see if it catches on.
Gemini 1.5 Flash 8B is so cheap now that you could build your own little custom Bluesky reader that filters out political tweets for you based on LLM classification. It would probably cost less than a dollar a month.
Not only do bluesky users(skeeters? did that catch on?) not tag posts correctly they do that "anti censorship" thing where they share a screenshot of a post so you are guaranteed to see things you don't care about.
I tried doing that with Twitter a few years ago in an attempt to reduce the amount of posts related to US politics. I don't follow any political figures or commentators, only tech people and artists, but about half the posts on my feed were about US politics.
Although I ended up with a blocklist of around 100 words it was very much a losing battle and a waste of time.
> 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.
I noticed the same thing about AI in the Nix community. Was really surprised by the extreme negative reaction, as I could see so many applications of AI that could be useful in the Nix ecosystem.
I don't see how it's surprising at all, given the current climate of overmarketing and overpromising on "AI" in tech. The most realistic applications are also the most straightforward - academic cheating, machine-generated "art," mediocre automated customer support, and so forth.
It's surprising because I thought Nix users were more discerning and not caught up in binary thinking. Just because it's overhyped doesn't mean it doesn't have any uses or should be rejected completely. I just solved a dnsmasq and systemd issue today in a 3 minute chat with Claude-sonnet 3.5 that I had been banging my head against for 6 hours. Why wouldn't I try to harness that?
Sorry, I'm not part of the Nix community so I don't have the context to answer that. Although I would infer from "so many applications of AI," you meant more than just technical support chatbots.
Projects should just bite the bullet and say "AI friendly" so those conservative anti tech users can pre-emptively be pushed away. Might hurt adoption but better than holding back progress.
One of the reasons i don't use bluesky much is coz they came out swinging anti AI
Twitter effectively doesn't have an API any more (what they do have is prohibitively expensive for tinkering).
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.
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 https://firehose3d.theo.io/ discussed previously: https://news.ycombinator.com/item?id=42159786
Here's my own quick firehose demo: https://tools.simonwillison.net/bluesky-firehose - code here: https://gist.github.com/simonw/af2e50446f6dfc5cb514a7d6aadbb...