This may have been the case if you managed to lose your keys. > (and if memory serves, old messages would be unreadable). Given that a large part of the web now uses LetsEncrypt, if this wasn't so, you would've already had problems on other websites as well. You shouldn't be having to accept anything - a renewed certificate should just work, transparently, without any interruption.
#ROCKET CHAT VS MATTERMOST ANDROID#
On Android I'd have to accept a new certificate to trust, and it allowed me to do so - although possibly this resulted in the requirement to re-login > The certificate issues were more specifically related to Apple devices not liking that an accepted certificate had expired, and a new one had taken its place, and wouldn't even allow for the updated certificate to be "trusted" in place of the expired one. The SQL encoding changed and caused messages to stay “unread.” Took me a day to find/correct the issue, and it’s been smooth sailing ever since. On the backend, I’ve only had one major bump - I went too long between server upgrades (I think I jumped from 5.21 to 5.29). I run the whole thing on a $5/mo VULTR VM, that also also acts as a WireGuard and PiHole server. As far as the family is concerned, the process was painless, and other than the lack of collapsible threads (recently fixed as mentioned in TIFA!) everything has been great.
I explained the reason for the shift, and migrated the whole family over sometime in 2019. Eventually, we hit message limits, and I wasn’t thrilled about Slacks data policies.Īfter a bit of research, I landed on Mattermost. I was able to get everyone to buy in on Slack sometime in 2017… it was great for awhile. Many of us are not on Social Media, and the “group text” became untenable. I have a large family (many siblings, their SOs, some siblings of SOs, some cousins, etc).
0 kommentar(er)
