 I am considering a Bluesky approach to @loops, but in ActivityPub! What I mean is that it will be vital to auth, discovery and the algorithmic FYP, for Loops to provide a centralized service and make it easy for users, while also allowing admins to opt-out and limit their Loops instance accordingly. We can have the best of both worlds, and who knows, we may even support native AtProto eventually! The goal is to empower short form video sharing, wherever possible! Are you with us? 🚀 6 comments
@dansup
Centralised authentication. So, a server that controls all users and instances that are responsible for operation? @feb no not centralized auth, but centralized auth features like being able to tell which server you are on. You would login to your server directly, the centralized features I mentioned would only be an optional layer between your server and the fedi, not you and your own server! I should have made that more clear.  @dansup @feb not particularly happy about the idea. This should be either a client feature (browser plugin could help here) and/or server support for the nomadic identity features that are being worked on in other Fediverse platforms https://wedistribute.org/2024/03/activitypub-nomadic-identity/ (see the OpenWebAuth in particular) |
Gregory's Server
@dansup @loops What does this mean for people that might want to run their own loops server? What parts/services are necessarily centralized?