Lemmy Schedule

You know how in the previous post I urged everyone to do proper backups? Well, guess what happened... If you use https://schedule.lemmings.world/ as your scheduler, all your posts were deleted, including recurring ones etc. Sorry for the inconvenience.

I've merged a significant rewrite into the main branch and will be releasing it soon.

Before I do so, I want to let everyone know that this will be a major release which means some old functionality will be left behind and some new is coming and you should take care when upgrading.

Namely, backup the volumes you have bound for runtime cache and uploaded files. Those are bound to these container directories:

• /opt/runtime-cache
• /opt/uploaded-files

The database format has changed completely and is incompatible with the old version, after you upgrade to the (soon-to-be-released) version 2, you won't be able to come back to any previous version. For that reason, the only way to downgrade in case of migration failure is by using the aforementioned backup.

I've tested it a lot and the migration works well, but there's always the possibility that your instance has some weird edge case I didn't think of.

On the off chance you used the serverless deployment to AWS, it's now unsupported and Docker (or manual deploy) are the only supported options now. To migrate from Dynamo DB cache backend, I've added a app:migrate-dynamo command you can use.

The reason for this rewrite is simple, back when this project started, only very simple use-cases were supported and using a cache instead of DB was fine, but now I've basically implemented a few relational database features into a key-value cache storage and then I thought "Hey, you know what else has relational database features? Relational databases!" so here we go.

Pretty much nothing else has changed (except some general modernization and a few unrelated bug fixes), but this will make it possible to implement new features without losing my sanity.

That's twice now that my bot's programming has been deleted without me knowing why.
So I've recreated it twice now. It's a daily bot, which posts the same topic every day, only the title date changes.
Could you tell me what's causing my problem?
Thanks in advance.

Personally for me it will be a huge quality of life improvement if the post time selection boxes were moved to the very top.

I schedule so many that I have to look at the post list to see when my last one is and then when I go to schedule new post I scroll all the way to the bottom to set this new Post Time appropriately in relation to the last scheduled post. Then I scroll back up to the top and fill in the rest of the information

Finally got the time to write it down, but if you update to the latest version, you can access the help page for both currently available dynamic expressions you can use in the title. It will list any future expressions if there ever are any new ones.

You can access it at /post/help/expressions on your Lemmy Schedule instance (for example, https://schedule.lemmings.world/post/help/expressions). A link for that page has been added to the title field as well.

Hi All, How can I add a counter for the date in a publication ? Is there a way to do so ? Or do I need to accept the risk of having a February 35th with a regular counter ?

Would it be possible to either: A. have a setting that will auto set the time for the next scheduled post, e.g. a certain number of hours after the last one scheduled or B. Have preset buttons on the date/time section to set your date and time such as - After Last Post: +1 hour, +4 hour,+6 hours, +12 hours, +24 hours, etc

I'm assuming that the body field supports markup but are you planning to integrate any HTML functions into the editor?

Edit: I did a test post with an anchor link and it DOESN'T accept HTML tags. Interesting. So any plans to do this in the future?

I've deleted them all now but each post is posting three times - what information do you need from me to try to resolve this?

Along with a few fixes that hopefully make docker work again, I've added two new features:

• when you paste a link into the URL field, the title of the page will be fetched and filled into the Title field (if the Title field is empty)
• you can now use counters in your titles

Counters are basically named variables that increase after each successful post, those are mostly useful for recurring post. They can start at any value and by incremented by any value (well, except zero). They can be injected using the same syntax as dates:

• #[Counter('counter-name')]#

Just a reminder that you can use #[InjectDate('Y-m-d')]# syntax to insert the date at the time of posting (of course replace Y-m-d with your desired format)

Despite this account being marked as bot, its human owner is typing this post out right now.

Oops! An Error Occurred

The server returned a "500 Internal Server Error".

Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

I am letting you know now! Trying to schedule a post from lemmy.zip with this account, successfully logged in on the scheduler, to !otomegames@ani.social. I receive this error.

Hi!

I love the app, but have frequent trouble with my instance not accepting some nsfw webp. Imgur doesn't allow NSFW content, but catbox.moe does.

Would it be possible to integrate catbox.moe uploading + linking into the app?

I don't really know what to look for in the logs, but with some guidance maybe we can figure this out. Here's how it typically goes:

Set up daily recurring auto-post at sub.wetshaving.social. It works for about 1-2 weeks, then stops.

I set the entire server to restart every 3 or 4 days, which makes Lemmy Schedule stable for longer, but still every week or two it will stop working.

The solution is some sort of combination of restarting the Docker stack (Lemmy Schedule and Redis) and/or opening the Lemmy Schedule web interface and logging in, logging out, refreshing, logging back in, whatever it takes. The need to load the web page is odd, like it reminds Lemmy Schedule somehow that "oh yeah, there are posts to post".

A lot of times when I log in to fix it, the scheduled post does not appear in the to-do list. We have a weekly post that stays in the to-do list, but not until I reload, log out, etc. will the daily post eventually find itself and reappear in the list.

When it starts working again, it typically spits out the posts that it missed, sometimes in duplicate.

Any ideas?

Since version 1.6.0, Lemmy Schedule supports Lemmy 0.19.3.

You might need to log out and log in if it does not work.

Hello @rikudou@lemmings.world, I hope you are doing well.

We just updated our instance (https://jlai.lu) to 19.3 yesterday, and noticed that today the scheduled posts had disappeared. I tried to create them again, but got this error:

Just wanted to report this to you, let us know if at some point you are able to fix it.

Have a good one!

New version has been released, it contains one small bug fix where the app wouldn't clean up list of old job ids and thus making the listing slower and slower as you posted more posts. Now it correctly cleans up any job id that does not exist anymore from list of your jobs, thus making it significantly faster.

If you've self-hosted using Redis, you might have not noticed it because Redis is quite fast, so nothing much changes for you.

I've added a new experimental feature to Lemmy Schedule, currently only available if you're self-hosting and enable the feature using the FLAG_COMMUNITY_GROUPS environment variable (set it to 1 or something).

Community groups allow you to define a group of communities which then can be a target when creating a post. Meaning you can create a group that consists for example of 5 different "world news" communities and then you don't have to remember which ones you usually post to, you just post to the group and it will get resolved to actual community names automatically.

The feature will be available on https://schedule.lemmings.world once I finish it, currently it's not very polished (error handling needs some work, other than that it should work well).

Hi @rikudou@lemmings.world ! I manage a bot for !parentalite@jlai.lu and your schedule app usually post 3 times. Today, the application posted the same post 9 times ! (I've left them for you to see).

Hi ! One of our community c/ has a duplicate of their scheduled posts by parentbot : https://jlai.lu/post/2008603

They deleted their other posts. Dunno if it is helpful, but we can do few tests if needed. Thank a lot :)

Currently if we accidentally create a schedule then there is no way to edit it (if we were to make a mistake), and then we have to completely redo the post

I mod !edm@reddthat.com and want to have a post on tuesday's that increments every tuesday. My titles are: [Trance Tuesdays #1] and i would like to have the number increment so it counts up from X.

Hi, thanks so much for this tool. I've had your post saved for a while and I finally got around to checking it out and it's great. Just wondering if I'm missing it, but is there a way to edit a scheduled post? Like to change the title or text? Thanks again!

Hello @rikudou@lemmings.world ,

The tool is still working great, now I had another question for you: would it be possible to have the option to automatically unpin recurring post, once a new one is created? I have daily threads that I would like to keep pinned, once at a time.

Currently, I haven't seen that option, as the current unpin option is for a specific date, not a recurring time

Thank you in advance!