Embed this noticeHélène (helene@p.helene.moe)'s status on Friday, 09-Sep-2022 05:09:26 JST
Hélènealright my take is as such: - profile decorations could be used for tumblr-style personalisation of user profiles - could also be extended to overlay avatars, decorate posts from an actor, etc - i don't want to use types for that and i want full customisability - it should be an array of AP objects with some pre-determined ones for common stuff like isCat, by encoding things à la as:Public so that no one has to implement the full stuff or complex stuff
@helene long long looooong time ago i proposed that we have hidden machine-readable profile fields, so that frontends could use those for isCat thing and such
@helene@p.helene.moe meanwhile i'm stlil here wondering why people don't just put the cat ears in the profile picture. e.g. not cropping the picture to a circle and you can use the area outside of the circle. sure it doesn't have the wiggling ears but you can use all kinds of ears you wish with 0 effort required from AP implementations
@hj it's mostly for federation purposes and to signal how i think of it (and to keep consistency), could just be JSON and frontends wouldn't have to deal with it exactly directly, could be interfaced via APIs etc
@helene maybe. I guess it's just different names for same thing - just storing an array of data meant for frontends. For frontends it would possibly be better to just embed jsons instead of linking and whatever the fuxx jsonld is
@helene Well I think it would be nice to describe a base and get it adopted by some others (say pixelfed, honk, friendica, …; Mastodon probably wants too much of a twatter)
Like default user-highlights probably wouldn't be too pleroma-specific. And to me isCat kind of stuff should basically just be animated profiles.
@helene not sure why it should be processed by BE at all, like, frontends just can set any arbitrary data there and it's up for them (and people) to define a schema by convention