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
See some of those fields rendered, egname, icon, image, but not summary or attachment
Expected behaviour
summary is rendered as bio, attachments rendered as profile metadata links
Actual behaviour
Neither are visible
Detailed description
Here's a screenshot of the Mastodon-rendered profile on indieweb.social (running 4.0.2), without bio or links visible. I sent an Update activity to the https://indieweb.social/inbox shared inbox, and got a 202, but no change.
Specifications
Mastodon 4.0.2
profiles viewed in Firefox 107.0, macOS 13.0.1
Thanks in advance for looking! #1557 and #4906 are loosely related but don't mention summary or attachment specifically. Tracking issue on my side is snarfed/bridgy-fed#323.
The text was updated successfully, but these errors were encountered:
Argh, never mind! This was user error. I was missing name from the attachment links, they showed up once I added that. And evidently summary worked after all, mastodon.social evidently shows it, I'm just (still) seeing an old cached copy on indieweb.social.
Steps to reproduce the problem
name
,icon
,image
,summary
,attachment
(thePropertyValue
objects)name
,icon
,image
, but notsummary
orattachment
Expected behaviour
summary
is rendered as bio,attachment
s rendered as profile metadata linksActual behaviour
Neither are visible
Detailed description
Here's a screenshot of the Mastodon-rendered profile on indieweb.social (running 4.0.2), without bio or links visible. I sent an
Update
activity to the https://indieweb.social/inbox shared inbox, and got a 202, but no change.Specifications
Mastodon 4.0.2
profiles viewed in Firefox 107.0, macOS 13.0.1
Thanks in advance for looking! #1557 and #4906 are loosely related but don't mention summary or attachment specifically. Tracking issue on my side is snarfed/bridgy-fed#323.
The text was updated successfully, but these errors were encountered: