I have to disagree. I used XML-RPC exactly twice, but it proved to be a quick solution to nasty integration problems and we were very happy with it. Case #1 - we had to implement an interface to book flights on Amadeus (https://amadeus.com/en). In order to guarantee the caller identity they provided a C library (binaries that you had to link with your stuff) that would generate tokens that you would then add to... - Source: Hacker News / almost 2 years ago

For example, my employer, Amadeus is part of the French national body through AFNOR, the French standardization organization. We have a representative at the meetings of the AFNOR, but Amadeus doesn't have its own delegate at the ISO meetings. The members of the French national body, including Amadeus, choose who can vote at the international meeting representing the French opinion. - Source: dev.to / almost 2 years ago

There are already some very good ebooks solutions out there so there's really no need. Calibre for the backend and database management, Calibre-Web for the front end, and Openbooks for content. Source: 6 months ago

I have a carefully-curated calibre-web library that is 100% epubs. I have a kindle to which I usually send books from calibre-web with the 'send to e-reader' button, and it works great. Source: 6 months ago

Worthy of note the Calibre-Web[0] project, which builds atop Calibre library to provide powerful web interface. The project and its maintainer deserve some love and support. [0] https://github.com/janeczku/calibre-web. - Source: Hacker News / 7 months ago

A pihole, of course. A backup script runner. An eink dashboard.. A book server. Source: almost 1 year ago

Calibre-web or the built in Calibre Content Server? Are you using a reverse proxy? Source: about 1 year ago