Let external apps propose event registrations #6

New issue

Open

opened 2026-09-16 01:09:38 +02:00 by morten-olsen · 0 comments

morten-olsen commented

2026-09-16 01:09:38 +02:00

Owner

Context

Users can manually define external broadcast events with JSON payload schemas and optional verified-sender allowlists. A future protocol may let another app propose its own event definitions.

Scope

Accept registration proposals through an F-Droid-compatible Android intent flow.
Show the verified requesting package, stable identity, schema, and requested sender policy before installation.
Require explicit user approval; a broadcast must never silently expand the trusted registry.
Define payload-size and publication-rate limits for external ingress.
Preserve the existing event gateway and registry interfaces.

Acceptance

Approved proposals become ordinary versioned external event definitions and named sources.
Rejected or malformed proposals do not mutate the registry.
Sender identity, schema validation, payload limits, and rate limits have observable failure states.
The flow uses Android platform facilities only; no FCM or proprietary service dependency.

## Context Users can manually define external broadcast events with JSON payload schemas and optional verified-sender allowlists. A future protocol may let another app propose its own event definitions. ## Scope - Accept registration proposals through an F-Droid-compatible Android intent flow. - Show the verified requesting package, stable identity, schema, and requested sender policy before installation. - Require explicit user approval; a broadcast must never silently expand the trusted registry. - Define payload-size and publication-rate limits for external ingress. - Preserve the existing event gateway and registry interfaces. ## Acceptance - Approved proposals become ordinary versioned external event definitions and named sources. - Rejected or malformed proposals do not mutate the registry. - Sender identity, schema validation, payload limits, and rate limits have observable failure states. - The flow uses Android platform facilities only; no FCM or proprietary service dependency.

morten-olsen added the

feature

label

2026-09-17 08:19:57 +02:00