A new feature has been added, this one is especially useful for recurring post - it allows you to add the date and/or time of the post to the title.
As an example you can use this exact post which should contain a date that looks something like 2023-10-04 14:15:00+0200 (note that the second will most likely be different, because the scheduler is not exact to the second).
This is how I’ve written the title in Lemmy Schedule: Lemmy schedule - add date to the post title (example: #[InjectDate(‘Y-m-d H:i:sO’)]#).
You may notice the ('Y-m-d H:i:sO')# - this is an expression that will be evaluated at the time of posting. Currently only the InjectDate expression is supported and it takes exactly one parameter. If you’re a programmer, you probably recognize it, it’s a format for the date. Just beware that it uses the PHP date format which might differ slightly from your favorite language.
If you’re not a programmer, the documentation is not that hard - you see a letter (like F) and its description (A full textual representation of a month, such as January or March). When you include F in the parameter, it means it will be replaced with current month name (October). If this is too hard for you and you want it for one or few posts, tell what you want the title to look like and I’ll write it for you.
Note that there’s a preview of what the title looks like:
You’ll also know if you’ve provided something that looks like it should be an expression but is not recognized:
Here are some examples:
Weekly discussion - week ##[InjectDate('W')]#- Weekly discussion - week #40Monthly discussion - #[InjectDate('F')]# #[InjectDate('Y')]#- Monthly discussion - October 2023Monthly discussion - ('F Y')#- equivalent to the above, just wanted to show that you can use it multiple timesDaily thread - ('d.m.Y')#- Daily thread - 03.10.2023
Let me know what you think!
You can find the tool at https://schedule.lemmings.world
You can also self-host it using docker: https://github.com/RikudouSage/LemmySchedule/#self-hosting---docker
You can also use the hosted version, if you wish so. I’m also the author of the client library for Lemmy that this uses and just two days ago I’ve updated the library to work with 0.19 (though it’s not updated in Lemmy Schedule yet).
Oh that’s neat that you have a hosted version. Sorry if you’ve explained this before, but isn’t giving the website moderator credentials sort of… bad?
In theory, though in this particular case you’re giving them to an open source app which you can check the source code of. Of course there is the possibility that I’ve modified the code that I’m hosting, you’re gonna have to trust me that I didn’t.
I’m an author of many open source libraries and apps and I have no need to steal your credentials. Though that of course doesn’t have to mean anything to you.
But if you’re giving your credentials to a mobile app or any other frontend, you’re doing pretty much the same thing. And technically speaking, even trusting your instance admins is the same thing - they might have modified the code to log your credentials.
In general, yes, you should be worried where you put your credentials. In ideal scenario Lemmy would support OAuth or something like that, but that’s not the case currently.
Cool, thanks for the explanation.