I come with a goal of changing what UI looks like and what UX feels like in crypto.
I'm not sure about when it's going to happen or how I'm going to get these jobs but for sure I'm going to do it. One team, one protocol, one app at a time.
Already provided detailed feedback and suggestions to @TotoTurtlesNFT for their Tuffy AI webapp and although team hasn't gone live publicly yet, I hope they do so eventually and I'll keep providing advice till they launch.
I've always said it and will always say it, crypto has a very huge UI/UX problem but no one is really talking about it surprisingly.
Coming as a Web2 dev into Web 3, the deficiency was and remains very glaring and in my opinion it remains one of the biggest issue in onboarding normies.
As the World Cup starts tomorrow, I just wanna take a moment and thank God for allowing me to make it thru 4 more years and being able to watch another World Cup. 🇲🇽🙏🏻
@miracle_quist@sopuruchn I can think of at least 2 more reasons for a possible failure of the desk aside electricity.
I do agree with your point regarding electricity though
My dream gf:
- female
- alive
- her dad is a partner at a Tier 1 VC firm
- dad can lead my Series C
- dad is on Forbes Midas List
- dad has a centibillion network
- dad has taken companies public before
- has nice eyes
@Ayor_Star@fkay__fk@Adikastakes You do have a point and it's too early to judge
Personally don't think they'll go deep though with what I've seen so far. I might be wrong.
I pushed Centinel V1.1.0 to NPM a while back but forgot to update y'all.
The new version supports the proxy file framework Next.js 16+ uses, Centinel now also natively supports webhooks and callbacks so you can log payments in your own DB.
The docs https://t.co/2igpfMXj4K
Why block agents or bots from accessing any resource on your site when you can just charge them for it?
I just released Centinel- A low code framework that lets devs charge agents or bots micropayment in crypto to access protected API routes.
GitHub below