4 ms·
Call for Developer Projects
- mcyc 2y agoSuggested projects for the AT Protocol from the Bluesky devs.
- simonw 2y agoThis could be interesting. 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/ https://firehose3d.theo.io/ discussed previously: https://news.ycombinator.com/item?id=42159786 https://news.ycombinator.com/item?id=42159786 Here's my own quick firehose demo: https://tools.simonwillison.net/bluesky-firehose https://tools.simonwillison.net/bluesky-firehose - code here: https://gist.github.com/simonw/af2e50446f6dfc5cb514a7d6aadbbc03 https://gist.github.com/simonw/af2e50446f6dfc5cb514a7d6aadbb...
- abathur 2y agoI'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).
- colordrops 2y ago> 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.
- kkarakk 2y agoProjects 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
- computably 2y agoI 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.
- colordrops 2y agoIt'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?
- computably 2y agoSorry, 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.
- tomjen3 2y agoI find that I want the opposite of the firehose: I want the thoughtful and smart people, and I want it to be about their interests. I did sign up for bluesky, but it has the same failure as twitter: I don't want to hear about your politics just because I follow you. 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. Really anything that aims to replace twitter should be forced to not optimize for engagement.
- bsnnkv 2y ago> 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] [1]: https://notado.app/feeds/jado/software-development https://notado.app/feeds/jado/software-development
- snthpy 2y agoI 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. 1: https://docs.bsky.app/docs/starter-templates/custom-feeds https://docs.bsky.app/docs/starter-templates/custom-feeds
- bsnnkv 2y agoSo I actually just went ahead and made the thing[1] for Bluesky. https://blucerne.app https://blucerne.app
- kkarakk 2y agoNot 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.
- faizshah 2y agoHow do you crawl or backfill the existing data? Like if you wanted to implement a search engine or recommendation system it’s not clear to me how you retrieve a training set.
- bob_theslob646 2y agoThis is a great question and I am looking for the answer as well.
- hasheddan 2y agoThere is a page[0] in the Bluesky docs on this, though it effectively boils down to “fetch each user repository”. [0] https://docs.bsky.app/docs/advanced-guides/backfill https://docs.bsky.app/docs/advanced-guides/backfill
- ChrisArchitect 2y agoSuch 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)
- andrewstuart 2y agoSomeone has probably mapped out some sort of cycle to this ...... Stage 1: new product, hungry competitor wanting eyeballs and users opens up their platform to developers.... Stage 2: developers embrace the attitude and start building amazing things... Stage 3: the company starts to not like seeing all these products make use of its user base and platform Stage 4: API features wound back Stage 5: developers uncermemoniously dumped, API closed Stage 6: platform hits rocky times, new management arrives, claims to be reborn, reopen platform API to developers Stage 7: skeptical developers hold back Stage 8: platform charges $30,000/month for bottom level access Fool me once, etc etc
- morkalork 2y agoYup, major déjà vu here. Great for students wanting to make a cool demo project and getting a job and forgetting about it after, bad for just about everyone else.
- steveklabnik 2y agoThe difference is that it's impossible to wind API features back: as an open protocol, they literally cannot do that. "The future company is an adversary" is a slogan the team uses to help guide decisions.
- computably 2y agoI'm curious as to what you mean by > as an open protocol, they literally cannot do that. From a cursory search, it seems the AT Protocol is solely maintained by Bluesky. Also, AFAICT, Bluesky operates the only sizable/relevant servers. i.e. Neither the governance nor the technical operation are decentralized. (edit: Although the OP call for projects includes options which would probably lead to further decentralization, that doesn't speak to the present state.) Note that I find it reasonably credible that Bluesky won't do that. I just don't see why they cannot. If there is a massive incentive to make backwards-incompatible protocol changes, say a fundamental security flaw, wouldn't the expected outcome be that Bluesky unilaterally makes those changes?
- 2y ago
- lakomen 2y agoNope. 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. This is a nightmare for every still independent software/web developer.
- paulcarroty 2y agoAnother Twitter with SMS verification paywall - nope, thanks.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- tempodox 2y agoNope. I've been screwed by Twitter already. Fool me once, ...
- bermestdema2016 2y ago[dead]