Add Smart Message Filter

[andymandias]

This is an attempt to address issue #94, which works locally but may need improving. In particular, I am concerned it will be brittle, since it relies on the formatting of the join/part/quit server messages. But, I didn't see any other way to get the username for the server message without modifying the data structure of the server message. If it would be preferable to modify the data structure of the server message, or if there's a better way to get the user nickname of a join/part/quit server message that I've missed, then I'd be happy to rework this implementation.

Serde was updated because I could not get it to recognize the seconds config for the smart filter otherwise.

[andymandias]

I started work on a version that modifies the the Server struct in data/src/message/source.rs, but the changes were significant enough that I figure I should wait for an official ruling before going any further. Have been using this PR's version of the smart message filter for the last couple weeks and it has been working well locally, so I think it could potentially be used in the meantime.
(Edit to fix reference file path.)

[andymandias]

Put a warning in the commit message but it's probably prudent to do so here as well; the latest commit stores the nickname with join/part/quit messages to check against, but that change results in chat history being clobbered when there's an error when deserializing it. I.e. it will wipe your chat history if you run it. Once that's fixed I think it might be good to go.

[tarkah]

Awesome! We can prevent deser failure with the right serde magic. I'll take a look tomorrow 👍

[andymandias]

The last couple commits have (de)serialization working for me; no longer destroys old logs made using the old Server enum. Added a fallback to the server message filtering so it should work for server messages deserialized from the old Server enum as well (uses the old method that attempts to get the nickname from the server message itself, by necessity).

If there's better serde magic to be employed then I'm happy to wait for that; was just learning a bit more about serde and saw a potential fix.

[casperstorm]

Perhaps you could use let else here:
(psuedo code)

    let Some(server_time) = most_recent_message_server_time else {
        return true
    };

    let duration_seconds = message.server_time.signed_duration_since(*server_time).num_seconds();
    duration_seconds > *seconds

[andymandias]

Looks clearer to me, thanks for the suggestion. Incorporated :)

[tarkah]

@andymandias Checkout the changes I just pushed. It retains backwards compatibility, but uses some more well defined types vs serde magic. By using untagged, we can decode as the old value or the new value. All code paths now set the enum to the new value.

Apologies for the delay getting around to this

[tarkah]

Awesome! LGTM