Quick Update About Homebase Last week, Google Chrome and Let’s Encrypt changed some rules about special security certificates. This affects a small part of how Homebase handles secure connections between identities (our peer-to-peer system). We’ve got this covered. We’re rolling out a new and better way to handle secure peer connections next week. It will be simpler for everyone and actually more secure than before. What this means for you: - Most people will notice absolutely nothing — everything will keep working smoothly. - Only a few people whose certificates were recently updated might temporarily be unable to send messages (for example, chat messages). No action is needed from you. We will fix this automatically when the update rolls out next week, and everything will be back to normal. --- Technical background (for those who want the details): Public certificate authorities like Let’s Encrypt are no longer allowed to issue certain certificates for client authentication (due to changes enforced by Chrome). This impacts Homebase’s peer protocol — the way two identities securely talk to each other. In the current setup, the caller uses a client certificate to prove ownership of its domain. We’re replacing this with a fully self-sovereign nonce-based challenge-response approach. No more public-CA certificates needed for client auth. It’s cleaner, removes the dependency entirely, and is more secure (especially against stolen keys, since proofs can’t be used offline). Thanks for being part of the journey! — The Homebase Team

02/19/2026 14:04:53