Ok. The roster so far is:
Infosec.exchange (mastodon)
pixel.Infosec.exchange (pixelfed)
video.Infosec.exchange (peertube)
relay.Infosec.exchange (activitypub relay)
risky.af (alt mastodon)
What’s next? I think I promised some people here bookwyrm
Sigh. I forgot one. The REAL roster so far is:
https://Infosec.exchange (mastodon)
https://pixel.Infosec.exchange (pixelfed)
https://video.Infosec.exchange (peertube)
https://relay.Infosec.exchange (activitypub relay)
https://risky.af (alt mastodon)
https://Infosec.press (writefreely blog)
@jerry Do you have any plans for SSO? We used Keycloak for Mastodon / PeerTube / Matrix and it certainly unfolds a new world of complications
@bobbyd0g I started using mastodon’s oauth provider - Infosec.press uses it. I expect to move peertube and pixelfed to it as well. It’s not ideal, but the ideal case would have been to use keycloak from the start.
I am considering another set of instances that start from the ground up using keycloak, though.
@mikemacleod @bobbyd0g I believe you would be directed to keycloak to create an ID, which would then allow you to login to Mastodon
@jerry @mikemacleod Keycloak has basic signup and login flows built-in, they are about as slapped-together as could possibly be on Hellsite.net and it works. New users sign up for Keycloak, and as soon as they visit each app with that auth, it creates an account with the same username. And so, obviously, begin the complications! :) Migration and integration should be greatly assisted by Keycloak's mapping config & SAML/LDAP support
@bobbyd0g @jerry very interesting. Will peruse the repo you linked elsewhere in the replies later. I’ve been intending to play around with a self-hosted instance.