Steve
@stevedylandev.eth
The conversation around this has been really interesting. IMO the answer isn’t as simple as “make the front end decentralized.” I think that’s part of it, but there’s so many layers between when code is committed to when it’s interacted with by a user. In web2 there were cases of domains being deceptive and just visiting a site wasn’t secure, so HTTP and SSL was implemented to verify the authenticity of a domain name with the IP associated. We’re now getting to a point where we need a verification mechanism that becomes part of the every day web. Users today experience the benefits of HTTPS without evening knowing what it is; we need the same for blockchain apps
2 replies
2 recasts
9 reactions
Frank
@deboboy
As someone who's tested my LLM stack experiments it was cool not to see you freak out because HTTPS wasn't built into the deployments. Which is making me re-think it's value [other testers have noted it's not a priority]. But, to your point I do want a verification mechanism when you're launching another browser tab.
1 reply
0 recast
1 reaction
ℭ𝔦𝔭𝔥𝔢𝔯
@cipher
why are you testing a non https in a live environment??? test locally, get a cert, or just use a serverless instance. Especially if doing LLM experiments, you should be aware how rapidly sites are now spidered and crawled
1 reply
0 recast
1 reaction
Frank
@deboboy
Exactly!
0 reply
0 recast
1 reaction
