You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If accounts are hosted in server that not supporting joined date federation, we should hide "Joined Date" from Web UI.
in API, I think we should split created_at and joined_at. If account is local user, joined_at simple returns created_at. if account is remote user, set "Date that server first knows this account" to created_at, and if accounts are hosted in server that supporting joined date federation, set "Joined Date" to joined_at (if not supported, set null to joined_at).
Actual behaviour
If accounts are hosted in server that not supporting joined date federation, Web UI displaying "Date that server first knows this account" (old created_at) as "Joined Date".
Steps to reproduce the problem
Create New Mastodon Server (in 3.4.0rc1 or later)
Input any URL of accounts (that are hosted in server that not supporting joined date federation) to Search Box
Open Profile
Specifications
Mastodon 3.4.0rc1
The text was updated successfully, but these errors were encountered:
Expected behaviour
If accounts are hosted in server that not supporting joined date federation, we should hide "Joined Date" from Web UI.
in API, I think we should split
created_at
andjoined_at
. If account is local user, joined_at simple returnscreated_at
. if account is remote user, set "Date that server first knows this account" tocreated_at
, and if accounts are hosted in server that supporting joined date federation, set "Joined Date" tojoined_at
(if not supported, setnull
tojoined_at
).Actual behaviour
If accounts are hosted in server that not supporting joined date federation, Web UI displaying "Date that server first knows this account" (old created_at) as "Joined Date".
Steps to reproduce the problem
Specifications
The text was updated successfully, but these errors were encountered: