-
Notifications
You must be signed in to change notification settings - Fork 15
Conversation
fediverse.network implements 2.0 right now, so it would be good to support both. as for translating the blocks/silences, you should add your own fields for that, under the federation object. we can extend fediverse.network for viewing those fields fairly easily. |
is there some reason this was closed? |
@kaniini I am working on implementing your suggestions (2.0 support and federation information). I will reopen once those are done. |
you should probably add the ability to disable the block disclosure as Pleroma has, but it looks pretty good. |
Yeah, some instances don’t disclose their instance block and silence to avoid being harassed for defamation or things like that. |
@ariasuni Thats a good point. Maybe an admin setting to choose wether to disclose this info? |
Because this is going to require more discussion on what should be disclosed and how this should be configured, I definitely don't think we should merge this before 1.0. That said, there may be some minimal version we could add before 1.0 that excludes all of the controversial data, although I'm not sure what such a minimal set is. |
Also FWIW I edited your post to include a content warning for all of the silenced/suspended instance names. Caught me a bit by surprise when I scrolled down the post. |
@clarfon Let me know what y'all think, I could just exclude the federation node from the metadata for now since its optional and we could decide to add it back in the future. |
fwiw you could probably use an environment setting to control the disclosure. i think that is how the other mastodon settings work that are configured from the panel. |
I'll keep this PR fresh and mergeable until we make a decision. It would be really easy to add an admin option to control the sharing of domain block data. |
* Add nodeinfo endpoint * dont commit stuff from my local dev * consistant naming since we implimented 2.1 schema * expanding this to include federation info
I also tried to PR this to upstream mastodon but...I'm pretty sure its going nowhere mastodon/mastodon#10079 Some of the comments are worth noting and thinking about (like removing the activeHalfyear activeMonths nodes) |
any status on this? would be nice to have for fediverse.network and other crawlers |
@kaniini no status because we've not started actually putting stuff into a first release yet. |
cool. thanks for the update. was just wondering what was going on. will try to drop in on mattermost sometime. |
So in terms of merging this, I think that if we started by showing the barest amount of info and the potentially questionable stuff were left behind an opt-in setting for now, that should be good to merge in. We can iron out the details post-1.0. |
@clarfon Let me know what should / shouldn't go in and I can update. I might also have some other updates from when I tried to PR it upstream. |
mainly the instance blocks I guess |
I don't mind leaving in the code to display the instance blocks, although it should be commented out or hidden behind an opt-in config option. Also, I feel that the logic on stating whether registrations are open needs to be changed due to the addition of registration requests in the latest version. |
While the project is still small, we decided to rename the |
What's the status of this ? (on florence side, and PR-side) Can this PR be respin as-is ? |
I think it could be added again as was, yes, but it needed to be submitted again because we renamed the branch. |
Ok thanks ! I can try to get that submitted in the next 2/3 days if nobody does it before that. |
This closes #21
I didn't implement all of the same metadata as pleroma (the metadata stuff is all optional). Specifically I didn't implement the federation node since I was unsure how to translate domain blocks/silences the fields pleroma is outputting.
edits
After talking it thru I now have the federation nodes
You can see this changes in action on my instance:
CW: lots of very bad instance names
https://banana.dog/.well-known/nodeinfo
https://banana.dog/nodeinfo/2.1