Fauzruk

One could argue that you don't become a trillion dollar company by leaving money on the table.

The way I see it is, we don't always want anonymity. Sometimes privacy is enough and this is where Signal shine.

Because being tight is considered a beauty standard for women, not so much for men. For men this is mostly upper body muscle (shoulder, arms). A vest top would he an equivalent, and you don't see skinny guys wearing that either.

I don't think any of the algorithm is expose to other instances so that wouldn't impact the communication between instances. At the end of the day this is open source so admins can freely build a forked version of Lemmy with a slightly different algorithm.

These days the standard is to create an API Doc out of a OpenAPI document generated from the code itself. Someone will probably contribute to it at some point.

For me it is Fedora as well. Before that I was using EndeavourOS but wanted to use something a bit more stable. Haven't distrohoped since!

There might be things Meta isn't allowed to do with WhatsApp. Also the concept of account is bit blurry on WhatsApp because you basically login with your phone number and an SMS code sent to your device. This wouldn't work as well for a service that can be used elsewhere.

Well, in the case of Bitwarden the client is open source so it can actually be reviewed whether or not it is actually encrypted. No need to trust anyone.

In my opinion, Signal isn't trying to be a Matrix alternative. Anonymity between users isn't their objective, they mostly want to be a none profit alternative to WhatsApp, Messenger, etc... with strong E2E encryption. Phone numbers is ultimately the best way to discover new users as soon as you install the app.

I'm fine about ads on Signal. It is a none profit. 😉

To me this sounds like a code / DB problem more so than a monolith vs microservice issue. You can totally run only the worker part of a monolith inside AWS ECS and have it autoscale, this is not specific to microservices.

Exactly, and nothing prevent a monolith from doing vertical slicing at the database level as long as the monolith is not crossing its boundaries. This is the only scaling part that is inherent to microservices. If the issue is the horizontal scaling, microservices doesn't solve anything in this case.

Also specifically on what I understand of the Fediverse, you want something easy to host and monitor since a lot of people will roll out their own instances which are known issues when running microservices.