Nostr Web Client

freecritter 10mo ago

Yes product development will radically change because of Bitcoin + Nostr.

The money isn’t melting so the incentive to scam and grow at all costs fads.

And with portable identity your user is an MVP away from leaving you.

The customer and user are finally the benefactors.

20

dead 10mo ago

okay explain how the incentive to make more money fades

RedTailHawk 10mo ago

Big picture, I'm not you and you're not me so I shouldn't treat you in ways that I would want to be treated and you shouldn't treat me in ways that you want to be treated.

I should treat you how you want to be treated and you should treat me how I want to be treated. That's the real Golden Rule. If we tailor our interactions to each individual in loving ways to meet them where they are, that's how to abide the Golden Rule.

That said, it's great that you think through what notifications you would find helpful.

I would like to propose that it would be even more Golden Rule compliant to "normie test" your stuff. Have normies try to use what you build. Provide any necessary hardware and step by step instructions they would need in order to successfully set up and use what you have developed. Do this with multiple normies.

I don't think devs do this. I would guess that most devs, if they normie test their stuff at all, will only ask their quasi-dev friends who are in no way normies to test their work. I think most devs are out of touch with normie computer abilities and don't care to bridge that gap.

hodlbod 10mo ago

I agree with that. But it's also true that if you have radically different values or cultural background from me, it makes understanding, and therefore effective love, more difficult. It's more effective to serve the people near you before you try to help the people far away. But point taken for sure.

RedTailHawk 10mo ago

Yeah. Jesus never said it was easy to love everyone but that's what we're supposed to do, including those who are the hardest to love, like "evil" people. We can love them for showing us an example of how to be that we can consider emulating and then ultimately reject.

I agree that tailoring to the masses is like herding cats. I think that with enough normie testing, perhaps at least the 80/20 target can get hit where 80% of people can use your creation without struggle during setup or normal use and 20% of people will. At the very least, I think it helps to get over the 50% mark. From a viral standpoint, you want more than half of your attempts to onboard to be successful. Each successful onboard is a new spoke in the hub and spoke model of viral propagation.

hodlbod 10mo ago

I think developers haven't done a lot of usability testing partly because they're not satisfied with their software themselves yet. It doesn't make a lot of sense to get input when there are self-evident issues there. I am getting close to happy with flotilla though, so this is item #3 on my list (after building two things that are 100% required by users first).

RedTailHawk 10mo ago

That's probably a fair assessment of why some devs don't normie test their stuff.

I think perhaps there are deeper reasons at play as well.

The following is a generic dev stereotype narrative for the purpose of illustration of my point:

-Smart introverted kid gets bullied in school and becomes more introverted.

-Not only does this create psychological trauma and baggage that carries forward throughout life into interactions with normies (who may be viewed as substitutes for the kid's tormentors growing up), this often immediately turns into a habit of spending more time with computers than with people simply to avoid dealing with people.

I think a lot of devs are antisocial when it comes to normies, and I think that's often a trauma response to the stereotypical dev childhood I articulated above.

I guarantee this is the case for some devs. Some will admit it. Others would never.

I'm glad to hear that "normie testing" is on your list. I imagine being a dev is a lot like being any other kind of engineer...there's not a lot of thanks or praise that goes along with it. That said, thank you for being the type of dev that normie tests your stuff and tries sincerely to build bridges that the masses can traverse to join the pioneers.That's probably a fair assessment of why some devs don't normie test their stuff.

I think perhaps there are deeper reasons at play as well.

The following is a generic dev stereotype narrative for the purpose of illustration of my point:

-Smart introverted kid gets bullied in school and becomes more introverted.

-Not only does this create psychological trauma and baggage that carries forward throughout life into interactions with normies (who may be viewed as substitutes for the kid's tormentors growing up), this often immediately turns into a habit of spending more time with computers than with people simply to avoid dealing with people.

I think a lot of devs are antisocial when it comes to normies, and I think that's often a trauma response to the stereotypical dev childhood I articulated above.

I guarantee this is the case for some devs. Some will admit it. Others would never.

I'm glad to hear that "normie testing" is on your list. I imagine being a dev is a lot like being any other kind of engineer...there's not a lot of thanks or praise that goes along with it. That said, thank you for being the type of dev that normie tests your stuff and tries sincerely to build bridges that the masses can traverse to join the pioneers.

Dawn 10mo ago

Almost every great product story starts out that way... "I had a problem or I needed a thing or I didn't like a thing" ... or maybe it was for someone very close to the creator. It doesn't matter if it's software or hot sauce. At some point that focus can shift, but if it goes too far it ends up at store brand ketchup & Facebook.

Five 10mo ago

I like your thinking, my sentiment is similar.

I was wondering how much information is by default collected by hosting providers and others though. Information that I and they don't need. I need dedicated users telling me in the face what I should do better.

As if the Beatles or any other great band made music watching peoples' reactions from recordings all day instead of searching for authentic expression and beauty.

Speaking of which how much of the information listed here is strictly necessary to collect regarding flotilla?

https://flotilla.social/privacy

hodlbod 10mo ago

All of it, but with the caveat that I'm a little over-scrupulous, and interpret things pretty liberally to make sure I'm covering my ass. So "cookies" might mean cross-domain trackers; all I mean is that I store your session across page visits. I don't know if that's unnecessary, but I like to be on the safe side.

Tekkadan, ゲロゲロ! 🐸 10mo ago

High hopes. With notifications alone I might just become a Flotilla maxi. Kind 1 who?

SwBratcher 10mo ago

Cool take on this. My time in UX added a piece to that. Bear with my ramble…

“Treat others how they want to be treated”—the Platinum Rule is a compliment to the Golden Rule. It adds empathy to the golden rule’s projection.

This is particularly useful in diverse use cases, diverse user personas, and where user expectations and workflows vary. However, it does have a potential flaw for the dev—what if what someone wants a certain feature that’s not the ideal for their workflow, or the app’s purpose in the eyes of the dev? The Golden Rule, by grounding features and workflows in respect for the app purpose and core user functions, provides a more stable foundation in those cases.

A balanced approach is to treat others with the UI and UX they desire, within the application’s core purpose, and in alignment with your Why as the dev.

Reply to this note

Discussion