localsend / localsend/protocol
Why use custom multicast advertisement instead of mDNS?
Open
Nobody has claimed this yet.
- Dominant language
- Mermaid
- Stars
- 571
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
I don't quite understand why the protocol uses custom multicast traffic instead of mDNS?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the protocol's multicast advertisement and any mDNS references in the repository, then determine what documentation would explain the design choice. Done means the rationale is documented or answered with enough protocol context to resolve the question.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100