openvibers/openvibe.watch Commits

README first screen and CITATION.cff (#266)

OP OpenVibers committed 3 days ago · d6f7a0cd31 · 2 files, +21 −0

Changes

ddiff --git a/CITATION.cff b/CITATION.cff
nnew file mode 100644
iindex 0000000..b3c83c9
---- /dev/null
++++ b/CITATION.cff
@@@ -0,0 +1,18 @@
++cff-version: 1.2.0
++message: "If you use OpenVibe.Watch in research or a product, cite it as below."
++title: openvibe-watch
++type: software
++authors:
++  - name: OpenVibe
++    alias: OpenVibers
++    website: https://openvibe.network
++repository-code: https://github.com/OpenVibers/OpenVibe.Watch
++url: https://openvibe.watch
++license: AGPL-3.0-only
++abstract: "Web monitoring over pages, feeds, APIs and devices that can wake Actor, Codes or Run, at openvibe.watch."
++keywords:
++  - openvibe
++  - alerts
++  - automation
++  - monitoring
++  - rss
ddiff --git a/README.md b/README.md
iindex 62d0d0f..183666c 100644
---- a/README.md
++++ b/README.md
@@@ -4,6 +4,9 @@
  > watch, get told when it changes or fires — cheaply, because a Watch never polls when an event or
  > the site's own ETag will do.
  
++**Live site:** https://openvibe.watch · **API docs:** https://openvibe.services · **For AI:** https://openvibe.watch/llms.txt
++**Run it:** `npm ci && npm run dev` (Node 22 or newer) · **Tests:** `npm test`
++
  **Status:** alpha (plan T18). The registry, the check engine, the pull carriers (`http`, `feed`, `api`), the push
  sources (OpenVibe events and signed webhooks), Link probes from the owner's own machine, the actions (a notification,
  an event, a webhook, an Actor task or agent run, a Run job, a Codes task) and the public site (sign-in, seven starting