* tests: short link type, QR code capacity and contact statuses
* core: validate the type of short links
* android, desktop: show contact info for addresses above QR code capacity
* ui: show chats with rejected contact requests
* tests: short link types with group, channel and contact data
* core: validate short link type against link data
* tests: fix short link data test
* tests: group data in invitation link before its first use
* tests: connect via address in contact profile with group link
* core: connect via contact address only with address links
* core: parse short link data once, by link type
* core: types of short link data parser
* core: test short link types and contact rejection, record app fixtures
* android, desktop: test contact info, link alerts and rejected contacts
* ios: test invalid link alerts and rejected contacts in the chat list
* desktop: contact info tests find texts without app resources
* ui: core responses of invalid link plans and a rejected contact request
* desktop: contact info tests provide the app bar handler
* core: normalise file and message keys in app test fixtures
* core: normalise deletion times in app test fixtures
* desktop: test that a QR code above capacity is not shared on tap
* core: test relay link checks and known channel refresh from link data
* core, ui: chatItemUpdated event has the previous item
Apps change counters by the difference between the previous and the new item, and insert an updated item only when the update created it.
* core, ui: a recreated item is sent as newChatItems
An update of a locally deleted message creates it again and sends it as a new item, so chatItemUpdated always has the previous item and the apps never insert on an update.
* core, ui: previous item is optional and has no chat info
Events from older remote hosts decode without it; the apps then insert the item if it is not loaded and change no counters.
* core: catch-up subscriber gets an edited history post as a new item
* ui: updates in another profile do not notify, as on iOS
* core, ui: one type for the updated item and its previous version
AChatItemUpdate has the chat info, the new item and the previous item with the same chat type and direction. Its JSON is the JSON of AChatItem with an optional prevChatItem; the event keeps the key chatItem.
* core: tested event key, previous item reactions, cleared mentions
One function renames the event field to chatItem for JSON and docs, and the test checks the wire key and compatibility with AChatItem. The previous item of a direct edit has its reactions. An edit that removes all mentions sends the item without them.
* core: test that an edit removing mentions sends the item without them
* core: event JSON field mapping inline in the TH options, for the Windows build
* core: file chat item update checked in one store transaction
* core: test that a file reset by unknown relays sends its previous item
* core, ui: chatItemUpdated event key chatItemUpdate
* core, ui: chatItemUpdated always has the previous item
* ci: mcp scope tests the plugin with its published dependencies
* core: mention of the user follows edits of a group message
* core: previous item of a prohibited file is read before the prohibition
* android, desktop: missed call check inline, counter test with core pairs
* ios: spec link of the chatItemUpdated event
* core: mention edits in support chats update members requiring attention
* core: one rule for the mention of the user in received and edited items
* core: record item events of updates for app tests
* android, desktop: remove the missed call notification of updates, never shown
* android, desktop: test item updates on events recorded by the core
* ios: test item updates on events recorded by the core
* docs: plan of app tests of item updates, recording tests in the CI guide
* core: record the response to an update after its item status is final
* ios: notification manager replaceable in tests
* ios: test notifications of updates and the update response
* android, desktop: test the recorded update response
* docs: plan with iOS notifications and the update response
* core: recorded response to an update of a sent message
* core, ui: plan name alert tests against core fixtures
* core: write name lookup responses to app fixtures in name tests
* android, desktop: name alerts tested against core fixtures
* core, ios: plan Swift fixtures and iOS unit tests of name alerts
* core: write name lookup responses in the Swift form to iOS fixtures
* ios: name alerts tested against core fixtures
* core: write both app fixtures of a name test in one run
* ui: add name lookup responses written by the core tests as fixtures
* core: keep the fixture writer of name tests to the forms it receives
* desktop: run name alert tests in the US locale
* ios: one switch for the title and effect of name alert actions
* docs: name alert tests in the app specs, CI guide and plan
* docs: known gaps of the name alert tests in the plan
* ui: restore the name alert code and the iOS project of master
* core: record name lookup responses and name parses for app tests
* android, desktop: test name alerts of planAndConnect on recorded responses
* ci: run the app tests for a change of the name fixtures
* core: name lookup responses and name parses recorded by the core tests
* docs: plan of app views tested on core responses
* ios: test name alerts of planAndConnect on recorded responses
* ci: iOS unit tests in the iOS job, the app launched on stub migrations
* android, desktop: core hooks below the externals, in the specs
* ios: name alert tests compile with the converter at file scope
* ui: the moved name test expects the alert to open a chat with the new address
* core, ui: app test fixtures under tests/fixtures/api
* core: record the responses of the name lookup flows that the apps test
* core: record URI parses, and normalize the random values of fixtures
* android, desktop: URI parse hook and event processing for tests
* ios: URI parse hook for tests
* desktop: full failure messages of tests
* core: domain errors view compiles with GHC 8.10.7
* core: normalize parses and profile send times in fixtures
* core: record the parses of the chat list search
* core: recorded responses of the name flows and the contact address
* android, desktop: test name alerts, buttons, search and name view
* ios: test name alerts, buttons, search and the moved event
* docs: plan, specs and CI guide of the app tests
* core: record lapsed names without grace, channels lapsed, moved, failed
* android, desktop: test the prepare domain, cleanup, search row and reasons
* ios: test the prepare domain, onOpen and the event's terminal text
* core: the grace date of an expired name in tests is in seconds
* core: recorded plans of lapsed, moved and unverified names; relays normalized
* ios, android, desktop: test lapsed, moved and unverified channel names
* docs: the follow-up tests and the gaps they leave
* ios: wait for the alert of a failed prepare before the next test
* ios: show the alert of a failed new chat on the main thread
* core, ui: plan name alert tests against core fixtures
* core: write name lookup responses to app fixtures in name tests
* android, desktop: name alerts tested against core fixtures
* core, ios: plan Swift fixtures and iOS unit tests of name alerts
* core: write name lookup responses in the Swift form to iOS fixtures
* ios: name alerts tested against core fixtures
* core: write both app fixtures of a name test in one run
* ui: add name lookup responses written by the core tests as fixtures
* core: keep the fixture writer of name tests to the forms it receives
* desktop: run name alert tests in the US locale
* ios: one switch for the title and effect of name alert actions
* docs: name alert tests in the app specs, CI guide and plan
* docs: known gaps of the name alert tests in the plan
* ui: restore the name alert code and the iOS project of master
* core: record name lookup responses and name parses for app tests
* android, desktop: test name alerts of planAndConnect on recorded responses
* ci: run the app tests for a change of the name fixtures
* core: name lookup responses and name parses recorded by the core tests
* docs: plan of app views tested on core responses
* ios: test name alerts of planAndConnect on recorded responses
* ci: iOS unit tests in the iOS job, the app launched on stub migrations
* android, desktop: core hooks below the externals, in the specs
* ios: name alert tests compile with the converter at file scope
* ui: the moved name test expects the alert to open a chat with the new address
* core, ui: app test fixtures under tests/fixtures/api
* core: record the responses of the name lookup flows that the apps test
* core: record URI parses, and normalize the random values of fixtures
* android, desktop: URI parse hook and event processing for tests
* ios: URI parse hook for tests
* desktop: full failure messages of tests
* core: domain errors view compiles with GHC 8.10.7
* core: normalize parses and profile send times in fixtures
* core: record the parses of the chat list search
* core: recorded responses of the name flows and the contact address
* android, desktop: test name alerts, buttons, search and name view
* ios: test name alerts, buttons, search and the moved event
* docs: plan, specs and CI guide of the app tests
* plan: mcp-agent-profile
* plan: mcp-agent-profile, answers Q1 (b) and Q2 (b)
* plan: mcp-agent-profile, lists render on GitHub
* mcp: User has the peer type of a person
* ui: show the peer type placeholder of members and contacts
* plan: mcp-agent-profile, answers to the user's notes
* ui: compare link icons with peerTypeIcon in the desktop test
* ui: snapshot references of the peer type placeholders
* android: peer type placeholder of a caller on the lock screen
* ios: agent icon of a link in the compose context at text size
* plan: mcp-agent-profile, review fixes
* ios: snapshot references with the compose context line of a link
* core: send a change of the peer type alone to groups
* mcp: User's peer type reaches existing session groups
* plan: mcp-agent-profile, Q1 (a)
* mcp: mark the agent profile item delivered in the roadmap
* core: ignore introductions of own member and from non-announcing members
* core: check member introduction in the same transaction
* core: reject introductions of removed members
* tests: describe the channel introduction test by what it checks
* ui: references of the flat layout names, italic and paragraphs
* ui: what's new references with the crowdfunding link
* core, ui: report reason with rule text, ios gaps as in plain text
* ui: references of report reason, ios gaps and right-to-left text
* core: use the member key sent by the channel owner on role change
* core: check the member key on role change in one branch, rename test
* core: describe the role change test by what it checks
* docs: plan resized profile images from files
* core: crop and resize profile images set from files
* docs: profile image from a file in the chat relay docs
* core: faster crop of profile images
* bots, nodejs: document chat, connection, member contact and network commands, typed commands in library
* bots, nodejs: restore apiConnect, wrap domain once, test all connect responses
* nodejs: JSDoc for new methods
* docs: plan for bot API commands and typed Node library methods
* tests: channel prepared with a domain has a verified SimpleX name
* docs: apply review fixes to the plan for bot API commands
* docs: apply second review pass to the plan for bot API commands
* docs: refer the bot API plan to the rewritten test commit
* docs: record decisions in the plan for bot API commands
* docs: plan tests of the generated Python command strings
* python: test the generated strings of the documented commands
* docs: plan the message information command for bots
* bots, nodejs: message information with the file servers for bots
* docs: plan the relay approval option of receiving files in Node
* nodejs: receive files without approving unknown relays
* docs: plan the user servers command for bots
* bots, nodejs: user servers and relays by operator for bots
* nodejs: document the message information method
* docs: plan the file upload progress event for bots
* bots: file upload progress event for bots
* bots: drop the file upload progress event
* docs: drop the upload progress event plan
* nodejs: document user servers and relay approval of received files
* core: keep channel profile from the owner's link when joining
* core: rename test of the channel profile on joining
* core: apply channel profile from link data when connecting
* WIP: Haskell impl of resizeImageToStrSize
* WIP: add FFI export wrapper
* WIP: switch ios resizeImageToStrSizeSync to backend
* WIP: fix resizeImageToStrSizeSync
* WIP: add JNI wrappers
* Add non-base64 resize and cWriteImage
* WIP: add chat_write_image
* fix resizeToStr
* fixes
* fix syntax, raise jpeg quality back
* add chatWriteImage
* Fix cfArgs in tests
* Use jpeg-turbo encoder
* add nix pins
* bump jpeg-turbo
* add CI deps
* add encoding funs to android lib
* bump jpeg-turbo for 20.04 fix
* jpeg-turbo fix for 8.10
* android fixes
* Bump jpeg-turbo
* set static flag for jpeg-turbo
* Fix nix for aarch64/android
* Fix android C api
* Fix resize in android
* Bump hs-libjpeg-turbo
* target correct override
* override android lib from android pkgs
* add macos build tweaks
* bump hs-jpeg-turbo for 8.10 fixes
* more build fixes
* make ios compile
* Always use pkgconfig for libjpeg-turbo
* WIP: debug libjpeg in ubuntu pkg-config CI
* Add pkg-config to dockerfiles
* Add libturbojpeg to dockerfiles
* Use -dev version of libturbojpeg in dockerfiles
* Install pkg-config in windows CI
* Disable flag for custom libturbojpeg linking options
Workarounds relocation error on x86_64-linux with gcc:
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libturbojpeg.a(turbojpeg.c.o): relocation R_X86_64_TPOFF32 against `errStr' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: failed to set dynamic section sizes: bad value
* WIP: debug libjpeg in windows pkg-config CI
* WIP: debug libjpeg package in windows CI
* core: image resize module and buffer FFI
* ci: link libjpeg-turbo statically on all platforms
* ui: resize images in the core
* core: rename image resize functions to chat_resize_image and chat_resize_image_uri
* ci: restore whitespace in build.yml
* ci: build libjpeg-turbo 3.1.4.1 from a submodule
* core: hs-jpeg-turbo from github.com/simplex-chat
* nodejs: resize images
* python: resize images
* core: hs-jpeg-turbo from gitlab.com, the GitHub import lacks LFS objects
* core: generate /img previews
* ci: link libjpeg-turbo on Windows without pkg-config
* ci: build libjpeg-turbo on Windows with the GHC toolchain
* docs: plan for image resizing in the core
* docs: update image resizing plan
* ios: prevent crash when wallpaper image cannot be resized
* android, desktop: raise an error when an image cannot be resized
* docs: update spec references for image resizing
* docker: build the CLI image from a clone without submodules
* docs: apply review fixes to image resizing plan
* docker: build the CLI from a git worktree with the submodule present
* docs: apply second review to image resizing plan
* docs: point image resizing plan at the rewritten commit
* core: choose image format by transparency in chat_resize_image
* nodejs: resize images to the app sizes
* python: resize images to the app sizes
* nodejs, python: describe the core modules as used for image resizing
* docs: add license notices of the image libraries
* ci: describe the avatar method without attributing it to the apps
* ci, ios, nix: remove the libjpeg-turbo build outside cabal
* python: name resize_image in the core module text
* nodejs, python: describe resizing to the app image sizes
* core: refuse images larger than the supported size
* core: resize to JPEG images with a side above 65500 pixels
* docs: record image resizing decisions for the bundled libjpeg-turbo
* core, docs: build libjpeg-turbo and stb from the fork submodules
* docs: record the fork pins in the image resizing plan
* core: resize images to at most 4320 pixels per side, refuse above 16384
* docs: record the image side limits in the image resizing plan
* core: pin the rebased hs-jpeg-turbo fork
* core: pin the hs-jpeg-turbo fork without package.yaml
* docs: plan scaled JPEG decoding and EXIF orientation of images
* docs: copy the JuicyPixels-stbir licence of the pinned fork
* core: pin the hs-jpeg-turbo fork with scaled JPEG decoding
* core: decode JPEG at the display size, up to 65500 pixels per side
* core: rotate JPEG images by their EXIF orientation
* docs: refer the image plan to the JPEG decoding code
* docs: record the approved image processing decisions
* core: limit JPEG decoding memory to 1024 MB outside iOS and Android
* docs: name JPEG decoding in the libjpeg-turbo notice
* docs: plan image resizing from files and the decisions of 26 Oct
* core: scale images in one Catmull-Rom pass with sharpening
* docs: plan image sizes at a fixed quality
* core: resize images at a fixed quality to fill the size limit
* core: resize images from a file path or a file descriptor
* ios, android, desktop: resize picked images from their files
* core: encode resized images with mozjpeg
* tests: check descriptor closing by the file it refers to
* core: raise JPEG quality only for a full-size image below 97% of the limit
* ci: name the mozjpeg submodule in the Windows cleanup comments
* docs: refer the image plan to the current code
* docs: refer the image plan to the code merged with master
* core: export every image resizing function from each library
* core: close the file descriptor when its handle cannot be created
* docs: count the C sources of mozjpeg with the arithmetic decoder
* core: use the reviewed hs-jpeg-turbo and JuicyPixels-stbir forks
* ci: build the armv7a Android core library on request
* core: round image heights half up in the size search
* ios: describe the file image resizing functions in SimpleX.h
* ci: pick, preview and send images in the Claude app tests
* core: decode PNG images with libspng and refuse other formats
* core: encode PNG with libspng, keeping the smaller filter choice
* ci: pick, preview and send images in the scripted app smoke tests
* flake: build the PNG decoder package in nix builds
* ios: remove the copy of a picked image after sending it
* core: refuse image files larger than the decode memory limit
* core: scale a JPEG image to its largest size once per resize
* core: bisect JPEG quality without a step function
* core: reduce the memory used to sharpen and to decode PNG images
* android, desktop: pass the image format to the core as an integer
* android, desktop: fuse the preview conditions of picked media
* android, desktop, ci: check that the core resized the smoke test images
* python: remove the docstrings of the explicit image resizing functions
* docs: add the second review fixes to the image plan
* ci: tap the iOS attachment button by its accessibility label
* core: keep the colour profiles of resized images
* docs: add the colour profiles to the image plan
* ci: wait up to 30 s for the new group screens in the iOS smoke test
* ci: pick the Android smoke test images from their own photo folders
* ci: tap the iOS photo picker by position, as its tree is not shown
* ci: pick the test card and the logo by their iOS picker positions
* core: update JuicyPixels-stbir with the stb_image_resize licence terms
* core: write a fixed Display P3 profile for Display P3 images only
* core: do not keep the input image in memory for its colour profile
* core: read the JPEG segments once for the orientation and the profile
* core: read an image file into one buffer of its size
* docs: add the third review fixes to the image plan
* core: resize images with Display P3 or no profile, not profile bytes
* ci: check the pixel sizes of the images sent in the iOS smoke test
* core: update hs-jpeg-turbo with PNG chunk limits and encoder fixes
* docs: list Compact ICC Profiles, libspng and miniz in the dependencies
* android, desktop: reword the picked media preview comment
* docs: refer the image plan to the code merged with master
* ci: render the iOS snapshots before the images case
* ci: dismiss the snapshot tests' camera alert before the iOS images case
* core: update hs-jpeg-turbo with tests and the JuicyPixels-spng synopsis
* core: pin hs-jpeg-turbo and JuicyPixels-stbir in simplex-chat repositories
* update ios core library
* core, ui: accept only JPEG and PNG image data
* core: update JuicyPixels-stbir
* docs: plan for the iOS copy of picked images
---------
Co-authored-by: IC Rainbow <aenor.realm@gmail.com>
Co-authored-by: Evgeny Poberezkin <evgeny@poberezkin.com>
Co-authored-by: Alexandre Esteves <alexfmpe@proton.me>
* core: test that history posted before channel signing reaches later joiners as signature missing, and channel moderator delete for all
Confirms the case the owner's new alert describes: a subscriber who joins after the owner turned on "Sign messages" sees the earlier posts as "signature missing" and later ones as signed, while earlier subscribers keep them unmarked. Also covers a non-owner channel moderator deleting a contributor's signed post for everyone.
Run: 001-channel-signing-moderators, slice 1
* ios: keep "Chat with admins" off when saving group preferences
toGroupPreferences left out the support preference, so the saved profile had none and core filled in its default, on: every channel preference save from iOS silently turned on chats with admins, which have no end-to-end encryption in channels. Android and desktop already pass it.
Run: 001-channel-signing-moderators, slice 2
* ui: let channel owners turn on "Sign messages", warning that earlier messages will show signature missing
The channel preference was hidden while signing was recipient-only. Owners now see the switch; turning it on asks for confirmation, because subscribers who join later receive the earlier posts unsigned through history and see them as "signature missing". The "Signature missing" explanation now says the message may predate signing or have been forwarded by a relay without its signature, instead of only implying tampering.
Run: 001-channel-signing-moderators, slice 3
* ui: channel owners can make subscribers moderators, and moderators see the subscriber list
Core already lets a channel owner make a subscriber a moderator; the role picker offered only subscriber and contributor. It now offers moderator too (not admin, by decision). Moderators see the full member list the owner sees, so they can reach the subscribers they may block (subscribers can't post, so there was no other way to reach them), and member info is headed Moderator or Contributor instead of Subscriber for those roles.
Run: 001-channel-signing-moderators, slice 4
* ci: long-press and right-click for app tests, safer ui arguments, desktop Kotlin 4 GB, desktop session limits from claude-scope
Message menus open only on long-press (iOS) or right-click (desktop), so Claude sessions couldn't reach Moderate, Info or Delete. Ported from f/directory-search unchanged, with its hardening: the guards refuse unquoted glob, brace and tilde expansion, and desktop ui checks numbers and sends one key per call so a key argument can't run an xdotool command. The desktop app job's Kotlin compiler gets 4 GB, as f/directory-search needed after merging master. Desktop sessions take max-turns and max-budget-usd from claude-scope like iOS (60 and 3 when unset, as before), and the Claude job may run 120 minutes.
Run: 001-channel-signing-moderators, slice 5
* ci: Claude test plans for channel message signing and channel moderators
This branch's iOS device test plan and desktop prompt replace master's smoke tests: the owner creates a channel on the preset relays, turns on Sign messages through its alert, and two more profiles in the same app join by the copied link; the owner makes one a moderator, who then sees the subscriber list, moderates a contributor's message and blocks the contributor. Signatures are checked as text in message Info. One layout, no test backend.
Run: 001-channel-signing-moderators, slice 6
* fixup! ui: let channel owners turn on "Sign messages", warning that earlier messages will show signature missing
* update plans
* fixup! ui: let channel owners turn on "Sign messages", warning that earlier messages will show signature missing
* fixup! ci: Claude test plans for channel message signing and channel moderators
* fixup! ui: let channel owners turn on "Sign messages", warning that earlier messages will show signature missing
* fixup! ci: Claude test plans for channel message signing and channel moderators
* fixup! ui: let channel owners turn on "Sign messages", warning that earlier messages will show signature missing
* fixup! ci: Claude test plans for channel message signing and channel moderators
---------
Co-authored-by: spacedandy-agents-simplex <342056592+spacedandy-agents-simplex@users.noreply.github.com>
* plan: UI improvements to improve LLM usage via SimpleX
* core, ui: types for chat layout
* core, ui: settings for alternative terminal-like chat layout for managing LLMs or other service bots
* plan: message priority
* fixes
* query plan
* update plans
* remove silent messages plan
* rename migrations
* implement layout
* amend
* fix
* fix
* fix
* improve
* time on the right, sender name in blue
* no avatar in direct chats
* better previews
* update, fixes
* update
* time gap
* changes
* ui: terminal layout line heights, gaps and time placement
* ui: simplify terminal meta layout, correct its docs and tests
* ui: right-to-left emoji edge in terminal rows, time placement tests
* android, desktop: raise Kotlin compiler memory to 4 GB
* ui: terminal captions as follow-up text, classic event separators
* ui: terminal media edge and overlay time, plan decisions
* ui: simplify terminal row separation, correct doc line references
* ui: keep the media time inside terminal rows, restore caption conditions
* ui: terminal heading capitals at large font scales, idle live message time
* ui: rename the classic voice-with-text flag, correct the meta copy docs
* ui: smaller terminal layout diff, sender gap and meta names
* ui: terminal row as tall as the media time
* docs: remove the chat layout section from the bots readme
* docs: shorten the terminal layout section of the chat view
* core: address settings API as on master, /auto_accept reads the stored layout
* ui: smaller terminal headings
* ui: classic sender rows and avatar rule as on master
* ui: classic reply quote text colour as on master
* ios: keep the chat layout setting with other UI settings
* ui: go-to button at the end of terminal rows, no gutter in direct chats
* ui: forwarded arrow on the header line of terminal rows, above the time
* ui: forwarded arrow centred above the time line of terminal rows
---------
Co-authored-by: Evgeny Poberezkin <evgeny@poberezkin.com>
* tests: fix group tests
* fix test
* fix
* fix delivery worker fix
* watch ci
* debug
* fix delivery worker not forwarding to moderators during host acceptance
* add script, update simplexmq
* debug lines
* more debug
* rerun
* debug
* fix, debug
* simplexmq
* simplexmq
* fix
* debug: log member-not-found call sites, restore hang diagnostics, use simplexmq fork
* tests: do not prompt for migration confirmation in strict tables test
* ci: run tests with one capability; simplexmq: end inactive sessions without closing under readers
* ci: run tests on all capabilities
* remote: close the HTTP2 client before its TLS connection
* cabal: use warp that kills timed out connection threads without closing their sockets
* remove diagnostics: member-not-found log, thread dump, CI watchdog; update simplexmq
* badge-service: prevent interleaving of concurrent log lines
* tests: wait for badge group broadcasts before closing members
* tests: log contact connected events received twice
* tests: log member connected events received twice
* core: use simplexmq that logs connections emitting CON twice
* core: keep the team contact above notes in a new user's chat list
* ci: skip macOS and Windows builds while hunting a Linux-only flake
* core: use simplexmq that logs the history of connections emitting CON twice
* tests: remove the logging of connected events received twice
* ci: run macOS and Windows builds again
* core: use simplexmq that runs one thread per agent worker
* core: use the merged simplex-chat/wai warp and the updated simplexmq
* core: use the merged simplexmq
* core: update simplexmq
* core, badge service: comment single writes of terminal segments and log lines
* rfc: invite member of one group to another group
* update
* update
* implement
* version
* update
* do not show error if contact was removed when joining group
---------
Co-authored-by: Evgeny @ SimpleX Chat <259188159+evgeny-simplex@users.noreply.github.com>
* core: group fixes/improvements
* Large messages dropped by relays and hosts (the same 15602 limit was applied, without accounting for forwarding header)
* Members below v18 did not receive forwarded messages or history in p2p groups.
* Join confirmations near the size limit could fail.
* SMP servers are limited to 2 host names each.
* simplify
* remove legacy forwarding and history support
* only restrict p2p groups
---------
Co-authored-by: Evgeny @ SimpleX Chat <259188159+evgeny-simplex@users.noreply.github.com>
* core, ui: remove database backups after key changes
* ui: delete database backups on chat start without delaying encryption marker reset
Keeping encryptionStartedAt set until chat start made DatabaseErrorView show
"The attempt to change database passphrase was not completed" with a Restore
button after every successful passphrase change when the passphrase is not
stored. Restore the marker handling from master and delete backups
unconditionally after chat starts.
* another flag
---------
Co-authored-by: Evgeny @ SimpleX Chat <259188159+evgeny-simplex@users.noreply.github.com>
Co-authored-by: Narasimha-sc <166327228+Narasimha-sc@users.noreply.github.com>
* core: cancel the chat callback on interrupt
* badges: add multi-use codes
* badges: add the managed group
* badges: document multi-use codes and the group
* core: sign test badges with whole-second expiry
* badges: rework tracker and reply texts