I started up my own instance and now I have realized that there’s no reason anyone would join mine instead of any other instance.

That’s no good. What neat stuff would the Fediverse like to see in a Lemmy instance?

  • Follow RSS feeds in your Lemmy feed? I have that already, in a way, but it would be nice to be able to do it for any feed automatically without it being clunky.
  • Follow Mastodon users? Or tags?
  • Embedded video? That seems costly.
  • Hackability? The ability to run your own customized front end? Or good scripting features in the browser console?
  • A better looking UI? This one is functional but it’s not pretty.
  • Better moderation? I have heard the Lemmy tools aren’t that good.
  • Something else?
  • maegul (he/they)
    link
    fedilink
    English
    arrow-up
    2
    ·
    5 months ago

    The RSS feeds thing feels like a good one.

    Additionally, some feature where you can start a community but define it simply as a combination of RSS feeds … essentially a feed aggregator. But one that others can share and subscribe to.

    I think a bot could handle most of that.

    Hackable front end is interesting. You can already run multiple alternative front ends. Lemmy world offer 5 I think. Then, they just need to be scriptable if that’s what you want.

    Restyling the default one seems to be common though

    • PhilipTheBucket@ponder.catOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 months ago

      The pondercat rss bot can already do that. You can create a community that gets posts from any number of RSS feeds.

      Well, you can’t, but I can. I don’t want to make it available for anyone to use yet, because I don’t want an explosion of RSS spam, but if you want to connect some RSS feeds to a community and it’s not going to become obnoxious, I can do that for you.

      Hackable front ends, I think, could be a huge deal. I don’t know how easy that is, but if it’s possible for someone to run a modified version of the frontend just for them out of a subdomain, without it being a security nightmare, that would solve a lot of these issues of wanting an extra button on the report page, but having to have it go from you to the site admin to Nutomic back to a code update to a PR and back down the chain and so on, before it can get done.

      With some web apps, that’s easy, and Lemmy’s frontend and backend are already nicely separated. I don’t know if there have to be privileged things running in the frontend, though. I looked at it just now but I couldn’t completely sort out how realistic it is. That might mean it’s not very realistic.

        • PhilipTheBucket@ponder.catOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 months ago

          It is not, partly because it is still rough and just written, and partly because I’m scared people will start blasting RSS spam everywhere and it will be my fault.

          • maegul (he/they)
            link
            fedilink
            English
            arrow-up
            1
            ·
            5 months ago

            partly because I’m scared people will start blasting RSS spam everywhere and it will be my fault.

            That is fair. Might be worthwhile talking to instance admins and core devs about how best to make use of it? Putting it behind some admin approval or administration might be the best way.

            There was an instance a while back that was dedicated to something similar. Their system was to define the feeds themselves without any real user input, and it never really took off.

            Maybe a dedicated instance that provides more user control but is also set up to control and limit things could go a long way? One basic control might be limiting usage to user accounts older than a certain threshold. lemm dot ee does this for image uploads (4 weeks minimum age).

            • PhilipTheBucket@ponder.catOP
              link
              fedilink
              English
              arrow-up
              2
              ·
              5 months ago

              That is fair. Might be worthwhile talking to instance admins and core devs about how best to make use of it? Putting it behind some admin approval or administration might be the best way.

              That’s a good idea. And then, if it turns into a mess of botspam, it’s not my fault.