Handle different versions of Lemmy Server

[fishcharlie]

Lemmy 0.18.0 to 0.18.3 removed a required property in the API, which caused decoding to fail. It feels like the Lemmy API is incredibly unstable between versions.

We need to figure out how to make this more stable and not throw errors between different server versions.

Some ideas:

• Make every property optional
• Have defaults for each property if decoding fails (ie. empty strings if decoding fails)

Any suggestions on how the community would like to see this handled would be appreciated.

[jstayco]

Sorry, just now seeing this as servers have bumped their versions. If you're still looking for opinions, I think I'd rather see optional properties, so that clients can wrap that however they need to based on the failure as opposed to having to check for default values which might be unique to your library. That second option would require downstream users to have to dive into documentation or source to figure out what they should be matching against.