• PropaGandalf@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      1 year ago

      I’d go even further and say: A platform where you can share any type of media (text, pictures, video, 3d models, …) but with threads and forum like comments as seen on lemmy or reddit. Each instance could then limit the upload size up to a certain limit or even use a decentralized type of storage like IPFS or something similar.

      Also I’d love to emphasize user based moderation/curation. I’d love to have a platform where you can see everything without any censorship but there are easy ways to filter the content locally using user built presets or just a very granular configuration.

      And last but not least: Single Sing On. ActivityPods is already in development so I hope all the best.

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

    A wiki with strong moderation tools, and gnupg signed/verified text built into it from the start.

    An activitypub method to keep git repos in sync automatically.

    A small blog type tool that’s used as a replacement for facebook. It would have a hosted “gathering” component that is always online, then when you open your local app, it pulls down all your stuff.

    Shared secrets like a distributed KeePass or Bitwarden.

    Distributed home directory and/or development environments.

    Something like the useful bits from KeyBase. I really wanted keybase to be something that could support this use case: Alice@foo gets a dev job at Bar. Her ID is added to the cool_project@bar group and automatically she has access to all the group’s big bug tracking, file shares, wiki, git repos, group chats, etc. Her joining the group is recorded in a permanent record, which can be publicly or privately annotated by people specifically allowed by the group she joined. It’d become an automatic resume.

  • PeleSpirit@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    I really liked RES on reddit and I still miss some of those capabilities like

    • tagging good and bad users so that you know them in the future. You could color code them to know instantly if you thought they were bots, trolls, or friends easily.
    • to put my favorite subs at the top to go to them instantly
    • the multi-subreddit feature
    • being able to see between comment threads easily. Right now, the quote bar gets mixed up with the thread bars and there is no separator between them, on RES I could have a thick line if I wanted.

    Other than these UI issues, I love Lemmy.

      • PeleSpirit@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 year ago

        I would definitely check that too but I liked the tagging a lot because you could see people do 180 degrees within the same day or a couple of months. It was super easy to track if they were trolls and/or propaganda people by how they changed and you could also check the link of the comment that made you first tag them. The trolls were exactly the same every time, they would call you a stalker lol. Politics and public freakout especially needed those nuances and you could ruin their troll account.

  • donio@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    1 year ago

    I’d really like to see some client-API consolidation. A common client API that could efficiently handle both “microblog” style and threaded discussions (lemmy etc) and leave the door open for other discussion formats too. This would allow for clients/frontends to flourish even more and backends could compete on features and efficiency. The backend specific features could be expressed through an extension mechanism of the common API.

    • Dr. Bluefall@toast.ooo
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I feel like something like that would need to be discussed at the standards level; a common API spec could maybe be issued as an extension of the current ActivityPub standard. Call it “CommonSocial”, or something.