| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
These warnings arecompiler annoyances where the vala compiler creates C code
that is usually unexpected in proper C code and thus triggers warnings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Sending a disco#info <iq> on being banned from a room is wasteful, and
when _creating_ a room dino asks too soon, receives an error, and gives
up on syncing the room metadata giving subtle, hair-tearing inconsistencies
because flag.has_room_features() returns false for everything.
It's barely noticeable, because if you're banned from a room you
can't query it anyway (though in that case it's still a wasted <iq>),
and if you're creating the room all its fields are empty by default.
I noticed this because I'm experimenting with https://modules.prosody.im/mod_muc_defaults;
dino incorrectly shows moderation off when it should be on in newly
created rooms.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #1728
|
|
|
|
|
|
fixes #1729
|
|
|
|
|
|
|
|
|
|
full-body fallback indication
|
|
|
|
|
|
|
|
Fixes #1666
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and be compatible with vala-language-server
|
|
|
|
|
|
|
|
parsable as int
|
|
|
|
|
|
|
|
Add a field in `Xmpp.Xep.ExternalServiceDiscovery` to keep track
of the `expires` TURN service value and use it (divided by 2) to
restart periodically the external services discovery.
|
|
Co-authored-by: Stanislav Malishevskiy <stanislav.malishevskiy@gmail.com>
|
