One that I’d like to see is a more in-depth sorting option for posts (allowing you to see for example top of December 2020, or top of a specific day). A custom date range selection would be best. I remember this being a frequently requested feature in the early days of reddit, and they never implemented it.

  • riccardo
    link
    fedilink
    arrow-up
    11
    ·
    4 years ago

    Can’t you already do that? As long as the instance federates with the one hosting your account, you can subscribe to its communities

      • nutomicMA
        link
        fedilink
        arrow-up
        4
        ·
        4 years ago

        Any idea how? Local and remote communities are shown in the same way, and both have a subscribe button.

        • zksmk
          link
          fedilink
          arrow-up
          4
          ·
          edit-2
          4 years ago
          1. Adding a Federated tab on the front page, so it’s Subscribed/Local/Federated/All, would help.

          2. Allowing sorting communities on the communities page by subscribers/category/userspermonth/etc by clicking on the relevant column name and having one of the columns be “instance”, would help. Sort the instances automatically alphabetically or by total userspermonth or posts of all of its communities combined or whatever in the background.

          3. Adding the community@instance.tld and instance.tld/c/community search syntax.

          4. Adding a small “What is Lemmy and how does it work” tutorial link under the signup/login button. Could be just a “Help?” button. Leads to a simple page that explains the federation concept in layman terms. I prefer the simple “public email” comparison, most people seem to get that quickly.

          5. Maybe federated communities shouldn’t be shown the same way. Maybe they could have a small “federated” tag next to the name that stands out, in the default theme color scheme css this could be a green background on the “federated” text of the tag. It’s important users notice at a glance they can access federated communities from here on lemmy.ml (or whatever instance they’re on).

          • nutomicMA
            link
            fedilink
            arrow-up
            1
            ·
            4 years ago

            Those sound like good ideas, would you mind opening issues for them in the lemmy-ui repo? Ideally a separate issue for each point.

            • zksmk
              link
              fedilink
              arrow-up
              2
              ·
              4 years ago

              Sure, will do (when I find some time).

            • zksmk
              link
              fedilink
              arrow-up
              1
              ·
              4 years ago

              Hey, I’ve opened separate issues for all of these on the repo, but Dessalines closed them all saying all these features already exist (even tho they don’t). Maybe I annoyed him somehow by not formatting something correct/not following some etiquette (it’s my first issue on GitHub) even tho I just filled in the templates. I did end up linking the issues by mentioning them in each other, I thought it would be helpful. Should I just leave this to up to you guys to resolve this internally?

              • DessalinesA
                link
                fedilink
                arrow-up
                1
                ·
                4 years ago

                You need to open up individual issues, not 4 issues with identical text. And if you think something isn’t closed, then respond why.

          • nutomicMA
            link
            fedilink
            arrow-up
            4
            ·
            4 years ago
            1. Yes, but its sorted by subscribers, and for remote communities we only know the number of subscribers from our instance, not the total number. So they will be shown far at the bottom. Actually this could be fixed as we send the subscriber count over activitypub, feel free to open an issue.
            2. No, chapo.chat runs an older version of Lemmy where federation isnt really working.
            3. Both communities will be completely separate.