Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document federation requirements #1465

Open
Tamschi opened this issue Nov 10, 2024 · 1 comment
Open

Document federation requirements #1465

Tamschi opened this issue Nov 10, 2024 · 1 comment
Labels
feature Features and feature requests that are specific to Bridgy Fed, not fully described by the protocols. now

Comments

@Tamschi
Copy link
Collaborator

Tamschi commented Nov 10, 2024

This is a follow-up to #1463.

It would be good to document specific federation requirements for remote networks, i.e. that fed.brid.gy must be federated with in addition to bsky.brid.gy or web.brid.gy and (or?) individual custom domains of bridge accounts.

The explanation should mention 'limited federation mode' to make it easier to discover for Mastodon admins.

@Tamschi Tamschi added the feature Features and feature requests that are specific to Bridgy Fed, not fully described by the protocols. label Nov 10, 2024
@snarfed snarfed added the now label Nov 10, 2024
@snarfed
Copy link
Owner

snarfed commented Nov 10, 2024

Yes! This would be part of a bigger "I'm an instance admin, what do I need to know?" section that I want to write. Will do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Features and feature requests that are specific to Bridgy Fed, not fully described by the protocols. now
Projects
None yet
Development

No branches or pull requests

2 participants