nextcloud / nextcloud/spreed

Make link preview optional

Open
#8,609 2 comments 25 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: frontend 🖌️ feature: settings ⚙️
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
18h 27m
Merged PRs (30d)
333

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • 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.

Is your feature request related to a problem? Please describe.

Always-on link preview can lead to privacy and usability issues, depending on the user and context.

Examples:

  • Privacy: Merely sending a link causes the link to be accessed, leaking information to the server hosting the link.
  • Usability: Pages behind authentication will show the login page in the preview.

Describe the solution you'd like

I'd like to have the option to turn off link preview, either globally, per conversation or per device.

Describe alternatives you've considered

Only infeasible alternatives:

  • Not sending links.
  • Removing the https:// part of the link before sending.
  • Switching to another messaging tool.

Thank you for developing spreed!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the existing link-preview handling in the Talk codebase and determine whether the setting should apply globally, per conversation, or per device; done means users can disable previews at the supported scope without sending the link for preview access.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.