Where to Get Help or Report Issues for Link Extractor

Link Extractor routes different needs to different channels: usage questions go to the Documentation or FAQ, bugs go to the issue tracker, feature ideas go to a feature request form, and general or community help goes to the Discord server. The official site lists all of these under its Support section, so you can pick the channel that matches your problem instead of guessing.

Match your problem to the right channel

Usage help: Documentation and FAQ

If the extension isn't behaving the way you expect — for example, filters aren't matching, or you can't find an option — check the Documentation first. The site describes it as the place for usage instructions, which makes it the right starting point for "how do I do X" questions.

The FAQ covers recurring questions, so it's worth checking before opening a new issue. Many "is this supposed to work this way" questions are already answered there.

Reporting a bug

Bugs go through Open an Issue. Before submitting:

• Reproduce the problem once more and note the exact steps.
• Check the FAQ and Documentation — if the behavior is documented, it may not be a bug.
• Search existing issues so you don't file a duplicate.

A useful bug report states what you did, what you expected, and what actually happened. Since the extension works across Chrome, Firefox, Edge, and other Chromium-based browsers, mention which browser and version you're on — behavior can differ between them.

Requesting features

Ideas, suggestions, and requests go through Submit a Feature Request, which is a separate channel from bug reports. Keep the two apart: a broken filter is a bug, while "I want a new filter option" is a feature request. Describing the workflow you're trying to accomplish is more useful than naming a specific implementation.

Community and general feedback

The Discord Server is listed as a support option, which suits quick questions or discussion that doesn't fit a formal issue. For anything broader — general feedback, or finding the developer's other apps — the CSSNR Website is the listed destination.

Before you ask

A few checks save a round trip:

• Confirm you're on a current version of the extension.
• Re-read the relevant Documentation section for the feature you're using.
• Search the FAQ for your exact symptom.
• If you're reporting a bug, gather your browser name and version, plus the steps that trigger it.

If none of that resolves it, the issue tracker is the place for reproducible bugs, and the Discord server is the place for everything else.