Skip to content

Decide on special characters to accept/reject #221

@dreeves

Description

@dreeves

My Latest Arguments Against Slashes In Particular

  1. We may want slashes to have special meaning so we shouldn't allow them willy-nilly in the meantime and make a (bigger) backwards compatibility mess.
  2. Bots and humans try dropping stuff after slashes, like going up a directory. This would be a feature in the case of @chrisbutler's folders idea but is bad in the status quo.
  3. A related problem is that it's not obvious that URLs like alice.commits.to/reply_to_bob/by/5pm and alice.commits.to/reply_to_bob/by/4pm are treated as entirely distinct. Change those to alice.commits.to/reply_to_bob_by_5pm and alice.commits.to/reply_to_bob_by_4pm and it's more clear that the system won't try to do any magic to treat those as referring to the same underlying promise.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ADOConsensus needed on what to Actually Do (or "much ado about ∅"), AKA questionMENMendoza = need to resolve before accepting more beta usersUVIUser-Visible Improvement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions