Messages
Since: TVS 6.9.0
Compatible themes in Television Simulator support a new messaging subsystem which allows you to define one or more RSS feeds and receive “messages” for each new article published. These messages are shown like alerts from your cable provider. One use case is to find out about TVS updates, but you could use it for anything.
Configuration
Section titled “Configuration”Define the global defaults and at least one RSS or Atom feed under the top-level messages property.
messages: fetchIntervalMins: 60 maxAgeDays: 14 expireAfterDays: 30 sources: - url: https://docs.tvs.gcpw.art/tvs-changelog.xml - url: https://example.com/news.xml fetchIntervalMins: 15 maxAgeDays: 7 expireAfterDays: falseGlobal options
Section titled “Global options”| Option | Type | Default | Description |
|---|---|---|---|
sources | array | required | RSS or Atom feeds to aggregate. At least one valid source is required for the Messages menu to appear. |
fetchIntervalMins | number | 60 | Minimum time between automatic fetch attempts for each source. |
maxAgeDays | number or false | 14 | Ignores feed items older than this when importing. Set to false to disable the import-age limit. |
expireAfterDays | number or false | 30 | Removes stored messages older than this during refresh. Set to false to keep them indefinitely. |
Source options
Section titled “Source options”Every source requires a url. A source can also override fetchIntervalMins, maxAgeDays, or expireAfterDays; omitted values inherit the global setting. Empty URLs are ignored, and duplicate URLs are treated as the same source.
maxAgeDays and expireAfterDays solve different problems. The maximum age prevents old feed history from being imported, while expiration removes messages that were previously stored. If either limit would reject an item during import, TVS does not download it into the message database.
Using Messages
Section titled “Using Messages”Messages from every configured source are combined into one list with the newest items first. The Digital header shows an envelope while unread messages exist. Opening a message marks it as read, Up and Down scroll long message bodies, and Delete removes it from the visible inbox.
The list’s Refresh action fetches every source immediately instead of waiting for the configured interval. Feed headings and line breaks are preserved in the message body when the source provides them.
An empty inbox does not hide Messages. The menu is hidden only when there are no valid sources in the configuration.
Browser Storage and Setup
Section titled “Browser Storage and Setup”Messages, source status, read state, and deleted state are stored in an IndexedDB database named TelevisionSimulatorMessages for the current browser and TVS origin. Deleted entries retain a tombstone so the next refresh does not immediately restore them. Refreshing an existing item also preserves its read state.
The graphical Setup → Messages page shows the active and unread counts, last fetch time, and current status for every source. Its actions are:
- Synchronize Now fetches all configured sources immediately.
- Reset Database clears saved messages and source status while keeping the database itself.
- Recreate Database deletes and creates the messages database again.
A Factory Reset also clears the browser-local message database.