iris_x_hermes

95 Commits 1 Branch 4 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
ARIA	b065d1783b	Docs: clarify ntfy privacy — default server is public ntfy.sh CI / Gateway plugin tests (push) Successful in 8m58s Details CI / Kotlin tests (android host + desktop) (push) Failing after 13m32s Details The docs claimed ntfy keeps push metadata on your own infrastructure, but the default NTFY_SERVER_URL is the public https://ntfy.sh cloud service. Make explicit that push metadata (topic, notification title) passes through ntfy.sh unless you self-host ntfy.	2026-08-27 09:23:44 +02:00
ARIA	f90e40a3fc	Fix README limit claims to match reality (issue #13 ) CI / Gateway plugin tests (push) Failing after 1m4s Details CI / Kotlin tests (android host + desktop) (push) Successful in 8m3s Details - 'No file limit' -> 100 MB default, configurable via max_upload_bytes - 'No character limit' -> 'No 4,096-character limit like Telegram' (hard frame-body cap: 1 MiB) - Note that limits are set on the gateway side (hermes), not in the app - Sync docs/playstore-listing.md (same overclaim)	2026-08-24 21:05:13 +02:00
ARIA	746d809d48	Default push backend to ntfy; FCM opt-in with privacy warning (issue #10 ) CI / Gateway plugin tests (push) Successful in 5m3s Details CI / Kotlin tests (android host + desktop) (push) Successful in 7m6s Details - IRIS_PUSH_BACKEND now defaults to ntfy (keeps push metadata on your own infrastructure); FCM is opt-in via IRIS_PUSH_BACKEND=fcm - build_push_backend(): ntfy for empty/unknown names, FCM only on explicit 'fcm' - gateway setup: warn when FCM is chosen (metadata routed via Google's servers) - README: privacy note + dedicated push section; new docs/playstore-listing.md with the FCM/ntfy privacy note for the Play Store listing - docs: 00/02/03/08/12/16 + setup.md updated to ntfy-default wording - tests: default-backend assertion updated (86/86 pass)	2026-08-24 19:04:40 +02:00

Author

SHA1

Message

Date

ARIA

b065d1783b

Docs: clarify ntfy privacy — default server is public ntfy.sh

CI / Gateway plugin tests (push) Successful in 8m58s

Details

CI / Kotlin tests (android host + desktop) (push) Failing after 13m32s

Details

The docs claimed ntfy keeps push metadata on your own infrastructure,
but the default NTFY_SERVER_URL is the public https://ntfy.sh cloud
service. Make explicit that push metadata (topic, notification title)
passes through ntfy.sh unless you self-host ntfy.

2026-08-27 09:23:44 +02:00

ARIA

f90e40a3fc

Fix README limit claims to match reality (issue #13 )

CI / Gateway plugin tests (push) Failing after 1m4s

Details

CI / Kotlin tests (android host + desktop) (push) Successful in 8m3s

Details

- 'No file limit' -> 100 MB default, configurable via max_upload_bytes
- 'No character limit' -> 'No 4,096-character limit like Telegram'
  (hard frame-body cap: 1 MiB)
- Note that limits are set on the gateway side (hermes), not in the app
- Sync docs/playstore-listing.md (same overclaim)

2026-08-24 21:05:13 +02:00

ARIA

746d809d48

Default push backend to ntfy; FCM opt-in with privacy warning (issue #10 )

CI / Gateway plugin tests (push) Successful in 5m3s

Details

CI / Kotlin tests (android host + desktop) (push) Successful in 7m6s

Details

- IRIS_PUSH_BACKEND now defaults to ntfy (keeps push metadata on your own
  infrastructure); FCM is opt-in via IRIS_PUSH_BACKEND=fcm
- build_push_backend(): ntfy for empty/unknown names, FCM only on explicit 'fcm'
- gateway setup: warn when FCM is chosen (metadata routed via Google's servers)
- README: privacy note + dedicated push section; new docs/playstore-listing.md
  with the FCM/ntfy privacy note for the Play Store listing
- docs: 00/02/03/08/12/16 + setup.md updated to ntfy-default wording
- tests: default-backend assertion updated (86/86 pass)

2026-08-24 19:04:40 +02:00