Highly recommend reading Designing Data-Intensive Apps [1] and Monolith to Microservices [2]. I can't remember which (maybe both?) but I definitely took away the idea that if services share a DB, that DB's schema is now a public interface and becomes much more difficult to evolve with new requirements.
Yes, OTel has autoinstrumentation libraries for some language that can pick up a fair amount by default. Though it's unlikely that that would ever be sufficient, it's a nice start.
Seems like the key shared characteristic of these examples are small communities where people care about each other. As you say, it works at smaller scales. But free rider problems are a lot tougher in a community of millions or more.
I was surprised to see no mention of automation tools like IFTTT and Tasker. These sorts of overarching automation oriented tools let people solve a lot of problems by stitching together things that aren't designed to work together.
I would actually put Excel in this original category. Part of Excel's utility is that it is really good at enabling building of dashboards, applications, whatever. While Excel's builders didn't have D&D character sheets in mind, they definitely expect users to do unanticipated things with the software, just as much as IFTTT or Tasker would.
In some ways this is a "platform" type of perspective. "Here's a bunch of building blocks, go do whatever you think you need" is really powerful once the network effect of building blocks gets big enough. Any tool with a built-in DSL or workflow builder type of UI is probably in this category.
Not all companies (stocks) have the same sensitivity to inflation. Depends on all sorts of things that are business specific. One example is how easily price increases from suppliers can be passed on to customers. A company that sells a commodity into a very liquid market won't suffer as much.
My tip on life insurance: don't buy it from your existing auto/home insurance company. In my recent experience it's far cheaper from a dedicated life insurance company. I also got a discount going through Costco.
They rewrote it from a native app to a web app, and it got a lot slower. Limits on the size / number of videos active. Status was not as flexible as we wanted (i.e. reminders when you forget to update, time zone conversion, etc).
We used to use Sococo and got frustrated and abandoned it a couple years back, actually.
If you hit the Slack button it opens a link to that Slack chat. If you are in a room with a group it'll open a group DM to the other people present. (I personally rarely use the Slack button because any given DM or channel in Slack is only ever alt+tab and ctrl+k away, but that's just me.)
I'm happy to see more virtual offices being built!
My company internally built and then open-sourced Qube[1], which has a lot of similarities, but just integrates with Slack and Zoom. A lot less ambitious, I'd say, but we're very happy with it.
Telegram has great features. It's fast, available on every platform, and the clients are open source. I've had good uptake on it among friends and family, especially with the option of easy web and desktop clients.
As others have said it's not as theoretically secure as WhatsApp or (especially) Signal. But I think it benefits from being the main product of a company that is totally focused on messaging, not on advertising (see all of Facebook and Google's messengers). The experience is great and even as they add features, they manage to keep things clean and stay out of your way, so you can ignore all the new features and just use it for simple stuff that it does really well.
That said, I haven't used WhatsApp much because I don't know many people who do. It comes down to where the people you want to talk to are, and if you can influence them to go elsewhere.
If I had to guess, I'd say that Apple and Google have the leadership and financial cushion to be more forward looking than all the PC manufacturers, who are in most competitive markets with lower margins.
That doesn't mean it's OK, but that's my guess as to why you see the lag in quality.
[1] https://www.amazon.com/Designing-Data-Intensive-Applications... [2] https://www.amazon.com/Monolith-Microservices-Evolutionary-P...