They get paid for functional requirements, but it's actually the nonfunctional requirements that make a product enjoyable to use, in the mid-term.

I complained to some Nostr client devs and always got some variant of "Buy a better phone and get better Internet." Or they're like, "You are speaking from a scarcity mindset."

But I'm my own client dev, now, and I started coding in the 1990s, and I'm rage-coding and have an AI, and I'm testing on an old cell phone and an old netbook with 2 cores, so look out, below! 😂

Let's bring Nostr to the Great Unwashed Masses, including people commuting with the Deutsche Bahn.

Reply to this note

Please Login to reply.

Discussion

"Works on my expensive, perfectly configured dev machine" has been a growing mentality.

Which is why I tend to favor software that's as independent as possible. For example, Tuta building their own notifications so people who use a fully FOSS stack don't just get fucked for not having Google spy services installed. It's the understanding that certain design choices will open the product up to as many people as possible, which should be the goal in most situations. I think it's goofy how much "open and decentralized" tech requires Google services to function properly or some other centralized stack.

you can't give nostr to deutche bahn customers, there's no wifi 🤪