It's much more tricky than that.
We can at least divide the problem into 2 layers,
The 1st layer is social behavior:
You can't assume every follower uses the same client.
Some client doesn't have notification at all.
Some only has a small UI hint, but no global OS level notification.
Some only notifies if you open the app, not in the background.
And some users never check DMs or use a client that doesn't have a DM, such as Rabbit.
The key need for nostr:nprofile1qqs9fvk57tm98y3lgzpcn44y62d29tt7zpz5nn3ag54ahe9xwxnqzcqayqv2q is not to massive DM followers, but to notify followers through any means.
DM is just one way.
The 2nd layer is the technical layer:
The
current follower/following NIP is flawed, not stable and consistent.
Therefore, using it as a base can only create an unstable feature. It's
probably acceptable to have it work 90% of the time for the first few
weeks. But unbearable for long term.
Therefore,
as much as I would love to have more users to use DMs and Blowater in
particular. We have to assume that most users just never see DMs and
start there.
It's easy for me to implement a massive DM feature in Blowater, but this DM may never be seen by nostr:nprofile1qqs9fvk57tm98y3lgzpcn44y62d29tt7zpz5nn3ag54ahe9xwxnqzcqayqv2q 's followers because most of her followers don't use Blowater and most other clients' DM are just bad.
But I'm happy to accept this challenge anyway because it aligns with my long term product vision anyway. Now it's just more prioritized.
