[bug] WebFinger domain not being reflected in account's fqn field #931

Closed
opened 2025-05-16 01:12:06 +00:00 by z411 · 2 comments

Your setup

OTP

Extra details

No response

Version

2025.03-02

PostgreSQL version

15

What were you trying to do?

Mangine frontend gets the full nickname (including the domain) from the "fqn" field of the account API viewpoint.

This works fine except when I set a custom WebFinger domain (domain.org) the frontend still will show the host (fedi.domain.org) because this is what the "fqn" field returns.

... "fqn":"z411@fedi.domain.org"}

Is this intended? The WebFinger domain appears in the OpenGraph tag of the profile in Pleroma-FE just fine.

What did you expect to happen?

I expected the fqn field to reflect the WebFinger domain, like the OpenGraph tag does (Utils.user_name_string() does this), as the Mangine frontend uses this field to display the nickname.

What actually happened?

It still shows the full host as the domain, probably because it's using User.full_nickname() which always return the nick with the host even if a WebFinger domain is set. A few other locations also use this function. Is this intended?

Logs

No response

Severity

I can manage

Have you searched for this issue?

  • I have double-checked and have not found this issue mentioned anywhere.
### Your setup OTP ### Extra details _No response_ ### Version 2025.03-02 ### PostgreSQL version 15 ### What were you trying to do? Mangine frontend gets the full nickname (including the domain) from the "fqn" field of the account API viewpoint. This works fine except when I set a custom WebFinger domain (domain.org) the frontend still will show the host (fedi.domain.org) because this is what the "fqn" field returns. ... "fqn":"z411@fedi.domain.org"} Is this intended? The WebFinger domain appears in the OpenGraph tag of the profile in Pleroma-FE just fine. ### What did you expect to happen? I expected the fqn field to reflect the WebFinger domain, like the OpenGraph tag does (Utils.user_name_string() does this), as the Mangine frontend uses this field to display the nickname. ### What actually happened? It still shows the full host as the domain, probably because it's using User.full_nickname() which always return the nick with the host even if a WebFinger domain is set. A few other locations also use this function. Is this intended? ### Logs _No response_ ### Severity I can manage ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.
z411 added the
bug
label 2025-05-16 01:12:06 +00:00
Owner

Yes, this feld is an *oma extension and using the full API domain is intentional.

To get the nickname with the WebFinger domain you should use the standard acct field

Yes, this feld is an \*oma extension and using the full API domain is intentional. To get the nickname with the WebFinger domain you should use the standard `acct` field
Oneric added
question
and removed
bug
labels 2025-05-16 09:35:48 +00:00
Author

Thanks for clarifying. I looked at that field before posting this but it only has the nickname, not the domain:

"acct":"z411"

This is a local account, and I can't see the WebFinger domain anywhere in the response. Is this misconfiguration on my part? Either way I think I'll go to the forums instead.

Thanks for clarifying. I looked at that field before posting this but it only has the nickname, not the domain: `"acct":"z411"` This is a local account, and I can't see the WebFinger domain anywhere in the response. Is this misconfiguration on my part? Either way I think I'll go to the forums instead.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#931
No description provided.