[bug] twitter:description shows bio instead of post in static-fe #644
Labels
No labels
approved, awaiting change
broken setup
bug
cannot reproduce
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs change/feedback
needs docs
needs tests
not a bug
not our bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AkkomaGang/akkoma#644
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
No response
Extra details
No response
Version
3.10.3-197-g98f0820c-develop
PostgreSQL version
No response
What were you trying to do?
Pasting a post from https://akko.wtf/ into Telegram.
What did you expect to happen?
Telegram expanded the post to show the textual content.
What actually happened?
Telegram expanded the post to show the user's bio.
More Information
I am not a user on https://akko.wtf/ nor do I even use this software; however, I am reporting this bug in the hope that the issue can be fixed for those that do.
It looks to me, and I could be completely wrong, that #365 / #373 swapped a problem with
og:descriptionfor a problem withtwitter:descriptionsince they define theirbuild_tagsfor posts differently.OG:
def build_tags(%{object: object, url: url, user: user}) doatdef build_tags(%{object: object,url: url,user: user}) doTwitter:
def build_tags(%{activity_id: id, object: object, user: user}) doatdef build_tags(%{activity_id: id, object: object, user: user}) doI think these need to both take the same parameter structure for the call on
meta = Metadata.build_tags(%{url: activity.data["id"], object: activity.object, user: user})to work.
Severity
I can manage
Have you searched for this issue?