7,223 karma · joined November 6, 2011
The substantive difference is that we didn’t do a mix & match spec process because we knew the ambiguity of spec support causes problems, just as it did with XMPP. Protocol specs only get implemented a few times. The meaningful developer choices are in schemas and business logic.
Bluesky is building an open internet protocol (https://atproto.com) and a flagship social app (https://bsky.app). We're a company of 30 with a strong focus on fostering a high-agency, talented team. The golang roles are focused on building the internal platform with a whole lot distributed systems engineering; the ML is working on our many recommender systems and feeds; the RN & fullstack engineers are working on the social app and internal moderation tooling, respectively.
If you think social media - and the internet - could be better, apply here: https://bsky.social/about/join
I can understand why artists who enjoy the non-con kink dislike this policy, but I think people can also appreciate where this policy comes from. I can also understand why other NSFW artists are anxious that they need to indicate consent, but there is, unfortunately, some amount of judgment that the moderation team has to make on whether something is violative noncon.
EDIT: also fwiw, I got my start in 2012 working on ssb and then in 2013 on dat, both of which were conceptualized as bittorrent variants. Atproto has a pretty clear lineage from that p2p work. You just can't do large scale social computing on user devices.
We're hiring ML Engineers, ML Ops, Data Scientists, and DevRels. Golang and python for the ML roles; golang and typescript for devrel.
It's fully possible to stand up the network on your own infrastructure, and to communicate with other providers