I've had wallabag on my radar for quite a while, but I keep ending up on "... but what even
is it?".
Obviously it archives things for later reading. It works great for that on my e-reader, and I'm super glad it exists and KOReader supports it.
But the API[1] is largely undocumented and undescribed, so I'm kinda at a loss as to what the goals and possibilities are, because the app leaves quite a lot to be desired for e.g. replacing personal cataloguing on something Delicious-like. It seems tailor made for small, barely-customizable offline reading (save it for reading later, maybe with tags, then archive it and don't look at it again), despite the API apparently (maybe?) offering a lot more (but not describing it so it's hard to know how it's intended to be used).
Is there, like... documentation somewhere? Particularly with capabilities / intent / goals? I'm hesitant to sink much time into it without some idea of how it thinks of itself, building a bowl of Hyrum-slaw on top of a shaky foundation is no fun for anyone involved. If it's mostly just what the core app presents, it's probably not what I want.
[1]: https://app.wallabag.it/api/doc/ and https://doc.wallabag.org/developer/api/methods/