Ok, taking a total fresh approach based on all the months I’ve been reading people’s suggestions and !lemmywishlist@lemmy.ml kind of things…

All / All Remote / Local / Remote Specific-Isntance

I think server operators should at minimum want the ability to view Remote-only, and even per-instance. Further, I think proxy of API to a community should be something to head towards… where a Lemmy API call can be forwarded as an API call on another Lemmy server for a specific community.

Small, Medium, Large, Trending, Featured Community

Some stock multi-community lists, some of which are dynamically generated like Small / Medium / Large based on number of active posts, users, or other tunable parameters. Encourage people to engage in topics that they normally would not see…

Multi-community sharing

I think foundation is that it should use words and not numbers. Right now, the entire Lemmy system is built upon using localized index numbers for community. Even if it just becomes a JSON blob to throw into PostgreSQL and recall by name…

Maybe have them like communities. And people can subscribe/unsubscribe to a specific list. And the list can have moderators who regulate it (editors). And an option to clone a list to new name.

/mc/ multi-community, name. And no ID numbers. A Trigger or something would have to build the ID numbers in the background.

And a browser of these, much like communities are browsed… and maybe even voting on them. Lemmy doesn’t have voting on communities - subscribe alone - but sometimes you don’t want to subscribe because they have too much content - but you would still vote for it or recommend it.

  • RoundSparrow @ BT@bulletintree.comOPM
    1·
    1 year ago

    ok, what’s really the easiest way to do this?

    1. create a community, set it hidden…
    2. create a person, set it as bot account. associate the person as owned by the community…
    3. Allow switching to another person for a session. Create posts, comments, subscribe/block/unsubscribe/unblock from that person.
    4. Most important, list posts as that person you switch to. That has to be available as read-only to anyone.
    • RoundSparrow @ BT@bulletintree.comOPM
      1·
      1 year ago

      The problem is that I don’t think follow of community and block of community gets federated to other instances/servers (other than the home for remote communities). So a downstream instance wouldn’t be able to view a person’s community whitelist and blacklist. Fundamentally, the data isn’t there.

      Humm. Then there is the issue of not wanting to create any new federation protocols.

      A community can be created, published, and inside that community a message that gets edited with the list… but then only the person who creates a post can edit a post.

      Is the only entity that gets fully replicate the list of moderators for a community? And a community itself. We could edit the community to have a list inside it.