nodeSolidServer / nodeSolidServer/node-solid-server
Consider excluding crawlers by default
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
Anecdotally, we have had a number of users complain about their name and email address being made available to spiders. This could be done by adding a robots.txt file to a pod.
Solid, being a privacy first framework, should consider excluding crawlers by default.
It would be relatively easy subsequently to turn it on via a dashboard, or an app.
The downside to the approach is that an adoption vector of finding people via search engine is lost. And ability to create a social graph.
I'm personally unsure on the trade off here.
Good idea / Bad idea / Thoughts?
Contributor guide
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
No files, tests, or entry points are named. First clarify whether crawler exclusion should be the default and how users would opt in through a dashboard or app, then inspect the server's pod-serving behavior. Done means an agreed policy and an implementation plan that accounts for the privacy and discoverability trade-off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100