- Update to version 0.8.2:
  * Historical encrypted messages can now be decrypted with old 
    megolm keys retrieved from SSSS.
  * The User library API is getting prepared to be split into 
    that for room members (RoomMember) and user profiles 
    (stays in User for now) in 0.9, deprecating most of User 
    methods that accept Room for the member context.
  * Along the same lines: functions to (un)ignore users by userid 
    rather than User* are introduced; the old signatures are 
    deprecated now and will be removed in 0.9.
  * More efficient (less cache-wasting) avatar retrieval.
  * Property for querying connection's account_data.
  * Fix brain-split when checking event types on some 
    Linux distributions.
  * A new event class for m.room.server_acl.
  * The library supports defaulting direct chats to E2EE now.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to version 0.7.0:
  * E2EE is the biggest part of this release, 
    + The following parts of E2EE are known to work:
      - foundations additional contributions and refactoring.
      - Olm/Megolm signalling with our parties/devices.
      - managing device and one-time keys.
      - sending and receiving (monstrous new encrypted messages.
      - encrypting/decrypting attachment.
      - retrieval and decryption of historical messages keys 
        for which are already in the database.
      - device verification.
    + What is not there yet:
      - historical Megolm sessions are not requested from other 
        devices/parties, so you will see quite a few undecryptable
        messages in rooms with past communication - this might be 
        fixed (if possible without breaking the API) in further 
        0.7.x releases.
      - secure server-side storage (SSSS) is not supported at 
        all for now, and will likely require API breakage so 
        will come in 0.8.
      - soft logout is not supported; this is also a subject of 0.8.
    + Because there's no soft logout the database for a given account 
      is completely reset upon a successful login attempt. This may 
      come as a very unpleasant surprise if you don't keep your 
      login session between client restarts; but this is a necessary
      trade-off for the current feature set (see #546 for the 
      discussion). Together with the rest of the above not-there-yet
      list, this means that you MUST NOT use E2EE with 
      libQuotient-backed clients as your only device(s) on 
      the account - there's quite a risk of losing encrypted

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to version 0.6.11:
  * Just after 0.6.10 was out another nasty bug has been discovered,
    preventing from proper usage of URLs with an unescaped double-hash (##),
    which may come when a matrix.to URL is generated for a bridged IRC channel
    (and it even got a very nice number #512). Aside from this fix, 
    quotest will not return with success code 0 any more if it failed to 
    even start testing for some reason (#496).

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to versiosn 0.6.10:
  * Yet another maintenance release of the stable branch, fixing an 
    issue (#510) with invites not showing up in some cases 
    (especially on less active/smaller accounts).

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to version 0.6.9:
  * Here's one more stable branch release of libQuotient, 
    fixing a rare assertion failure due to uninitialised
    read marker when new events arrive and all history 
    is already loaded.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to version 0.6.8:
  * Retain the current room member avatar when renaming the user 
    for the room.
  * When displaying the room, notification/highlight counters are 
    no more reset. This never really worked, with the notification 
    and highlight counts jumping to zero and then back to the 
    original value if the timeline hasn't been completely read; 
    now that read receipts are correctly sent, the counters 
    can be left to the homeserver to update 
    (while E2EE is not around).
  * Fix the missing percent encoding in User::fetchProfile(), 
    leading to problems around historical userids that still 
    have slashes.
  * CS API files have been regenerated from the new matrix-doc 
    after revamping the layout and tooling; the library API didn't 
    change, but doc-comments are now in Markdown rather than 
    ReStructured Text.
  * Update GTAD configuration to version 0.8 of the tool.
  * Fix potential linking errors around quotient_common.h.

• Files Changed
• Browse Source

• Browse Source