Lemmy MultiPass
I had hoped to be able to do this with mostly API tricks and leveraging existing data structures within Lemmy's database... but I think it's proving that August 2023 isn't the right timing. I learned a lot by prototyping this and thinking about multi-person editing like moderators can do in a community...
I did get permission to share this private message. For the record, I loath having public Lemmy topics being discussed in private messages. I created this community to get all this OUT in the OPEN. I already made my decision on NOT changing privacy policy. But now I see that the very idea of having more than one "Subscribed" list for an end-user is raising threats of defederation! ![](https://lemmy.ml/pictrs/image/e2619ec1-1d21-4e70-aab7-c0784845c296.png)
The design will route around and avoid ANY sharing of any personal information that is already in Lemmy. I don't want to get into new user preferences for opt-in - too many Rust changes and API changes that front-ends would have to implement. I'm specifically trying to make this project small enough that it can be implemented.
Yes, inspired by... https://www.youtube.com/watch?v=9jWGbvemTag ------------------------------ ---------------------------------- Lemmy MultipPass is a proposal to implement a system for: 1) sharing subscribed communities list publicly. 2) Creating specific MultiPass community lists that are not owned by any one person but instead managed like a Community with multiple moderators. You may know the concept of “MultiPass” as “MultiReddit”, multiple subreddit viewing. Basically a way to build a subscribe community list that is shared. Right now, Lemmy 0.18.4 era has only you personal subscribe list or a single community.