Urgent.News

What's breaking now, across thousands of outlets.

Tech

bibliograph: An AppView for interfacing with bibliographic information on ATProto

An ATProto AppView that provides information about books for other apps to build on top of. First user of it is https://livtet.olamaelcu.net/ Comments

The project aims to create an appview for interfacing with bibliographic information on the ATProto ecosystem. This tool, known as Bibliograph, is open-source and designed to simplify interoperability with other products and projects. It utilizes various methods for discovery, such as searching for book reviews via https://constellation.microcosm.blue/ and ingesting records from TAP of the NSID net.olamaelcu.livtet.biblio.bookReview.

This enables near-real time analysis of book reviews on the protocol directly from Livtet. Bibliograph also normalizes reviews from other applications like Bookhive, ensuring compatibility across platforms. Prometheus is available locally at http://localhost:9090 for monitoring purposes, with pre-computed recording rules refreshed every 30 seconds.

The TSDB (Time Series Database) resides in the promdata named volume with a retention period of seven days. The /metrics endpoint on bibliograph-service is currently unauthenticated and should be bound to localhost before exposing the port.

Written by urgent.news from Lobsters's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at github.com →

More in Tech

Meilleures pratiques de gestion des erreurs des API REST : Codes d'état, RFC 9457 et erreurs réessayables

Concevoir un contrat d’erreur robuste pour une API REST Les réponses d’erreur de votre API font partie de son contrat. Les clients les analysent, les mécanismes de réessai s’appuient sur elles et les…

  • Use appropriate HTTP status codes for error responses, not body content
  • Follow RFC 9110 families: 4xx for client errors, 5xx for server errors
  • Indicate retryability and avoid sensitive information leakage in error responses

API Tekrar Deneme Mantığı ve Üstel Geri Çekilme: Gerçekten İşe Yarayan Desenler

Ödeme API çağrınız sabah 2'de başarısız oldu. Bu bir ağ arızası mıydı, hız sınırı mıydı, yoksa çökmüş bir sunucu mu? Cevap, yeniden denemenin işlemi kurtarıp kurtarmayacağını veya müşteriyi iki kez…

  • Idempotans POST isteklerinde sıfır tekrarlarını sağlar
  • Üstel geri çekilme, gecikmeyi yükselterek senkronizasyonu önler
  • Retry-After başlığı, belirli bekleme sürelerini istemcilerine bildirir

More from Monday 31 August →