-
Notifications
You must be signed in to change notification settings - Fork 52
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
allow connecting accounts #38
Comments
I don't really have any use cases in mind that connecting accounts like this would serve. Open to ideas though! |
Documented on https://brid.gy/about#connect |
One thing I thought of about this since opening #1194; I don't know how Bridgy's crawling/polling is actually implemented, but for people who connect multiple social networks to a single website, it seems like Bridgy ends up crawling their website separately for each of those networks. Connecting accounts could ease the number of crawling operations Bridgy has to do, but that also seems like something you could solve independently if the amount of crawling ever becomes concerning to you |
True! Good point. Polling h-feeds for syndication links is a relatively small amount of Bridgy's total load, but you're right, we could consolidate it for web sites with multiple silo accounts. And you're also right that we could do that with or without the kind of UI connection described in this issue. |
e.g. for the same person's accounts on each silo. could use indieauth to also let them attach their domain, but not strictly necessary.
The text was updated successfully, but these errors were encountered: