the cast length limit is enforced at the client level not the protocol, right?

if that's true, there may be some value in using the FIP process to establish some ecosystem standards (similar to how the EIP process can be used to establish ERC standards) for length limits for various types of casts

building /hatsprotocol | 
proudly mid-curving it since 1995

well then, consider that solved 😜

that does lead to another question tho: what if somebody wants to build a farcaster client for longer form discussion? Already there are some discord-style clients in the works (farcord), and that use case likely has a longer natural cast length

should the protocol support that?

We could change it via an FIP: https://github.com/farcasterxyz/protocol/discussions/82

jam.so has long casts

My sense is the simplest v1 is to add some OpenGraph tags to the page to point to a version of the text on Arweave or IPFS and then clients would be free to support full-text preview.