So I just looked at this. Does this mean that Bluesky does not support EmojiReactions?

If yes, why are you people using it! Go join a serious Fediverse application. Serious of course meaning supporting EmojiReactions.

@helge this is schemas going too far and preventing extensibility

which atproto is built on and if you don’t like that then feel free to make your own schemas and repos and sidecar records.

@trwnh @helge
The extension mechanism is to make a new lexicon, defined by its own schema, that does what you want. For example, being similar to a like, but also carrying an emoji, for greater expressiveness. I would even say you should make that an annotation to a previously created default like, for real, graceful degradation with unknown counterparts.

You lose nothing by doing this, and gain reliable, zero-coordination interop.

@trwnh @helge
I have no shortage of criticism for bluesky, but this isn't one of them

@jenniferplusplus @helge i think proliferation of sidecar records is problematic, especially when it requires awareness of the existence of these records

for what it's worth, i similarly don't think fedi-style "emoji reactions" should necessarily extend from Like activities. that's just something misskey did that we're stuck with.

but the atproto way is like saying that Notes go in one repo and Articles go in another repo, and then every extension prop on a Note goes in a new repo, and so on.

@trwnh @helge
I think we have extremely different ideas about what a repo is

@jenniferplusplus @helge my understanding of it is that bsky goes about it from the other end, they don't link from the post to its likes, they expect some appview to backlink the likes to the post. if that's your model then sure, you can create a new lexicon for emojireacts and stuff them in a new repo and... still expect the appview to stitch this together?

for example, here's a post: https://atproto-browser.vercel.app/at/did:plc:tt7idshnkaltasf5cd6irpwj/app.bsky.feed.post/3lb4d4dkwo22e

how many likes does it have?