Hey everyone! I’ll be going through and making features for the site soon (as I’ve almost got my laptop back) and wanted to know if there was any features that are wanted that I dont already have noted down

I’m currently planning to do:

  • Customizable icon shapes (circle, hexagon, etc.)
  • Flairs
  • Ability to block an instance
  • Ability for admins or community mods to hide communities from the all feed
  • Community short descriptions (to show in the community list + top of sidebar)

And polls are also being worked on by snowe

Will try to get the changes merged into lemmy itself as well but they’ll be released here first

    • mark@programming.dev
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      I’ve always felt like the blocking should happen at the user level and muting should be at the instance-level. Feels odd for admins be able to prevent users from seeing content.

      • Reader9@programming.dev
        link
        fedilink
        English
        arrow-up
        8
        ·
        1 year ago

        Feels odd for admins be able to prevent users from seeing content

        My understanding is those admins aren’t just allowing users to view it but also allowing copies of the federated data to be stored on the server those admins are responsible for, so for certain types of content it seems really important to be implemented in this way.

        • mark@programming.dev
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          edit-2
          1 year ago

          We’re talking about blocking all content on an instance though–not necessarily a few nasty communities or posts or users. Blocking an instance blocks all content, including non-offensive content that may be posted by legitimate users.

          For an admin to block everyone on an instance from all of their users just because of a few bad actors still seems weird to me. It’s just gonna lead to every instance blocking each other, which destroys the experience for users and defeats the point of federation.

          • Reader9@programming.dev
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Good point and I agree with the downsides. Giving admins more granular ways of hiding content sounds healthy.

            There’s also the important distinction between admins finding opinions on the other instance “disagreeable” and muting vs. illegal content in the instance server’s jurisdiction and those of the admins. Defederating the whole instance does seem harsh if the problem is within specific communities only and doesn’t deal with illegal content.

            Difficult problem!

  • mark@programming.dev
    link
    fedilink
    arrow-up
    9
    ·
    1 year ago

    This is great news! What happens if the Lemmy devs dont accept the changes upstream, though? 🙂

      • mark@programming.dev
        link
        fedilink
        arrow-up
        6
        ·
        1 year ago

        Oh ok seems fine as long as the code continues to merge cleanly with upstream. But once that stops happening, could be hard to continue development without branching off and going our own way.

        Will the custom code be open source and made available to us? If so, where would that be?

        • Ategon@programming.devOPM
          link
          fedilink
          English
          arrow-up
          7
          ·
          edit-2
          1 year ago

          Yeah should be fine, dont think any changes made are going to severely overhaul the base structure so everything will be able to merge in (and if it does change then makes sense to branch off at that point)

          Yeah it’ll be in a github repo. Currently trying to brainstorm a name and then I’ll share the repo publicly

          • tatterdemalion@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            and if it does change then makes sense to branch off at that point

            I really hope it doesn’t come to that. I don’t want to become a fork of Lemmy. I would consider going to a different instance if that happened, because I would need to weigh pros/cons of sticking to OG Lemmy dev team or programming.dev team.

            • Ategon@programming.devOPM
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Yeah very unlikely to actually happen. Even if it branched stuff could be shared between them, just would have to be adapted a bit

    • philm@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      I don’t think this will be a very big issue for the majority of the cases though. As long as it’s configurable and not a (very) controversial change. Especially, since I don’t think that feature requests on a programming focused community will be that much controversial…

      What I have observed so far: I think the maintainers are relatively open to changes (compared to a few other open source repos).

    • philm@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Pretty sure, that there’s already a github issue on lemmy itself (too lazy currently to search it though)

      • WierdWebDev@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        ah sorry, I was just going off the list in the OP. I’m fairly new here. (ah, i see “on lemmy itself,” I’m not totally clear on how that works but that makes sense.)

          • WierdWebDev@programming.dev
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            My thoughts on show/hide “read” is that I don’t necessarily want to hide all that i’ve read, not do I want to read all that I want to hide. I might want to keep some “read” ones on the feed in the event they get new posts.

  • graphito@beehaw.org
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 year ago

    Just listing some features I find valuable, some of them got issues already

    • Migrating communities to another instance
    • Ability to subscribe to communities in bulk
    • Notification for new communities on particular instance
    • subscribe to post replies when you’re not the poster
    • mentions by username notification
    • subscribed + local/all feed together
    • local/all feed without subscribed
    • mark as read on posts
  • canpolat@programming.dev
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    This is great. I think “instance post/comment links” would be a great addition to Lemmy core in general, but don’t know how easy it would be to implement. What I have in mind is: when someone provides a link to a post/comment in another instance, it would be converted to a link the person is logged in from. I think it would be OK to leave the link as is but add an icon next to it that goes to the correct URL for that instance.

    • Ategon@programming.devOPM
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Yeah no idea how that would be connected. I know theres an extension that does it so I might need to look at the source for that

      • canpolat@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I believe there is an API to convert such a link, but detecting that a link is going to a Lemmy instance might be difficult (or non-elegant).

        • cacheson@kbin.social
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Should be able to just compare against the list of known instances. It’ll miss the ones that aren’t connected yet, but that should fix itself once someone subscribes to a remote community on the missing instance.

          • canpolat@programming.dev
            link
            fedilink
            English
            arrow-up
            4
            ·
            1 year ago

            Yeah, that’s what I meant by non-elegant. I think the way Lemmy assigns IDs to posts and comments should be re-thought. Dictionary lookup is a solution, but not a good one.

            • cacheson@kbin.social
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              Hmm, yeah, I see what you mean. Wasn’t thinking about having to convert the IDs. Plus the actual local copy of the post needs to be available, not just a connection to the remote instance.

  • qwertyasdef@programming.dev
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    No idea how hard it would be but it would be nice to have code blocks with syntax highlighting like on Github, so you could write something like

    ```python
    def f(x):
        return x
    ```
    

    and get syntax highlighted code def f(x): return x

    • Ategon@programming.devOPM
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Yeah also have that planned as one of the first things I put in since we’re a coding site, forgot to put it on the list. Shouldn’t be that bad since there’s libraries for it