Skip to content

Conversation

@BentiGorlich
Copy link
Member

Closes #1292

@BentiGorlich BentiGorlich added bug Something isn't working backend Backend related issues and pull requests api API related issues and pull requests labels Jan 31, 2025
@BentiGorlich BentiGorlich self-assigned this Jan 31, 2025
@jwr1
Copy link
Member

jwr1 commented Jan 31, 2025

Do you think it would make sense to have the /.well-known/nodeinfo route available as well?

@BentiGorlich
Copy link
Member Author

That is exactly what I did. One of them is the .wellknown/nodeinfo route and the other is the nodeinfo/2.0|2.1 route

@jwr1
Copy link
Member

jwr1 commented Jan 31, 2025

I see. I didn't realize the ap_node_info route corresponded to the well-known.

Copy link
Member

@melroy89 melroy89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@BentiGorlich BentiGorlich merged commit 198c13b into main Feb 3, 2025
7 checks passed
@BentiGorlich BentiGorlich deleted the fix/nodeinfo-not-available-without-federation branch February 3, 2025 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api API related issues and pull requests backend Backend related issues and pull requests bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Nodeinfo route is inaccesible when federation is disabled

4 participants