Notifications

hdtracker can tell you when something from your library comes out: a new episode or season, a cinema or home release, a game release – exactly what shows up under Recently released on the dashboard that day.

• Everything is set under Settings → Notifications.
• They are off until you switch them on.
• Available from version 0.7.0.
• The inbox inside the app collects the same releases for everybody, whether push messages are on or not (from version 0.9.0).

What and when

Under New releases you choose how you want to be told:

Notify me	What you get	Tapping opens
Off	nothing, whatever targets you have	–
One by one	a message per title	that title
Together	one summary a day	the dashboard

From is the hour of the day from which the messages of that day are sent. Only the day of a release is known, not the time. The hour follows the TZ setting in .env.

Every choice is saved the moment you make it.

Good to know:

• A single title can be muted with the bell on its page or in the window that changes its status. Muted, it is left out of the push messages and the inbox.
• Nothing is announced twice.
• When you switch notifications on, only releases from that day on count.
• If the server was off, releases of the last two days are caught up.

Tracking together

If you track titles together with others, hdtracker can send a push message about that too. The card Tracking together has a switch for each kind – it is only shown while there is somebody to share with.

Switch	You get a message when	Tapping opens
Somebody invites me	somebody invites you to a title	the inbox
My invitation was answered	your invitation is accepted or declined	the title
Somebody no longer tracks along	somebody stops tracking a title with you	the title

• All three are on by default and are sent at once, independent of Notify me and the hour set above.
• They go to the same targets. Without a target that is switched on, nothing is sent.
• On your own devices the small picture is the profile photo of the person, if they uploaded one, otherwise two figures in the colours of the logo.
• Several titles at once (an invitation to ten titles) are one message.
• The message names the title and the display name of the person.

Inbox

The bell in the header opens the inbox. It works without any setup and without targets.

Section	What is in it
Invitations for you	Open invitations, with Accept and Decline
Waiting for an answer	Your own open invitations, with Withdraw
News	Releases of titles you track, and what others did with titles you track together (accepted, declined, left)

• What waits for a decision comes first.
• Waiting for an answer and News show their first three entries; the rest unfolds. News you have not read yet are never folded away.
• The bin next to News deletes the news you have read, before the week is over. Opening the inbox reads everything, so it empties the list. Invitations stay.

The number on the bell counts what is unread plus the invitations you have not answered.

What	Counts as read when	Stays how long
Releases	you open the inbox or the dashboard	a week after reading
Answers and leaving	you open the inbox	a week after reading
Invitations	–	until answered or withdrawn

• What you have not read stays until you have.
• New episodes of one title are one line.
• The releases are the same ones the dashboard lists as recently released; the task Announce new releases (Settings → Maintenance) writes them every hour.

Targets

Targets is the list of where the messages go.

• Every target has a name and a switch. Switched off, it keeps all its settings.
• Tap a target to change it, to send a test to exactly this target, or to remove it.
• You can have several targets of a kind.

Target	Needs	Picture arrives away from home	Tapping opens
This device	HTTPS	only if your phone can reach hdtracker	the title in hdtracker
Pushover	a Pushover account and its app	yes	the Pushover app
ntfy	the ntfy app	yes	the title in hdtracker
Webhook	a service that accepts such requests	depends on the service	depends on the service

Who can read the messages differs a lot between the targets – see Who sees what.

This device

Push messages straight from hdtracker, without any other service.

• Needs HTTPS – see HTTPS and installing as an app.
• Android, computer: works in the browser and in the installed app. Installed as an app, the messages are shown as coming from hdtracker instead of from the browser.
• iPhone, iPad: only in the installed app (iOS 16.4 or newer): add hdtracker to the home screen, open it from there and add the device. iOS always shows the app icon, not the picture of the title.
• Add it on every device that should get messages. Tapping a message opens the title in hdtracker.

If adding is not possible, the entry says why:

• the page was not opened over HTTPS,
• you declined notifications for this site once – allow them in the site settings of your browser and reload,
• or the browser cannot receive push messages.

Pushover

Through your Pushover account – useful for devices that cannot get push messages from the app, or if you use Pushover anyway.

1. Log in at pushover.net. Your user key is at the top right of the page.
2. Create an application (Create an Application/API Token; name it e.g. “hdtracker”). Its API token is the app token hdtracker asks for.
3. In hdtracker: Add a target → Pushover, enter both and save. hdtracker checks them at Pushover right away.

Only to these devices (optional)

• Left empty, the message goes to all devices of your Pushover account.
• Otherwise enter one device name, or several separated by commas.
• After saving, the names of your devices at Pushover are listed below the field. Tap one to add it, tap again to take it out.
• Careful with typing: a name Pushover does not know means to all devices there.

What the message looks like

