Good catch! It isn't related to #887. I will fix it until next release.
I didn't mean you should develop API. I just wished. Don't worry.
I'm glad to hear you prefer Plume!
Are you interested to modify your Docker image to be static with an (improved) entrypoint script?
Yes, I think it's nice if Docker image size is reduced. Once you think your Dockerfile and starter script is enough well, can you make a pull request? Then I will review in detail again (this does not mean I don't see scripts here. But now I'm seeing them roughly).
Because it loads all the posts of the instance without a time or user filter?
Yes, that's the reason.
So some more filters and default limits would be nice?
I think so.
For user activity, you can retrieve Atom feed although it might not be useful for modern development. Its URI is /@/{username}/atom.xml
.
I think about a way to use plume as backend server for some blogs, loaded by api (limit, pagination) to show inside of a custom html / js frontend.
That's nice idea! I wish someone had time to implement APIs...
Searching title need to be full title (path) hit?
Yes, it does.
I read implmentation. According to it, all of title, subtitle and content need to match exactly...
Anyway you can retrieve all contents from GET /posts
without any params. (But don't do that againt any instances excluding yours because it occur high loads.)
API doc for GET /posts
is wrong. I filed an issue to documentation repo: plume/documentation#122.
Note:
- Python documentation: https://docs.python.org/3/library/platform.html
- Source code: https://github.com/python/cpython/blob/3.9/Lib/platform.py