I totally understand the issues with having a toolset offering, but at the same time, there's no way someone that is not as concerned to privacy, or a business that uses basic office tools, to consider Proton as an alternative to Google or Microsoft. They don't have only an email and calendar, they have a full work tooling suite, which is very important to a lot of people. I believe we should work for more companies to develop their own apps and systems, even a full ecosystem. Otherwise, we might land on the same problem streamings are right now: there are so many of them, that it's again easier (not only in terms of money) to download movies and tv shows. If you have 10-20 apps you need to pay or to keep updated, add new users through a management system, you will probably not choose those tools and move to one that includes everything. I personally am sticking to Proton for mail, calendar drive, and VPN, but I'm going with OnlyOffice for office tools, and considering between keeping 1Password or moving to Bitwarden, since the cost of 1Password is high - it is totally worth it, just not currently my plan to keep that expense
I also like OnlyOffice as an alternative to MSOffice/Google Office Suite, has free tiers and real-time sessions
I love Technical Connections!!
I have an opinion that, as everything else in software, depends:
If there are tens of teams working on the same repo, it's chaotic. Separating into smaller ones makes it easier to deploy, specially when there are db migrations involved.
If there are fewer teams, there's two approaches: monolith monorepo, or monorepo with separate projects, but with single deployment pipelines. I prefer the latter, as testing changes and deployment isn't as chaotic. I also prefer when each subproject has it's own DB, so the migrations can be separated. There's nothing I hate more than dealing with migration conflicts
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!
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!
Who would have thought that shoving privacy nightmare AI "tools" into the most used OS would have negative reactions huh
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.