Issues · LemmyNet/lemmy
github.com
🐀 Building a federated link aggregator in rust. Contribute to LemmyNet/lemmy development by creating an account on GitHub.

While @nutomic@lemmy.ml and I do have a lot of issues that are going to take us a lot of time this upcoming year, its still useful for us to hear what your most desired features for Lemmy are, and prioritize them.

If they’re smaller, we could get to them fairly quickly, or others wanting to contribute could see whats most wanted.

Outside of just posting them here, make sure github issues exist for them (this is what we work from), and do a thumbs up react for all the ones you’d like. Despite being a popular project, we have very few people voting on these issues . We can then use the link above (issues sorted by most thumbs up ), to keep track.

Thanks all.

    •  Dessalines   ( @dessalines@lemmy.ml ) OP
      1•2 years ago

      We could add helpers in the ui, like the one we have on the create post page for using an archive link. But overall I’d like a link aggregator to remain mostly agnostic about the links being posted ( we also do remove some tracking / utm params tho ).

      The other thing is there are many of these 3rd party viewers, and they go down quite often and leave dead links. We’d use it if someone made a rust or js library for it tho.

  •  Arthur Besse   ( @cypherpunks@lemmy.ml ) 
    3•2 years ago

    Human readable URLs! The URL is a very important part of a site’s user interface, and lemmy’s URLs currently just have a post number - there is no title, or even the name of the sub-community. Compare this to reddit: when I paste a friend a reddit URL in chat they get two hints about what it is about: the subreddit name, and the post’s title, both embedded in the URL itself. This lets them decide if they want to click it now, or later, or never, or to recognize if they’ve already seen it. Lemmy links should be like that.

  •  CHEF-KOCH   ( @CHEFKOCH@lemmy.ml ) 
    0•2 years ago

    An option to block someone from commenting in your community to avoid trolling.

    Entrance only if followed or based on specific levels…

    • Needs x amount of months membership on Lemmy to comment.
    • Needs x amount of comments or and post submissions.

    This would also help fighting spam and trolls with alt-accounts to create an account, troll-up here, down-vote everything + shit-post. Since you could restrict voting as well with the idea.

    •  Dessalines   ( @dessalines@lemmy.ml ) OP
      1•2 years ago

      We recently added private communities, and might eventually add some new user limitations… but I’m very wary of reputation or gamified based systems, or one that isn’t welcoming for new users. It’ll need lots of discussion before we add anything like that.

  •  Evan   ( @Cloak@lemmy.ml ) 
    0•2 years ago

    REPOST!!!11

    1. How can we make the federated Lemmy more seamless? The in message community mentioning syntax, for instance, could use refinement
    2. How can we support different languages better?
    3. Is it possible to avoid the space for radicles that comes with federated platforms while still maintaining the values that a federation stands for?
    4. Working out minor quirks that lower trust, like the 502 page when logging out, randomly being logged out until you reload, no css occasionally, and the free .ml [[domain]] for the flagship instance

    Than, how can we attract users, specifically from different countries?

    The first thing that comes to mind before advertising is attracting other communities from Reddit, but why would they come? Voat attracted members because the alt right was unwelcome on reddit, but most communities dont find a huge need to switch, even if they feel things could be better. The one exception is the privacy/Foss community, but it’s a small one and perhaps not the best Target audience, let alone one of many nationalities.

    If the above paragraph was somehow an attraction plan despite no internationality, some more issues would need to be ironed out:

    1. can we offer reddit import?
    2. can we make a compelling offer for everyone
    3. can we have an attractive landing page

    In line with 3, I think at some point some branding consideration is needed, ie

    Lemmy: a world for everyone

    With an illustration of stuff being shipped between different planets, one covered in flowers, another in factories and tech, and one more with ???

    As an idea.

    I am interested in your strategy ideas for growth. While I am rambling, worth noting that a democracy system is my long term dream, although far off in the pipeline

  •  Zalamander   ( @Zalamander@lemmy.ml ) 
    0•2 years ago

    I would be happy to see client-side password hashing implemented.

    I understand that responsibility of using unique passwords falls on the user, and maybe a truly malicious instance would be able to remove the hashing (although I think that it would be possible to check if non-hashed passwords leave the client). However, the reality is that many people still re-use their password for many websites and do not use 2FA when not required. Password hashing would reduce the level of trust required of the instance makers.

    On a similar vein, it would be nice to anonymize the ip addresses that are printed to the docker logs if possible, similar to the nginx logs. I think that this would be easier to undo for a malicious instance, but at least they would need to have a bit more technical knowledge to get to this information.

      •  Zalamander   ( @Zalamander@lemmy.ml ) 
        0•2 years ago

        This protects the database from a breach, but someone can set up an instance and collect the passwords from the logs:

        As far as I can tell with my very limited experience, back-end encryption is the standard. One trusts the host not to steal their passwords from the logs, so protecting the data in the case of a breach is good enough. I think that it would make sense for the standard in the Fediverse to be different. Passwords should be encrypted by the client by default, and then re-hashed back-end.

        It is also possible that what I am saying does not make sense in practical grounds - this is just something that surprised me while looking through the logs. I was under the wrong impression that plain text passwords were never accessible before looking into this topic.

        •  Dessalines   ( @dessalines@lemmy.ml ) OP
          1•2 years ago

          We’ve recently removed that logging line, which logged all websocket requests. But yes most importantly, the database stores no plaintext passwords.

          You don’t want to client side hash passwords before sending, because different clients might not do it the same way. But also we have to add oauth at some point, so 3rd party clients don’t even have to know your pass. This is less important with open source apps imo, which are the only ones we’re gonna link to anyway, but it’d be nice to have.

  •  abbenm   ( @abbenm@lemmy.ml ) 
    0•2 years ago

    I just would want the option to view pages as lightweight, static html with low or no JavaScript, even if it means pages are not interactable.

    I also think it would be nice if there were additional themes, and that the things fundamentally rethought how much white space was put all over the place. There’s so much potential with the things, but I genuinely just don’t think they are reaching their potential right now.

  •  kevincox   ( @kevincox@lemmy.ml ) 
    0•2 years ago

    It would be nice if the RSS feeds were advertised. For example if I browse https://lemmy.ml/c/lemmy I wouldn’t know there was an RSS feed until I find and click the little RSS icon.

    If a <link> to the RSS feed was provided my browser extension would light up and I can subscript just by putting the community URL into my reader instead of having to spot the RSS button on the page.