Showing off the first deployment of the FIRES reference server to a few people :D
Technical Discussion
1
Posts
1
Posters
0
Views
-
Showing off the first deployment of the FIRES reference server to a few people :D
I've just landed dataset exports, for getting a zip file snapshot of a dataset with files for domain denylists/allowlists, and a retractions file.
The denylist / allowlist should be compatible with the Mastodon Domain CSV files, but unfortunately @Mastodon doesn't support importing a retractions file.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Thank you so much!
-
Audience is added back with this PR: https://github.com/LemmyNet/lemmy/pull/6157
-
Showing off the first deployment of the FIRES reference server to a few people :D
I've just landed dataset exports, for getting a zip file snapshot of a dataset with files for domain denylists/allowlists, and a retractions file.
The denylist / allowlist should be compatible with the Mastodon Domain CSV files, but unfortunately @Mastodon doesn't support importing a retractions file.
-
I feel like that being explicit is more advantageous. There are some subtle edge cases that it helps work around.
Thanks nutomic@lemmy.ml for your attention :)
-
Token revocation and userinfo endpoint are also implemented. iss indication on redirects is also recommended, but not planned yet
-
I believe CIMD is planned, and at some point expiring access tokens & refresh tokens will also land, and maybe in a distant future DPoP too.
DCR has a client registration proliferation problem, which is why Mastodon want CIMD.
-
So, as far as I can tell, Mastodon supports:
Authorization code flow PKCE Authorization server metadataIt doesn't seem to support:
OAuth Dynamic Client Registration Client ID Metadata DocumentsIt instead uses a proprietary endpoint.
thisismissem is that about right? Is there work underway to support CIMD (preferred) or dynamic registration (less good but a more established standard)?
-
@julian Nice workaround. They should describe it in the FEP
