🐫 API wrapper for Shaarli exposing pinboard.in/api. Zero-config, drop-in, single-file CGI deployment. https://demo.mro.name/shaarli-v0.41b/pin4sha.cgi
|Marcus Rohrmoser 929e452db8 testdata||2 years ago|
|bin||2 years ago|
|lib||2 years ago|
|pinboard.in||2 years ago|
|test||2 years ago|
|.gitattributes||2 years ago|
|.gitignore||2 years ago|
|.travis.yml||2 years ago|
|LICENSE||7 years ago|
|Makefile||2 years ago|
|README.md||2 years ago|
|doap.rdf||2 years ago|
|post.msc||3 years ago|
|post.png||3 years ago|
The natural API for shaarli.
The wish to have an API goes back to the early days.
And because shaarli started as a personal, minimal, delicious clone, using a minimal subset of just that very API seems natural to me. pinboard.in prooves the API is not only seasoned and mature, but also still up the job today.
Also another project of mine, ShaarliOS needs a drop-in API compatibility layer for a wide range of shaarlis out in the wild.
You find a single, statically linked, zero-dependencies (🐫 Ocaml) binary which is both a
All shaarlis from the old ages until spring 2020 (v0.11.1).
All systems 🐫 Ocaml can produce binaries for.
Just the delicious API calls in pinboard.in/v1/openapi.yaml