Utility Types Working Group

[LemmaEOF]

As I've been tinkering with ATProto dev, I've come across bunch of little utility types that would be nice to have but aren't really present yet. A few of these include:

• Translatable strings with representations in multiple languages and a fallback to display if a translation is unavailable
• CID-less objects for holding a URI reference in a union to an object which is subject to change
• Human-readable slugs to act as easier links to records with non-human-readable key types

I'm not entirely sure I'm allowed to formally propose one as I'm not a steering committee member, but I would love a working group focused on small utility types in order to get some nicer developer ergonomics.

[trezy]

+1 for this, tho I'd wager localization may warrant its own working group.

[verdverm]

yeah, localization gets complicated quickly when you consider

• ideally I only need to fetch one translation when getting a record, at the same time there are cases where you want all of them
• translations may come much later, what if it comes from a third party?
• block basked content, such as one of the popular long-form content formats out there
• how do the various libraries out there expect to receive translation information

[LemmaEOF]

Yeah, I'd be more than fine with flagging translation as out of scope honestly.