FluffyChat
FluffyChat 2.8.0 is an open-source Matrix messenger with rooms, spaces, end-to-end encryption, file sharing and multi-device sessions. This page focuses on device verification, recovery keys, notifications and self-hosted service boundaries.
Rooms, spaces and service boundaries
FluffyChat uses rooms for conversations and spaces for grouping projects or topics. Invitations, member permissions, media retention, search and synchronization are controlled partly by the selected Matrix homeserver. Test a new account and room before moving important conversations into a production space.
Encryption and device recovery
Encrypted rooms depend on device keys, verification and a recovery process. A new device should be verified before an old device is removed, and recovery material should be stored separately from the phone or desktop. Losing every verified device and recovery source can make earlier encrypted messages unreadable.
Notifications, media and self-hosting
Android, iOS, Linux and web sessions differ in background execution, notification permissions and local caching. A self-hosted homeserver also requires independent maintenance of certificates, databases, media storage, backups and push settings. Review these boundaries instead of treating the client as a guarantee from the server.
Review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave FluffyChat to this cloud drive
Baidu Netdisk
Save FluffyChat to this cloud drive
FluffyChat 2.8.0 installation, encryption and multi-device guide
Connect a test account to a Matrix homeserver, complete device verification and recovery, then test rooms, files, notifications and offline behavior before using a production account.
Before you start
- Choose the Android, iOS, Linux or web build that matches the device, and prepare a test account plus a written recovery-material checklist.
- Confirm the homeserver registration policy, room invitations, media limits and push strategy; client features do not override server policy.
- Prepare two devices and one test room so login, messages, files, encryption and sign-out can be checked without risking important data.
Installation steps
- 01
Install the matching platform build
Install the package for the target platform, then enter the homeserver used by the account and verify that the sign-in identity matches the intended organization.
- 02
Verify the device and recovery path
Use an already verified device or recovery key to verify the new session, check the device name and encryption status, and keep the old device until history is confirmed.
- 03
Test messages, files and notifications
Send text, an image and a file in the test room, then compare foreground alerts, background push, media download and local-cache behavior.
Quick start
- 01
Organize conversations with spaces
Create spaces for projects, place rooms under the appropriate topic and set notification or mute rules so urgent collaboration is separate from low-priority discussion.
- 02
Confirm history on a second device
Sign in on the second device, complete verification and check messages, attachments and read state before cleaning up an old session or changing recovery settings.
- 03
Review push and privacy settings
Record device push, media and third-party service settings, then disable unneeded notifications or choose a self-managed service when the deployment requires tighter control.
Usage tips
- The Matrix client, homeserver and push service have different data boundaries; end-to-end encryption does not remove every form of server metadata.
- Keep recovery keys and device-verification records separate, and retain an independent copy of important attachments.
- Notification, background and file-permission behavior differs across Android, iOS, Linux and web sessions, so recheck each platform after upgrades.
Troubleshooting and uninstall
Why are older encrypted messages missing on a new device?
Check device verification, recovery-key status, the availability of the old verified device and the room encryption state. Keep the original session and local data until recovery has been confirmed.
Why are notifications not arriving?
Check operating-system notification permission, background restrictions, homeserver push settings and network reachability, then retest in the test room instead of relying only on the online indicator.
- Complete the device migrationConfirm login, room history, recovery material and important attachments on a replacement device, and record the active homeserver and device list.
- Sign out and remove local dataSign out, uninstall FluffyChat through the platform application manager and clear local cache only after recovery material and server-side copies are known to be available.
Frequently asked questions
Can FluffyChat connect to any Matrix homeserver?
It requires a homeserver with compatible Matrix login and synchronization support. Push, media, identity verification and custom registration rules still depend on that server, so test an account before migration.
What happens if the recovery key is lost?
Encrypted history relies on device keys and recovery. Complete verification on a new device and preserve recovery material before signing out of every verified session; otherwise earlier messages may remain unreadable.
Does FluffyChat push data through one fixed service?
Push behavior depends on the platform, client configuration and homeserver policy. Review the configured push path and network requests when privacy or self-hosting requirements matter.