I’ve made an app that makes it possible to schedule a post in Lemmy at an arbitrary time. It’s available at https://schedule.lemmings.world and can be used by people from any instance.

Let me know what you think!

P.S. This post is made using the app!

Edit: And it’s open source!

  • [email protected]@kerala.party
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    1 year ago

    I am not feeling comfortable entering my login credentials to this website.

    Edit: I made this comment before OP shared the source code.

    • Rikudou_Sage@lemmings.worldOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      No problem, it was planned right from the beginning to be open source, I just wanted to share it as soon as possible!

      • Salamander@mander.xyz
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I would like to make a list at some point with several community integrations and ask my instance’s users whether they would like some of them installed into the instance. This application will definitely go on that list! I do need to take into consideration how many resources each of the apps consume, to make sure I don’t bloat my server. But this one seems quite light. Is it?

        • Rikudou_Sage@lemmings.worldOP
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 year ago

          The way I run it it’s entirely serverless and costs you close to nothing.

          • the application code runs on AWS Lambda (400,000 seconds per month free, time’s only counted when someone is actually making requests)
          • the static assets (CSS, JS etc.) are on S3/CloudFront (very small size, so less than $0.10)
          • event bridge scheduler is used for the scheduling (first 14,000,000 schedules per month are free)
          • sessions and “database” is in DynamoDB (you only pay for real requests, probably less than $0.10)

          All in all the app can be hosted for much less than $1/month like that. If you host it in a standard docker container or something, it probably won’t take much resources either, my guess would be less than 256 MB RAM (probably less than 100 MB) is needed and whatever your backend for scheduling takes (Redis would probably be the most straightforward choice).