Nick Nisi
๐ค SpeakerAppearances Over Time
Podcast Appearances
Did he give you that? Did he give you that file too?
So today for the first time in a very, very, very, very long time, I opened up ARK just because, just because I was like, well, I got to talk about a browser that isn't Safari. And so I've been in meetings recently. I've like screen share with folks and they're sharing their stuff with me and they're navigating around and give me demos and stuff like that. Sure.
So today for the first time in a very, very, very, very long time, I opened up ARK just because, just because I was like, well, I got to talk about a browser that isn't Safari. And so I've been in meetings recently. I've like screen share with folks and they're sharing their stuff with me and they're navigating around and give me demos and stuff like that. Sure.
And at least a couple of occasions, I was like, what's that browser? And it was ARK. It's kind of cool. That's it. That's it. I still can't use it though. Why not? It's such a departure from standard web browser that I don't know how to use it. I got to retrain my brain how to use a browser.
And at least a couple of occasions, I was like, what's that browser? And it was ARK. It's kind of cool. That's it. That's it. I still can't use it though. Why not? It's such a departure from standard web browser that I don't know how to use it. I got to retrain my brain how to use a browser.
That's about it. I mean, that's the reason. It's just like VIM. It's enough change.
That's about it. I mean, that's the reason. It's just like VIM. It's enough change.
I mean, like for somebody who hasn't VIMed.
I mean, like for somebody who hasn't VIMed.
But for someone who hasn't and they're intimidated or they have imposter syndrome. I can understand why it's challenging to get over that hump to even be comfortable in Vim. And so I would say that Arc or a browser that is uniquely different like it is has similar characteristics of the challenge that Vim has to capture users. And when you're over that hump, maybe you're like, I'm sweet.
But for someone who hasn't and they're intimidated or they have imposter syndrome. I can understand why it's challenging to get over that hump to even be comfortable in Vim. And so I would say that Arc or a browser that is uniquely different like it is has similar characteristics of the challenge that Vim has to capture users. And when you're over that hump, maybe you're like, I'm sweet.
It's great. I get it. But for me, it's like, well, I just can't get past this departure. It's hard.
It's great. I get it. But for me, it's like, well, I just can't get past this departure. It's hard.
Who's they? The people?
Who's they? The people?
Same. I do want to clarify, just because we put this security mention out there, I pulled up the CVE, the CTO, Hirsch, I believe, of the browser company, the makers of the Arc browser. On August 25th, there was an incident and a fix was out the very next day. The loop to be closed is not the details of it, but that they say no ARC members were affected by this vulnerability.
Same. I do want to clarify, just because we put this security mention out there, I pulled up the CVE, the CTO, Hirsch, I believe, of the browser company, the makers of the Arc browser. On August 25th, there was an incident and a fix was out the very next day. The loop to be closed is not the details of it, but that they say no ARC members were affected by this vulnerability.
They did an analysis of their Firebase access log. So they use Firebase to deploy certain and use certain features inside of the ARC browser. And so they trolled their, I guess they combed. Trolled is probably a bad word. But they combed their Firebase access logs and confirmed that no creator IDs had been changed outside those changed by the security researcher.
They did an analysis of their Firebase access log. So they use Firebase to deploy certain and use certain features inside of the ARC browser. And so they trolled their, I guess they combed. Trolled is probably a bad word. But they combed their Firebase access logs and confirmed that no creator IDs had been changed outside those changed by the security researcher.
So TLDR, at least on the breach, is there was no vulnerability. There was a vulnerability, but no one was affected by it.