Deleted account tombstone
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
To complete https://github.com/solid/solid/issues/14, we need to record what to do with incoming requests after deletion. At the very least, we should make sure that nobody gets the same URI so that they can impersonate the former account owner.
As noted there, we should respond with 410 if nothing else has been recorded, but even better is it to allow users to register their new home and do a 301. At the very least, their new WebID should be saved.
I thought about using the old .htaccess format for this, that we just dump such a file in the former home dir of the user.
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
Start with linked issue #14 and review the proposed .htaccess approach alongside the 410 and 301 behaviors described here. Define and document the chosen rules for deleted-account requests, URI reuse, redirect destinations, and saving a new WebID; the issue is complete when those requirements are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100