Conversation
Notices
-
@hankg I'm fine with returning the resource-id in some friendica group. But I don't like this guesswork of the first and second point. This should be handled differently.
-
@hankg Yeah, that list would be an idea.
-
@heluecht So you would prefer we return IDs for each of the images when queried from the friendica side which can then be used to seed the Mastodon endpoint?
-
@hankg We can work with a second parameter like resource_ids. But the problem is that we then have got to tell the size as well.
-
@heluecht Ah you mean picking size 0, 1, or 2 if we provide resource-id instead of ID? That would be solved by returning the IDs of the images when we query it from the Friendica side. It would then not require any special logic in the Mastodon API or even changes there. We just need to decide if we break the current Friendica API format by introducing it directly in the link array, produce a second field of IDs, or a second field of "scales" or something which itself is a collection of maps with IDs and links.
-
@heluecht Which of the the above options do you think would be best:
a. break links by change the elements to be IDs and URLs
b. new field "ids" just of IDs
c. new field "scales" (or something) which is an array of elements containing the ID and URL of each scale level?
d. Same as C but with more metadata perhaps?
-
@hankg D:
Michael Vogel
hankg
All bartle content and data are available under the