dropyour_events
shallowio.dropyour/dropyour · Verify this server
Events between YOUR server apps, SIGNAL ONLY. A topic (e.g. 'devis.signe') declares the identifier keys its signal carries, e.g. ['devisId']; a signal never carries data, the subscriber reads the detail back from the emitter through a call permission. action='declare' (topic + keys, max 8 keys, max 8 topics per app; redeclaring with other keys bumps the revision; give a `label`, the human name the owner sees on screen, e.g. 'Devis signé'), 'retire' (also removes its subscriptions), 'subscribe' (topic + subscriber dropId + the subscriber's ROUTE that will receive the signal; requires that the emitter is allowed to call the subscriber via dropyour_link, both server apps of the same account; max 8 subscribers per topic; the answer tells whether the subscriber may call back the emitter to read details), 'unsubscribe', 'list'. Owner gesture; unlinking or transferring an app removes the subscriptions it carried. EMIT from the app's server code, atomically with a write: app.records.put(collection, id, doc, expectedUpdatedAt, { emit: { topic, signal: { devisId: 'd_42' } } }) (also records.remove(c, id, { emit })) — nothing leaves a refused write, and a refused signal refuses the write (reason 'evenement_refuse', with why). Without a write: app.events.emit(topic, signal), sent at the end of the request only if the code did not throw. Chains are capped at depth 3, 10,000 emissions per app per day. DELIVERY: the subscriber's route receives a POST { id, topic, signal, revision, seq, emisLe, emettrice } with app.caller = { dropId: emitter }, at least once and deduplicated by the platform (its code runs once per event); 2xx = delivered, 5xx/429/throw = retried with backoff, other 4xx or no route = refused, said in the logs. Unlinking stops delivery, even for events already queued. After 8 failed tries a dead letter is written in the EMITTER's logs (dropyour_logs). DEAD LETTERS (exhausted tries, or refused by the subscriber: 4xx, no route) are kept in the emitter: action='dead_letters' lists them; action='replay' sends them again with the same event id (all not yet replayed, or one subscriber, or one event id) — fix the subscriber first; a subscriber that already took the event never runs it twice. The owner sees the same thing in their dashboard: on the system page, which app notifies which, and "Not received" with a one-click "Send again".
1 trials · measured today
dropyour_events scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.dropyour/dropyour, measured 20 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-20 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/dbcfaeba-7ca9-4132-a345-49209ee23ad3)