• MachineFab812@discuss.tchncs.deOP
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    8 months ago

    Read up. I stated I would be refraining from speaking to the difficulty of implimentation as I do not have my laptop with me.

    I’ve written apps/extentions for personal use. I would rather contribute to an existing code-base like Lemmy, but I acknowleged the fact I am in little position to do so, for the next two weeks in fact.

    Entitlement, really? How is your passing the buck to extention/app devs different from my requesting a feature be implimented in the single location where it will stay fixed, saving time and effort for the devs, including for app and extention devs, going forward?

    Where is your suggested solution that could be implimented, beyond suggesting that apps and extentions have this solved for their users, and we should leave it at that?

    I’ve bought multiple such apps, and found the webUI preferable, so I’mma throw my future suggestions, requests, and yes, financial contributions, as well as any code I write if that turns out to be necessary on my part, at the single project that is already doing so many other things I’ve come to enjoy.

    “What.”, you say.

    • MentalEdge@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      edit-2
      8 months ago

      Again. What?

      I’m not passing the buck anywhere, I’m saying the lemmy server can do this but the default lemmy webUI doesn’t make use of it. At least not yet.

      The problem isn’t being solved by the clients and apps. It’s solved by lemmy.

      Some clients have just made use of it sooner than others, and the vanilla webUI is one of the ones that hasn’t yet. But the feature itself IS IN LEMMY ITSELF.