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

That's a fair question, but my disagreement is with the suggestion that Merkle didn't prioritize it because Neynar said that they would take it.

https://github.com/farcasterxyz/snapchain/pull/363

i like to think a company that has tons of money and pays people a ton of money would have a PM that says "hey we got a new bug let's track it and put it in the pipeline", this isn't a charity open source project this is a real company, i think? no?

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?

@jc4p spent the last couple days cleaning up docs. 

Inconsistencies should be resolved now at https://snapchain.farcaster.xyz/
We also updated https://docs.farcaster.xyz/ to remove deprecated Hubble references and point to updated Snapchain docs. 

Our docs surface area is big, let us know if you notice any remaining inconsistencies and will prioritize fixing!

father, meditator and (freelance miniapp builder and consultant). this month working for $runner. shipping on friday

my idea would be "hire a PM and instill a process of fixing things twice (once short term once long term) each time a user facing bug occurs" but that isn't likely to occur

have you tried giving ideas?

i have. and don't want to do it anymore