Admin-configurable custom URI protocol handlers for autolinking

[fomand-dev]

Tip

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Feature request

Allow administrators to configure which custom URI protocols (beyond http/https/ftp/mailto) should be automatically recognized and rendered as clickable links in Talk messages.

Only standard protocols are auto-linked in plain text messages. Custom protocols like e1c://, zoommtg://, tg://, ms-word://, jetbrains://, figma:// remain as plain text even though they are valid, OS-registered URI schemes.

Example:
e1c://server/1c-srv/235#e1cib/data/Document.Audit

→ Currently: plain text
→ Expected: clickable link

Proposed solution: Admin UI for protocol management

Structured list with validation (preferred)

Custom URI protocols

Protocol    | Description (optional)        | Actions
------------|-------------------------------|----------
e1c         | 1C Enterprise ERP links       | [Edit] [Delete]
zoommtg     | Zoom meeting links            | [Edit] [Delete]
tg          | Telegram app links            | [Edit] [Delete]
            |                               |
[+ Add protocol]

Security setting: [☑️] Only allow configured protocols (block all others)

[Antreesy]

Hi,

I'm not sure that's in the scope of Talk application, but rather an underlying library + server core.

Allowed values for linking are hardcoded here: https://github.com/nextcloud-libraries/nextcloud-vue/blob/1e4398a6019f2b0a60a8f062e4fc7dfb7343b5f6/src/components/NcRichText/NcRichText.vue#L329-L332

Since it can potentially affect all NC Hub applications in general, that would be rather a part of Administration settings -> Security. Transferring issue to server

[spanchy]

hello, i same need, and i think at a need as well add autopreview setting for all and/or separated proto. I think see question about this.