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.
@jerry You may find them terribly rudimentary, but you're welcome to use our configs, and I've been looking for experienced admins to discuss the challenges it presents for these apps. I think it could ultimately render something that better empowers users, but until then it clearly gives administrators more power to root users to the instance. I'm on Matrix at @bobbyd0g:hellsite.net . Don't mind the senseless utulalia in the readme -- https://github.com/bobbyd0g/commlab
