- cross-posted to:
- selfhost@lemmy.ml
- schedule
- cross-posted to:
- selfhost@lemmy.ml
- schedule
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.
Edit: The hosted version is at https://schedule.lemmings.world and the support forum is at !schedule@lemmings.world
That is awesome. Thanks for sharing.
I remember using laterforreddit.com some time ago, and there was an option to let it choose the most appropriate time to post. I think it was based on peak traffic time.
Do you know how this was achieved ? Is this something you can reproduce?
It would probably need a direct access to the database (which I want to avoid), there currently aren’t apis for that. Best I could do is based on comment times but that can be inaccurate (lurkers are not taken into account).
If you want, raise it as a feature request either at the Github repo or at !schedule@lemmings.world.
Actually, it did this based on the number of upvotes of the highest posts of the day of each week, and what time of day they were actually posted at. No database access required, I’d presume
That sounds like a wrong metric to use. Better than nothing, but upvote and comment times seem like a much better one.
Well, if you’re optimizing for total # of upvotes, and your only input is the time of day you post, it actually makes good sense to use total upvotes as the metric.
I would imagine it was based on what time upvotes came in for a particular community. Someone would need to collect data on that separately. I don’t think there’s a built in API for it yet