frustrated enough with nostr clients that i want to create my own

when android?

#nsfw #sundaybumday #nudestr

GOOD MORNING 💜

36 years around the sun and we still here. 👏🏻🚀🥳🎈

I’m really bullish on the next six months of Nostr development.

I don’t know if it’ll generate user growth in that time period, but I’m more confident that it’ll improve UX and applications, and thus bring in more capital for the next stage, which can then be used for more user acquisition.

coming to an NDK near you

🫨 nostr:note14kv240qs62g5djzgzuru8ssuj00a43reef240qhgvp3jkun2eu5smc9073

Some people think Nostr cannot work with things like a "universal consistent like count" and other basic social media malignant tumors.

Even if we ignore the bad psychological and societal effects of such practices and assume they are good, and even if we assume that Nostr is all running in a single server that has all the events (a Bluesky-like unavoidable requirement for such universal consistency) these people are still completely oblivious to the fact that anyone can create a bazillion keypairs and spam like counts.

So when they ask for a "universal consistent like count" what these people are really asking for is for a centralized KYC barrier at the doors of Nostr that ensures only a single keypair can be created by each human.

A few facts about Primal:

- We have 4 devs: 1 iOS, 1 android, 1 web, 1 backend

- We open source everything we build under the MIT license

- We’ve raised a small seed round from mission-aligned investors

- We optimize our UX for onboarding new users to nostr and bitcoin

- We’ve always been friendly and supportive of other nostr projects

- We will continue building and shipping; that’s a promise

Our goal is to build a profitable business that serves nostr users and no-one else. We expect that to be a long process, spanning many years. We are here and ready to grind.

Anyhow, GM. ☀️

this is what happens in the future if the "outbox-is-broken-let's-use-smart-proxy-relays" people win:

- people start relying on "caching services" to fetch their notes. now every client must run their own caching service to remain competitive.

- as the network grows, syncing from all relays becomes more and more prohibitively and databases grow to the infinite.

- less and less caching services exist, but a "local best scenario" would be if we had like 4 different clients/caching-services to read from, but then if one of them banned alex jones that would mean 25% of users lose access to alex jones. there is nothing alex jones can do to change that.

- users could switch from app A to app B that hasn't banned alex jones, but app B had already banned donald trump, so that move is questionable and uncertain. anyway, it's too much friction for a user who doesn't know how to find this caching-service setting buried deep in their settings (because UX specialists said that's the best place to put it).

- eventually it makes no sense to switch anymore and as one of the caching services gains more market share they merge with the others, saving costs and regulatory burden (these caching servers are so big they need to do spam moderation, find and delete pornography and scam bots, comply with government takedowns, defend themselves against lawsuits, it's a huge cost), so it's much better to just have a single caching-service.

- everybody still publishes to their own relay, so nostr becomes exactly like bluesky and the central service can censor anyone. eventually people give up the stupidity of using intermediary relays and just publish directly to that central service.

- that central service now can serve you ads and blue checks, shadowban everybody who doesn't pay, modify your feed with amazing AI techniques to keep you engaged and prevent you from seeing anything they don't want you to see but keep you nourished with memes.