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
The Mastodon API has two similarly-named attributes, which are used for different purposes:
uri: URI of the Activity Streams object associated with the API entity (id in Activity Vocabulary)
url: URL of a human-readable HTML representation of the API entity (url property of Activity Vocabulary)
The Account entity has only the url attribute (though the upstream might add the uri attribute someday. cf. mastodon/mastodon#17030) and the Status entity has both the uri and url attributes.
Currently, Kitsune uses the Activity Streams URI of incoming objects for both of the attributes, even though they are not guaranteed to match in general. For example, the Activity Streams representation of Gargron's first post looks like the following:
(Usually though, they are interchangeable in practice, given proper content negotiations.)
I expect fixing this would be fairly easy (just making the database store both the properties separately and making the Mastodon mapper set them separately), but I'm not working on a patch just yet since the database restructure (#458) is underway.
The text was updated successfully, but these errors were encountered:
The Mastodon API has two similarly-named attributes, which are used for different purposes:
uri
: URI of the Activity Streams object associated with the API entity (id
in Activity Vocabulary)url
: URL of a human-readable HTML representation of the API entity (url
property of Activity Vocabulary)The
Account
entity has only theurl
attribute (though the upstream might add theuri
attribute someday. cf. mastodon/mastodon#17030) and theStatus
entity has both theuri
andurl
attributes.Currently, Kitsune uses the Activity Streams URI of incoming objects for both of the attributes, even though they are not guaranteed to match in general. For example, the Activity Streams representation of Gargron's first post looks like the following:
(Usually though, they are interchangeable in practice, given proper content negotiations.)
I expect fixing this would be fairly easy (just making the database store both the properties separately and making the Mastodon mapper set them separately), but I'm not working on a patch just yet since the database restructure (#458) is underway.
The text was updated successfully, but these errors were encountered: