In the browser, I can see that markdown displays correctly. In the app (version 1.16.0), it displays the raw, unformatted text.

Browser example:

App example:

Comment Of úkols

Please add therefore a MR here: https://gitlab.com/fdroid/fdroiddata

Hi, is it not possible to publish from Android app?
If this is a missing feature I'll probably just use webapp on phone as well.

Hi, I would like to suggest not only to support local stored images to illustrate the channels, but also to support picking an emoji. The emojisets usually contain a lot of icons to underline the channel's intention and are optimized to be easy to recognize across different cultures etc. and support a lot of different aspects to illustrate the channels intent 🙂

• 🏡 smarthome
• 🧯 security
• 🥼 lab
• ....

Normally when receiving notifications the app listens from ntfy.sh.

This feature however focuses that when the notifier sends a POST/PUT HTTP request to the devices local IP address (with respect to the port) the app process the request.

Are you aware of https://gitlab.com/fdroid/fdroiddata/-/merge_requests/13948?

Please open issues in the main issue tracker, thank you: https://github.com/binwiederhier/ntfy/issues

I will be perfect if that app can display notifications on Android Auto head unit. It is planned?
Thanks!

'java.security.cert.CertPathValidatorException: Trust anchor for certification path not found' produced in Android app when attempting to subscribe to self-hosted docker instance using SSL. HTTP subscription using Android app, and browser based HTTP and HTTPS work without issue.

Description:

Phone numbers in messages are not recognized as clickable links in the NTFY app. Users are unable to directly tap on phone numbers to initiate calls. This inconvenience affects the user experience by requiring manual copy-pasting of numbers into the dialer.

Expected Behavior:

Phone numbers within messages should be formatted as clickable links. Tapping on these links should initiate phone calls directly from the NTFY app.

Android provides a mechanism for marking a service, receiver, or provider to only run on user 0 and for all requests to that service, receiver, or provider to be routed to the one on user 0 rather than within the current user [1].

If ntfy was to take advantage of this, users who segregate their apps between user profiles (as is common with GrapheneOS for example) would be able to still keep one ntfy instance locally and one connection back to the ntfy server rather than requiring one instance per user.

I may be able to eventually try writing up a PR implementing this functionality but it'll likely be a decent while before I do so.

1. https://source.android.com/docs/devices/admin/multiuser-apps

What is the "state of the art" to integrate ntfy in other apps/projects? Copy the mechanism of this app or send somehow a broadcast intent from this app to other apps/project? Is there any example?
By the way: Great work. Exactly what I missed for long time.

<@topcaser:nope.chat> ```
type: crash
osVersion: google/husky/husky:14/UD1A.231105.004/2023112900:user/release-keys
package: io.heckel.ntfy:32
process: io.heckel.ntfy
processUptime: 564 + 308 ms
installer: dev.imranr.obtainium

java.lang.RuntimeException: Unable to create service io.heckel.ntfy.service.SubscriberService: android.app.ForegroundServiceStartNotAllowedException: Service.startForeground() not allowed due to mAllowStartForeground false: service io.heckel.ntfy/.service.SubscriberService
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4681)
at android.app.ActivityThread.-$$Nest$mhandleCreateService(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2271)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.app.ActivityThread.main(ActivityThread.java:8199)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
at com.android.internal.os.ExecInit.main(ExecInit.java:49)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:359)
Caused by: android.app.ForegroundServiceStartNotAllowedException: Service.startForeground() not allowed due to mAllowStartForeground false: service io.heckel.ntfy/.service.SubscriberService
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel(ForegroundServiceStartNotAllowedException.java:54)
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel(ForegroundServiceStartNotAllowedException.java:50)
at android.os.Parcel.readParcelableInternal(Parcel.java:4890)
at android.os.Parcel.readParcelable(Parcel.java:4872)
at android.os.Parcel.createExceptionOrNull(Parcel.java:3061)
at android.os.Parcel.createException(Parcel.java:3050)
at android.os.Parcel.readException(Parcel.java:3026)
at android.os.Parcel.readException(Parcel.java:2968)
at android.app.IActivityManager$Stub$Proxy.setServiceForeground(IActivityManager.java:6776)
at android.app.Service.startForeground(Service.java:775)
at io.heckel.ntfy.service.SubscriberService.onCreate(SubscriberService.kt:101)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4668)
... 11 more

this is a clear app bug

I always have my phone on do not disturb mode. I would like Max Priority Notifications to bypass this mode, so I can receive sound notifications all the time :).

I know it's possible on android, and I'm wondering whether you have plans to add a support for it.