Post #2178346

2026-05-03 09:26 UTC

@kopper@not-brain.d.on-t.work token can be anything: an URL at which the media can now be found, the "template" json document Evan was talking about with the URL filled in, etc... Whatever would make the most sense I guess. @hongminhee@hollo.social

Replies (2)

@kopper@not-brain.d.on-t.work 2026-05-03 09:31

@mariusor@metalhead.club @hongminhee@hollo.social URLs to AS objects makes the most sense to me, as you can Just (assuming valid JSON-LD handling across the ecosystem) paste the link into whatever property to federate it immediately without needing to load more data and the media uploader can do things like introspect width/height/blurhash out of the uploaded file into the document itself, instead of moving that logic to the client (although I imagine it'd be a good idea to allow the client to as:Update the resulting documents to add more metadata if it has to)

Open ##2178347
@mariusor@metalhead.club 2026-05-03 09:33

@kopper@not-brain.d.on-t.work now that I had to think about it for 10m, I really like the idea of getting back a templated object that can further be amended by the client and sent in a Create. *By templated I mean an "incomplete" object which has filled only the properties that make sense: ID, URL, MediaType, Type, AttributedTo,etc... @hongminhee@hollo.social

Open ##2178348