It depends on the phone’s brand. Samsung’s keyboard is way different from Motorola, for example. The other reasons would be the possibility of customization, and for privacy-minded people, as the keyboard is basically a very sensitive entry point
I believe the biggest issues of self-hosting email is the sending part, not receiving. I usually don’t have to send any emails through my aliases, I just use them so I can easily block if they start spamming, or know where a breach happened by the email, as well as to hide my main email. I know there are other use cases though, so its fair to share concerns
I’ve been working on pt-BR translations for the project, really excited about its progress and future!
I highly recommend you change vendors, if possible. Not only will you not have to deal with this kind of issue anymore, you could also find vendors with dedicated support channels, status pages, and documentation detailing breaking changes (which, in an API, should only happen through versioning)
I do agree that, to a certain point, this shouldn’t be possible in this volume, but also, when you add a phone number as a contact, it would show up on WhatsApp as long as the profile has public data. Anyone that saves every possible phone number would have the same result (although this could take ages, thus the issue with the scraping)
Well, it’s not easy, but I like the idea, hadn’t thought of that… I don’t really use the triggers, only when files change, so that’ll do it!
I’ve done the same. Not trusting something until it can be trusted. Unfortunately it seems there’s no easy alternative apps, so not sure how I’ll handle my usage now
I’ve been using delta for a while, alongside lazygit, and enjoying it.
As I don’t have any critical script, I will try it out locally, perhaps I can open some PRs with fixes of what I see 😄 loved the idea!