There's already a ConversationNameUpdate event, why is this needed? If it's just for user info, that should not touch chat info, it should only update the ghost.

Ghost updates don't go through the remote event queue, you can call Ghost.UpdateInfo directly with the wrapped *bridgev2.UserInfo object.

• 44a51841 use ghost.UpdateInfo

Updated. UserEvents.Entries is empty when user name/avatar changed, so ConversationNameUpdate won't be triggered.

• 2bb66e20 use black video instead of user avatar

• 9b59afdf Update pkg/connector/handletwit.go […]

• 7db38362 handletwit: handle user info changes (#60) […]

• 6e8a34f0 do not convert video/mp4

• dae1e1e1 twittermeow: support sending voice message (#59)

• 2dc83a76 twittermeow: use event stream for real time updates
• 3e327fad no need to cancel context

• 171279f9 lint

• 75b71dc6 handletwit: fix member list in participant join event

• cce919b3 handlematrix: use client-generated transaction IDs

@tulir @rnons is this ready to merge now?