i think the only way for atproto to succeed is for us to show what apps can do when every app sees every other app's public data, and they share an identity system. no technical or sociological argument is as convincing as seeing seamless interop and the lighthearted competitive landscape it unlocks
>Now that we have a name 50% of the work is done. so real RE:
haha that's fun RE:
i wish pdsls also let you look at everything grouped by a collection, in addition to by repository. i understand that this would either require an index of the entire network or for volunteers to host the corresponding Slices. but i think it would be a nice way to explore the network. the global db
i have an idea for a fun little atproto app. so my question is… uhh what should i know. i know the β€œlinks between data should be at:// uris” thing. are there other important design principles like this? for backend i was planning to use [@slices.network]( ) and/or maybe [@microcosm.blue]( )
roam on atproto when
wahhh this is so good RE:
"the semantic web is already here" too spicy for a blog post title?
skills are a sick concept, love it RE:
[@zed.dev]( ) annoying bug: cmd+P doesn't work right after opening a project (with no open tabs)