vicwalker.dev.br
+3
-3
SANDBOX.md
+3
-3
SANDBOX.md
···
18
18
19
19
The sandbox environment is intended to test infrastructure, but user content may be created as part of this testing process. Content generation can be automated or manual.
20
20
21
-
Do not post content that requires active moderation or violates the [Bluesky Community Guidelines](https://blueskyweb.xyz/support/community-guidelines).
21
+
Do not post content that requires active moderation or violates the [Bluesky Community Guidelines](https://bsky.social/about/support/community-guidelines).
22
22
23
23
## Keep the emphasis on testing
24
24
···
93
93
94
94
# Learn more about atproto federation
95
95
96
-
Check out the [high-level view of federation](https://blueskyweb.xyz/blog/5-5-2023-federation-architecture).
96
+
Check out the [high-level view of federation](https://bsky.social/about/blog/5-5-2023-federation-architecture).
97
97
98
98
Dive deeper with the [atproto docs](https://atproto.com/docs).
99
99
···
139
139
140
140
We’re not actually running a Bluesky PDS in sandbox. You might see Bluesky team members' accounts in the sandbox environment, but those are self-hosted too.
141
141
142
-
The PDS that you’ll be running is much of the same code that is running on the Bluesky production PDS. Notably, all of the in-pds-appview code has been torn out. You can see the actual PDS code that you’re running on the [atproto/simplify-pds](https://github.com/bluesky-social/atproto/pull/1198) branch.
142
+
The PDS that you’ll be running is much of the same code that is running on the Bluesky production PDS. Notably, all of the in-pds-appview code has been torn out. You can see the actual PDS code that you’re running on the [atproto/simplify-pds](https://github.com/bluesky-social/atproto/pull/1198) branch.