is 410 gone during well known resolution honored? #38
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/resolvematrix#38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Basically, is it reasonable to implement and honor this somehow: https://github.com/matrix-org/matrix-spec-proposals/pull/4188
It's not handled right now, no, but shouldn't be too difficult to implement some sort of handling for it.
That MSC also includes changes like
which would be irrelevant for this library.
There's also:
This could theoretically be done on the library side, however i would be more inclined to have it managed on the homeserver side to keep this library explicitly purely for resolution (not managing backoff logic and similar)
Yes, not high priority, just a feature request for an un-accepted MSC :) I would expect we'd return some kind of a null or fail answer to whatever is behind resolvematrix, doesn't need to handle anything else really