| description | 🐫 API wrapper for Shaarli exposing pinboard.in/api. Zero-config, drop-in, single-file CGI deployment. |
| repository URL | https://code.mro.name/mro/pin4sha.cgi.git |
| owner | eu1ahS@mro.name |
| last change | Thu, 2 Apr 2020 18:54:08 +0000 (2 20:54 +0200) |
| last refresh | Sat, 27 Apr 2024 12:51:30 +0000 (27 14:51 +0200) |
| mirror URL | git://repo.or.cz/pin4sha_cgi.git |
| https://repo.or.cz/pin4sha_cgi.git | |
| ssh://git@repo.or.cz/pin4sha_cgi.git | |
| bundle info | pin4sha_cgi.git downloadable bundles |
| content tags |
README.md
pinboard.in.cgi
The natural API for shaarli.
Why?
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.
How?
You find a single, statically linked, zero-dependencies (🐫 Ocaml) binary which is both a
- cgi to drop into your shaarli php webapplication next to index.php – as the API endpoint,
- commandline client to any shaarli out there, mostly for debugging and compatibility-testing purposes.
Compatibility
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
Design Goals
| Quality | very good | good | normal | irrelevant |
|---|---|---|---|---|
| Functionality | × | |||
| Reliability | × | |||
| Usability | × | |||
| Efficiency | × | |||
| Changeability | × | |||
| Portability | × |
| 2 years ago | develop | logtree |
| 4 years ago | master | logtree |
| 4 years ago | pinboard.in/go | logtree |