@drq I hear that. But it's got to have some good utility for others to get aboard. What's been stated so far is kinda minor, considering the workaround above. And with a major migration cost of replacing a single optional field with a recordset in a new table (on an RDBMS-backed Fedi node which I'd expect to be the vast majority). That'll take some convincing.