I will no longer be able to assist with development nor debugging actual issues with the software… Quite juvenile behavior from the devs. It stemmed from this issue where the devs continuously argued in public by opening and closing an issue. Anyway, thought I would keep y’all apprised of the situation, since these are the people maintaining the software you are currently using.

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

    Dude, who in their right mind would add scheduling infra to a client like that? 😆 I’m going to need these Lemmy devs to have a tad bit more experience before they start being so dismissive, especially to someone who’s just trying to help.

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

      Hi there more experienced person, would you mind explaining the intricacies of the madness for a lowly n00b?

      Is it just 'cause it’d need the client to be constantly running to output the scheduling? So like, you set it to schedule a post and then you have to actually open it as an app before it would actually work if it wasn’t running in the background when the time ticked over? Is there more to it? Any and all details you’d be willing to explain would be appreciated.

      Regardless, I hope you have a lovely day and best of luck with everything you’re doing!

    • rglullis@communick.news
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      2
      ·
      1 year ago

      A “client” in this context can mean anything, including another separate service.

      This makes no sense to have in a desktop/mobile app, but it certainly should not go to the server as well.