Consider excluding crawlers by default
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
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.
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?
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Getting set up
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.
More from nodeSolidServer/node-solid-server
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
nodeSolidServer/node-solid-server#1848 · 2 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nodeSolidServer/node-solid-server#1841 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nodeSolidServer/node-solid-server#1147 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodeSolidServer/node-solid-server#1867 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
nodeSolidServer/node-solid-server#1853 ·
All issues in nodeSolidServer/node-solid-server
Similar issues
-
Complexity: Small P-Feature: Projects page ready for merge team role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
bellingcat/toolkit#905 ·
-
self-care self-care:docs-build-time-investigator
Difficulty 2/5 Half a day Newbie friendliness 76/100
githubnext/gh-aw-cao#14191 ·
Maintainers usually reply within 1 day
-
effort:low impact:medium RAG status: auto-triaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mastra-ai/mastra#25229 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sugarlabs/musicblocks#8984 ·
Maintainers usually reply within 1 day