NodeBB

i'll hack around and find out

i could dedicate an "actor_icons" table that doesn't require the "id" for this. but it's a stupid solution, very stupid

in #activitypub, an remote actor may or may not have an icon, which essentially it's the actor's avatar metadata information.

but in #mastodon api, the icon object doesn't have an "id" field, so i cannot correctly map this icon into a more generic "attachments" table (because it requires the presence of id field) in my local instance when i import the remote actor.

some ppl created icon as jsonb to facilitate this non-generic "icon" field.

which isn't a great solution in its api design.