Content pfp
Content
@
https://warpcast.com/~/channel/daos
0 reply
0 recast
0 reaction

Trigs pfp
Trigs
@trigs.eth
Something that came up in our weekly DAOs call regarding protocol branding and awareness. @yonks brought up something I hear often: "In web2 nobody knows what TCP/IP is, or http" The meaning is simple: Users don't care about protocols. @stellaachenbach had another point that I found very relevant: - part of our job building web3 is building awareness and understanding of *why* web3 So my question is this: Is "abstracting" away the protocols actually the better UX? Or is it a gateway to enabling the centralization of web3?
2 replies
0 recast
5 reactions

Trigs pfp
Trigs
@trigs.eth
My first inclination is to lean more heavily on the "we need to educate" side of things. I do think that abstraction makes sense to a degree. It's a lot to ask ppl to understand what an L1 vs an L2 is, or why one chain matters over another. But I do, however, feel inclined to say that it is essential for users to understand if their identity and data is owned by a centralized entity or is under their sovereignty. This is where the protocol vs platform is my relevant, imo. How can we convince users to prioritize decentralized tools when it's actually more efficient and effective to build a better UX with a centralized solution? I will gladly steel man this position just to see what everyone's pushback is. I want to see where the alternatives are for creating incentive to do the hard thing to migrate away from centralized platforms towards open protocols.
1 reply
0 recast
1 reaction

mOde pfp
mOde
@mode-nearchos
I think we all try to thicken the colors while painting a common canvas... It is never black or white. We always have many more colors included. Like sayin that people in web2 doesn't know about TCP/IP or http, or bacnet, or whatever is not right. It all depends on the perspective and the job the person is doing. Everyone out there using internet on daily basis and caring about their security in there know at least a difference between http and https. Many people out there would say their opinion about TCP/IP even if it is not detailed or very well structured or even right, but many would definitely have their opinion. And likewise we have many misunderstandings about the protocols in our Web2 life. Like I'm working with building automation and talking about differences between bacnet, modbus, lonworks and all that stuff is a daily struggle just like it is in the web3. The very end user, who doesn't care about anything might not tell you anything about these things, but most people would have opinions.
1 reply
0 recast
2 reactions