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

... for cross-client compatibility.

It would be a real shame if different microblogging clients used different length limits and a post made on eg herocast was too long for and therefore didn't show up on warpcast

Same with cross-compatibility b/w future potential forum-style or discord-style clients

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?