0eabf108d9
Add a mechanism for redirecting clients after login
...
Implements https://github.com/matrix-org/matrix-doc/pull/1730
7 years ago
d6c33ea0a5
Make CAS a subset of SSO
7 years ago
59196bfd79
Merge pull request #1788 from matrix-org/anoa/proposals_sticky_headers
...
Sticky headers for proposals page
7 years ago
f738f671d1
Sticky headers for proposals page
7 years ago
ec97e1eedb
Merge pull request #1753 from matrix-org/rav/proposal/cs_capabilities
...
MSC1753: client-server capabilities API
7 years ago
c10394d03f
Clarifications thanks to @uhoreg
7 years ago
3e7a5f5ea4
Initial draft for SSO support
7 years ago
09a547d67e
add some cancellation codes, and mention existing verification MSCs
7 years ago
38689a8215
add information about interacting with key requests and define cancellation codes
7 years ago
ff0b9eac76
add ability to start verifications that happen in two stages
7 years ago
c02ecb58ae
mark which fields are required
7 years ago
3b0073a9d1
allow for multiple keys to be verified, for cross-signing
7 years ago
ba39779375
add a conclusion
7 years ago
517754bada
use common key verification message types as per MSC1717
7 years ago
3a5d56467b
reword lead renewals
7 years ago
2377a944c6
Merge branch 'matthew/msc1779' of git+ssh://github.com/matrix-org/matrix-doc into matthew/msc1779
7 years ago
5235293623
spell out the Core Team a bit more
7 years ago
0e246b1477
Update proposals/1779-open-governance.md
...
Co-Authored-By: ara4n <matthew@arasphere.net>
7 years ago
c05000b38d
broaden reasons for dysfunctional core spec teams
7 years ago
2047ba59da
spell out domain spread requirement for spec core team
7 years ago
103d2f4ed2
clarify that the project lead doesn't have casting vote
7 years ago
e730cc02a9
specify how to select a new spec core team lead
7 years ago
7831c04e4c
clarify sytest responsibilities
7 years ago
4fcd38a3a0
clarify guardians' right to override spec core team membership
7 years ago
4994fa115e
X=75
7 years ago
b541c2a247
more formatting
7 years ago
5812450299
spec that we follow redirects
7 years ago
f1ebbc358b
document dismissed options
7 years ago
fb171cadf4
formatting fix
7 years ago
12fc50cea7
clarify that a whitelist is useful for cjdns too
7 years ago
f33a540e6d
Do a SRV lookup before .well-known lookup
...
also other clarifications and corrections.
7 years ago
75c084e987
changelog
7 years ago
74b2db7937
Remove .well-known section
...
This really belongs in MSC1708.
7 years ago
367f61f14a
cleanups and clarifications
7 years ago
ccc1cdaead
Add support for unstable feature advertising via /versions
...
Incorporates https://github.com/matrix-org/matrix-doc/issues/1497
7 years ago
bc1303a1a0
Add a bit of rationale for WIP tags
7 years ago
671527360c
Recommend some kind of WIP tag for MSCs
7 years ago
258aba5fed
Incorporate MSC1693
...
This is largely blatant copy/paste from the MSC with some formatting done to tidy it up a bit.
7 years ago
b824906709
typoes
7 years ago
de6a8b20ff
grammar
7 years ago
c073adac9b
incorporate review from #1318
7 years ago
e6fb403dd0
add TODO for clarifying features v. extensions
7 years ago
303e1081f8
unbreak wordwrap
7 years ago
4538745809
MSC1779: Open Governance for Matrix.org
7 years ago
bd72ecfa58
oops, wrong branch
7 years ago
c5de71843a
MSC1779: Open Governance for Matrix.org
7 years ago
ffe577371d
Add a room version specification
...
The "Room Specification" (or "Room Version Specification") is the specification that defines which room versions do what and are intended to be documents which speak the truth about how rooms operate under the hood.
The approach taken here is a bit different than other specifications. For starters, the specification is versioned in this project instead of relying on the matrix.org repository to track compiled HTML. This is done for a couple reasons, the first being we're still developing the v1 specification while concurrently making a v2 spec and the second being trying to reduce the reliance on matrix.org's repository for specifications.
Because the room spec is built into versions, some changes needed to be made. The `targets.yaml` now has a special syntax for indicating what version something is at, and the changelog generator can handle rendering different versions of the same changelog (as parsed from the RST). Some additional work has been put in to the changelog parsing to allow us to reference the v1 room spec as "v1" without having to sacrifice clarity in the changelog headings.
Finally, this moves the state resolution algorithms into the versioned
spec as a result of MSC1759 (https://github.com/matrix-org/matrix-doc/pull/1759 ).
Note: this does not introduce the concept of versioned schemas (tabs) that I was previously working with. There's currently no use for them, so they are shelved elsewhere.
7 years ago
e0fa00fc34
Some HSes use more than one notary
7 years ago
ca2e9260d4
Update proposals/1753-capabilities.md
...
r0/versions isn't a thing
Co-Authored-By: richvdh <1389908+richvdh@users.noreply.github.com>
7 years ago
4019678661
Update proposals/1753-capabilities.md
...
r0/versions isn't a thing
Co-Authored-By: richvdh <1389908+richvdh@users.noreply.github.com>
7 years ago
Travis Ralston