• It carries the picture of the title and a link Open in hdtracker.
• With a picture attached, the notification shows the picture where the icon of the application would be (seen on an Android phone). The switch Attach the picture turns the picture off, then the icon is shown.
• Tapping the notification itself opens the Pushover app. That is how Pushover works and cannot be changed from outside.

ntfy

Through ntfy – the public service ntfy.sh or an ntfy server of your own. The message carries the picture of the title, the icon of hdtracker and a link to the title.

1. Install the ntfy app on your phone and subscribe to a topic there.
2. In hdtracker: Add a target → ntfy, enter the same topic and save. Server stays https://ntfy.sh unless you run your own.
3. Use Test.

Pick a long topic name nobody can guess, e.g. hdtracker-k3v9x2mq7p. On ntfy.sh a topic is open to everyone who knows its name – to read and to write.

Access token (optional)

• For a protected topic on your own server or with an ntfy account (tk_…).
• It is stored but never shown again.

Attach the picture

• The picture is uploaded to the ntfy server, so it also arrives where your phone cannot reach hdtracker.
• How long the server keeps the picture is described by ntfy: Privacy policy.
• From our own test on ntfy.sh: while it is there, the uploaded picture can be downloaded without logging in by anyone who has its address. The address is part of the message.
• On a server of your own, attachments have to be switched on. If they are not, the message arrives without the picture.

Icon address (optional)

• ntfy only passes on the address of the icon; the phone loads it by itself.
• Left empty, it is the icon of your hdtracker – fine if your phone can reach hdtracker.
• If it cannot (hdtracker only in your home network), enter an address that is public, e.g. https://raw.githubusercontent.com/dvnkln/hdtracker/main/static/icons/icon-192.png.

Good to know

• Tapping the notification opens the title in hdtracker – which works wherever your phone can reach it.
• Tried against real ntfy servers and ntfy.sh: message, picture, link and token arrive as described.
• Not checked on a phone: how the notification looks in the ntfy app (icon next to the picture).

Webhook

Sends every message as an HTTP POST to an address of your choice, with content you write yourself. That reaches Gotify, Home Assistant, Apprise and anything else that accepts such a request.

Address

• Where to send it (http:// or https://).
• Redirects are not followed.

Content – what is sent. These placeholders are filled in:

Placeholder	Becomes
{{title}}	the title of the message (the name of the title, or “New today: 3 titles”)
{{message}}	the text, e.g. “S02E03” or the list of the day
{{url}}	the address of the title (or the dashboard) in your hdtracker
{{image}}	the address of the picture of the message; empty if there is none
{{count}}	how many titles the message is about
{{test}}	true for a test message, otherwise false

• If the content is JSON, the values are escaped for you – a quote in a title cannot break it – and it is sent as application/json.
• Anything else is sent as plain text.
• {{url}} and {{image}} use the first https:// address of ORIGIN (otherwise the first address).
• The picture can be loaded without a login, through an address that opens only this one picture.

Header (optional)

• One extra line such as Authorization: Bearer … for services that want a key.
• It is stored but never shown again.

Templates

Both were tried against the real services with hdtracker.

Gotify

• Address: https://gotify.example.com/message
• Header: X-Gotify-Key: <application token>
• Content:

{
  "title": "{{title}}",
  "message": "{{message}}",
  "priority": 5
}

Apprise – for everything hdtracker has no target of its own for: Telegram, Discord, Matrix, e-mail and many more.

1. hdtracker does not contain Apprise. You need the Apprise API running as a container of its own.
2. Save your Apprise addresses there under a key, e.g. hdtracker.
3. In hdtracker – address: http://apprise.example.com:8000/notify/hdtracker, content:

{
  "title": "{{title}}",
  "body": "{{message}}",
  "attach": "{{image}}"
}

• attach makes Apprise fetch the picture from hdtracker and pass it on. For that the Apprise container has to reach hdtracker under the address in ORIGIN; leave the line out if it cannot.
• A message without a picture is sent just the same.
• If you would rather keep nothing in Apprise, use the address …/notify and add a line "urls": "<your Apprise address>" to the content.

Other services work the same way: look up what their API expects and put the placeholders where title and text belong. Use Test – it shows what the other side answered if it refuses.

Who sees what

Target	Who can read the content
This device	Only your server and your device. The push service of your browser's maker passes the message on but cannot read it
Pushover	Pushover. The HTTPS connection protects title, text, link and picture on the way, not from Pushover
ntfy, public service ntfy.sh	ntfy.sh, and anyone who knows the name of your topic
ntfy, a server of your own	That server – and anyone who can reach it and knows the topic, unless it is protected
Webhook	Whoever runs the address you entered receives what you put into the content

This is the short version. What exactly hdtracker sends and stores, and the links to the privacy information of each service: Privacy and security → Notifications.