Tom Dryer

I think this is related to the snap package [not supporting Unicode properly](https://github.com/tdryer/hangups/issues/232#issuecomment-216425793). Since notifications also won't work, you could work around this by disabling notifications.

You can use `Conversation.watermarks` to get the timestamp that each participant has read up to. If a timestamp is greater than the timestamp of the message, that user has read...

You might need to add a line break segment to the message instead of using a newline character.

`ChatMessageSegment.from_str` can parse a string into segments for you. For example: ``` >>> import hangups >>> hangups.ChatMessageSegment.from_str("hello\nworld") [, , ] ```

> Is this a case that actually happens, or are we guaranteed to always have at least one event for any conversation? I have some empty conversations with no events,...

I'm not sure how that line of code could be raising that exception. Did you modify hangups somehow?

I think this is caused by `mechanicalsoup` using prepared requests, which ignore `HTTP_PROXY` by default (https://github.com/requests/requests/issues/3190).

Right now auth is using `mechanicalsoup` which is synchronous-only. If we [drop the automatic login method in the future](https://github.com/tdryer/hangups/issues/350#issuecomment-434921805), it should be easy enough to port to async.

> Example - send_message.py is ...(sorry)... pretty much unreadable. I can sort it out but by the time I get to the end of the ~20 lines I get tripped...

> What I find to be odd, is that I told someone to turn that feature off in their account's settings, and it worked for them. And mine hadn't been...