Lemmy Schedule

I'm constantly missing new posts from smaller communities I moderate (like this one, sorry pals, won't happen anymore) so I've added a new feature to Lemmy Schedule.

You can schedule getting notified of any new posts from any specific community you desire. This feature makes the most sense if you enable recurring schedule, but I've made it possible to use a one-time schedule even though I can't really see a use-case. But hey, maybe you will!

The reports will be sent by @UnreadPostReportBot@lemmings.world, make sure you don't block it.

The feature is available for people who self-host as well, in that case you'll have to create your own bot account and put its JWT token (and instance) into the configuration.

You can of course create more than one schedule for a single community, meaning you can get reports at a granularity that the recurring scheduler doesn't report - if you create a recurring job for every hour of the day, you'll get a report every hour of every day.

Let me know how you like the new feature!

You can now select where you want to upload an image when scheduling a post. Current options are the target instance or Imgur.

This is for two reasons:

1. Some instances have very small limits for image files
2. By uploading to different hosts you don't add to the instance admin's storage cost

If you know any other host you'd like to see supported, do let me know!

Hey, nifty piece of kit you made here, and thank you for it. Only problem is that I don't actually see it being posted.

I installed it all via docker compose and it seem to work fine. I'm able to open the app, log into lemm.ee with my credentials, then schedule a post. It then simply clears from the queue at the right time without the post happening.

The redis docker logs aren't showing anything. Here is what I have from the lemmy-schedule docker logs: 192.168.1.50 - - [17/Sep/2023:15:43:50 +0000] "GET /post/create HTTP/1.1" 200 22270 "http://192.168.1.20:8000/post/list" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" 192.168.1.50 - - [17/Sep/2023:15:43:50 +0000] "POST /en/_components/ScheduleComponent/setTimezoneAsString HTTP/1.1" 200 1934 "http://192.168.1.20:8000/post/create" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" 192.168.1.50 - - [17/Sep/2023:15:44:24 +0000] "POST /post/create/do HTTP/1.1" 302 652 "http://192.168.1.20:8000/post/create" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" 192.168.1.50 - - [17/Sep/2023:15:44:25 +0000] "GET /post/list HTTP/1.1" 200 2583 "http://192.168.1.20:8000/post/create" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0"

In the above I set something to post at 15:56. It clears from the queue and nothing further is put into the logs.

Any troubleshooting I should try?

Has anyone experienced getting duplicate posts? every now and then I get a duplicate post and I'm not really sure how to go about debugging it

I've got one post scheduled every day to post in lotrmemes@midwest.social for the account https://lemm.ee/u/Wikischedule, but as you can see from the account linked, it misses quite a few days at a time, and has missed the last 5 days in a row.

Let me know if there's any more info I can provide about the issue ~

Multiple people have been asking about it, so the support for self-hosting using docker is added.

The quickest way to get it up and running is using docker-compose: https://github.com/RikudouSage/LemmySchedule/#docker-compose

~~In the coming days I'll be adding support for locking the app to a single instance only, meaning if you self host it alongside your Lemmy instance, only people from your own instance will be able to use it.~~ Done!

In the newest version I've added support for recurring posts. It's quite flexible, see for yourself:

It also shows a preview of next post times so you can be sure you've got it right:

Other features

• You can now schedule an unpin of a post that you are creating - meaning you can do both on one screen and more importantly, you don't have to wait until the post is posted to be able to unpin it
• I've started some ground work to support uploading images to other hosts instead of always uploading it to the target instance but that's gonna take a while.

Hello,

Thank you for this, I'm currently trying this for !casualconversation@lemmy.world .

As I would like to open new threads every day, would there be a way to have recurrent posting option?

The hard part on scheduling is done, so adding other actions to schedule is quite easy. So, what else would you like to schedule?