[GH-ISSUE #497] UnifiedPush restrictions #379

Closed
opened 2026-05-07 00:23:39 +02:00 by BreizhHardware · 5 comments

Originally created by @bt90 on GitHub (Nov 14, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/497

A few things which are currently not covered by the documentation:

  1. Does UP still work if i restrict the access by default? https://docs.ntfy.sh/config/#example-private-instance
  2. What happens if i change the displayname of an active UP subscription in the app? e.g https://ntfy.example.com/xxxxxxxc to tusky ?
Originally created by @bt90 on GitHub (Nov 14, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/497 A few things which are currently not covered by the documentation: 1. Does UP still work if i restrict the access by default? https://docs.ntfy.sh/config/#example-private-instance 2. What happens if i change the displayname of an active UP subscription in the app? e.g `https://ntfy.example.com/xxxxxxxc` to `tusky` ?
Author
Owner

@binwiederhier commented on GitHub (Nov 14, 2022):

  1. This is covered in the UP docs: https://unifiedpush.org/users/distributors/ntfy/#limit-access-to-some-users -- Long story short: you have to allow write access to up* for anonymous users, or for a specific UP topic
  2. The display name has no impact on the subscription. It's just displayed differently in the client
<!-- gh-comment-id:1314009972 --> @binwiederhier commented on GitHub (Nov 14, 2022): 1. This is covered in the UP docs: https://unifiedpush.org/users/distributors/ntfy/#limit-access-to-some-users -- Long story short: you have to allow write access to `up*` for anonymous users, or for a specific UP topic 2. The display name has no impact on the subscription. It's just displayed differently in the client
Author
Owner

@bt90 commented on GitHub (Nov 14, 2022):

Thanks for the quick answer. I created #499 as i think this should be covered in the ntfy documentation.

<!-- gh-comment-id:1314219075 --> @bt90 commented on GitHub (Nov 14, 2022): Thanks for the quick answer. I created #499 as i think this should be covered in the ntfy documentation.
Author
Owner

@binwiederhier commented on GitHub (Nov 14, 2022):

https://docs.ntfy.sh/config/#example-unifiedpush

<!-- gh-comment-id:1314337698 --> @binwiederhier commented on GitHub (Nov 14, 2022): https://docs.ntfy.sh/config/#example-unifiedpush
Author
Owner

@bt90 commented on GitHub (Nov 14, 2022):

Thanks for the adjustments. This should make things a lot clearer for UP newbies 👍

<!-- gh-comment-id:1314369204 --> @bt90 commented on GitHub (Nov 14, 2022): Thanks for the adjustments. This should make things a lot clearer for UP newbies 👍
Author
Owner

@bt90 commented on GitHub (Nov 14, 2022):

Should we drop the $ from the examples? Just noticed the copy button which obviously won't properly work that way.

<!-- gh-comment-id:1314371292 --> @bt90 commented on GitHub (Nov 14, 2022): Should we drop the `$ ` from the examples? Just noticed the copy button which obviously won't properly work that way.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#379
No description provided.