There are two accounts that pop up when you start typing "atproto" in a username field: @atproto.com and @atprotocol.dev, conspicuously titled AT Protocol Developers and AT Protocol Community respectively.
This will clear up the confusion caused by the handle saying .dev but the screen name of the @atproto.com account being the one that says AT Proto Developers.
5
$type
pub.leaflet.pages.linearDocument#block
block
$type
pub.leaflet.blocks.header
level
2
facets
plaintext
Links
6
$type
pub.leaflet.pages.linearDocument#block
block
$type
pub.leaflet.blocks.text
facets
plaintext
The two main community spaces are the forum and discord. Both have nice shortlinks but they are confusingly different, especially given the overlap mentioned above.
7
$type
pub.leaflet.pages.linearDocument#block
block
src
https://discourse.atprotocol.community
$type
pub.leaflet.blocks.website
title
ATProtocol Community
description
A community space for coordinating, convening, and collaboration around ATProto
Make sure links to community spaces are easily discoverable by prospective community members and builders. Namely the forum and the discord server. We can even do this on protocol! @woosh.link is a linktree-like app made by @aka.dad. I've put a redirect on my domain for links.tyn…
Put a links link (woosh) in the @atprotocol.dev Bluesky bio, which in turn links out to the discord and forum.
17
$type
pub.leaflet.pages.linearDocument#block
block
$type
pub.leaflet.blocks.text
facets
plaintext
The advantage of a links link would be we could feature more links without cluttering the bio. Upcoming event pages, spotlight blog posts and community efforts, fundraising links, all sorts of stuff!
18
$type
pub.leaflet.pages.linearDocument#block
block
$type
pub.leaflet.blocks.header
level
2
facets
plaintext
Website
19
$type
pub.leaflet.pages.linearDocument#block
block
$type
pub.leaflet.blocks.text
facets
0
index
byteEnd
76
byteStart
62
features
0
uri
https://atprotocol.dev
$type
pub.leaflet.richtext.facet#link
plaintext
I realize as I go through all of this that the web blog is at atprotocol.dev and there is nothing at atprotocol.community. I think as this community grows we will need to quickly shed any focus exclusively on devs.
20
$type
pub.leaflet.pages.linearDocument#block
block
$type
pub.leaflet.blocks.blockquote
facets
0
index
byteEnd
49
byteStart
29
features
0
uri
https://atprotocol.community
$type
pub.leaflet.richtext.facet#link
plaintext
change the website domain to atprotocol.community and redirect any old .dev links to .community
21
$type
pub.leaflet.pages.linearDocument#block
block
$type
pub.leaflet.blocks.text
facets
plaintext
If it becomes useful later to use the .dev domain for dev specific resources and spaces, sure use it. If we are going to have one main space for our community (across different platforms like discord and forums and whatever comes next), I'd rather the namespace focus on community…
22
$type
pub.leaflet.pages.linearDocument#block
block
$type
pub.leaflet.blocks.horizontalRule
23
$type
pub.leaflet.pages.linearDocument#block
block
$type
pub.leaflet.blocks.text
facets
plaintext
That's all I've got for ya for now. Lmk what you think.