@swizzard
In my understanding, account-ids and status-ids are expressed by HastodonId defined at Type.hs.
Would you use HastodonId instead of String?

And I noticed several points that needed to change type into HastodonId in addition;

• Types.hs: statusInReplyToId, statusInReplyToAccountId

  hastodon/Web/Hastodon/Types.hs

  Lines 230 to 231 in 334b19d

  	statusInReplyToId :: Maybe Int,
  	statusInReplyToAccountId :: Maybe Int,

• Option.hs: inReplyToId, mediaIds

  hastodon/Web/Hastodon/Option.hs

  Lines 283 to 287 in 334b19d

  	inReplyToId :: IsPostStatusOption a => Int -> a
  	inReplyToId i = mkOption "in_reply_to_id" (Just $ show i)
  	mediaIds :: IsPostStatusOption a => [Int] -> a
  	mediaIds l = mkArrayOption "media_ids" $ show <$> l

@as-capabl done. i'm a little uncomfortable having account ids and status ids and media ids all be HastodonIds, since they represent pretty different things, but that can be put off for another commit. Similarly, it may be worth newtyping ids to prevent them from getting mixed up with other strings like status content

@swizzard Thanks a lot! 👍 I agree that various ids should be expressed by distinct types.

closed in favor of #27