issues i've faced today with the Snapchain HTTP API:

1. docs say camelCase, API says snake_case -- i brought this up a month ago, but it's been around for much longer
2. docs say `REACTION_TYPE_LIKE`, it's actually just `Like`

and not only are the docs wrong, the errors are ambiguous and don't help.

this github link (3 month old report of issue #1 in my post) is a fascinating read.

bug report itself: perfect i would say

team response: "wait so how should this work? how did it use to work? what should we do?"

my ideal team response: "let's fix the docs and figure out the rest later"

this github link (3 month old report of issue #1 in my post) is a fascinating read.

bug report itself: perfect i would say

team response: "wait so how should this work? how did it use to work? what should we do?"

my ideal team response: "let's fix the docs and figure out the rest later"

https://github.com/farcasterxyz/snapchain/issues/357

I make lights blink and play with crypto (cryptography and cryptocurrency). they/them or he/him

The team didn't pick it up, @quazia from Neynar contributed that help. Neynar reported it @flashprofits.eth and Neynar committed.

This is how I imagine an open source project normally should work?

He had a PR merged fixing a bunch of them, but there's still more. They use/recommend the grpc api and so polishing the http api isn't priority.

@quazia said they would take on the work. Did Merkle say elsewhere they'd finish out the issue?

This was also during hubble migration, so it's probably worth revisiting now and throwing a few AI credits at.