Always scale vertically, not horizontally.
It’s easier for engineers to scale horizontally (e.g., adding all the nips to your client) because they can simply reuse infrastructure across different sectors. It's all very natural and comfortable. However, this means that the value grows linearly and fails to compound (different sectors don't work together). Scaling vertically (e.g., owning the best content production to consumption pipeline for one event kind) allows you to compound the gains your products offer for a single task, annihilating any competition that comes your way.
Vitor Pamplona
_@vitorpamplona.com
npub1gcxz...nj5z
Nostr's Chief Android Officer - Amethyst Social
Trying to clean up our most used event kind, one PR at a time...
Devs, please consider migrating your NIP-05 settings to it's own event kind and deleting it from kind 0.

GitHub
NIP-05: Moves from kind 0 to its own event kind. by vitorpamplona · Pull Request #2213 · nostr-protocol/nips
This PR moves the nip05 property from kind 0 to its own kind 10008 so that we can:
have multiple nip05s.
stop polluting kind 0
filter 10008 events...
Lol, now you can easily fork Amethyst and create your own derivative with OpenClaw.
View quoted note →

Can openclaw fork Amethyst, remove/tweak features and build a different APK for each user?
Amethyst doesn't have shareholders. Best 3 years of my life.


If that is true, it means Google is now doing twice the traffic of ChatGPT, which was doing 80% of the LLM usage until not long ago.
View quoted note →