Avatar
santos
4d992bd1e12f77866334ce3fdfe20203799bfefb84b7ed5cd111290345157b5a

Sounds intriguing. ๐Ÿ‘€

Gonna check it out! ๐Ÿ––

Love Meditations. Iโ€™ll have to checkout Laws of UX. Sounds very interesting.

Happy birthday #Bitcoin! ๐Ÿฅณ

Thank you for everything youโ€™ve done for me. ๐Ÿ™๐Ÿงก

Whatโ€™s the first book youโ€™re going to read this year?

What are your goals for the new years?

Thatโ€™s a good idea. Learn to Earn for everyone. Maybe a hackathon project for you at BitBlockBoom? ๐Ÿ˜Š

Yeah, I also built my own educational platform emeralize.app :)

Nice! I love that idea too. I would be open to using that.

I am going to create a nostr badge system gearing towards a degree and/or certifications.

We will issue badges to users who complete our lessons and workshops, then if you have the full set, you can be issued a special badged with a tag indicating it is a degree.

I almost imagine an UI like pokemon badges. I think it could be very cool. It would gamify education for local meetups and remote programs.

I want an AI that can watch a series of videos for me and generate a custom quiz each time.

It would help further education significantly and prevent cheating.

Replying to Avatar fiatjaf

I think it's undeniable at this point that the creation of Lightning Address has made the usage of custodial Lightning solutions increase -- or at least be more prominent. We see these stats everywhere of how many of Nostr Lightning Addresses are custodial, and how services like Nodeless and Geyser only work if you give them a Lightning Address, and that probably sounds like a lament to many people who thought Lightning would be this amazing network of self-hosted nodes that everybody runs, and is indeed sad.

Well, on the other hand the Lightning Address flow is clearly an improvement -- to most people -- over the cumbersome invoice flow. Since the early days of Lightning people had been complaining about the fact that there is no way to "just send money to an address". Even though I personally liked the invoice flow much more (especially if they had structured, signatures, clear descriptions and amounts, payment proofs and so on) the fact is that most people didn't and slowly invoices were losing their meaning entirely anyway.

This improvement in the payment flow, along with the open, easy and interoperable way that Lightning Addresses work, has opened space for new use cases that maybe wouldn't have existed otherwise -- like the services mentioned above, and others. So we can't really say this was all a bad thing.

We also shouldn't say it was a bad thing to have Lightning Addresses being invented at all, because if they hadn't been invented like they were, there is a high probably they would have been invented in other forms, probably much worse, that would involve private deals and proprietary integrations with ad-hoc APIs, SDKs and JavaScript widget buttons with iframes. I even remember some of these things starting to happen at the time Lightning Address was created, and we have more evidence of these things even after Lightning Address, like some "partnerships" here and there and the "UMA" protocol. So maybe Lightning Address was just the best possible protocol at the best time, and all its problems are not really its problems, but symptons of the problems of the Lightning Network (or maybe you wouldn't call these "problems", just natural properties, but doesn't matter).

The saddest realization of all this process, for me, was that Lightning payments are mostly used for tipping and not for commerce as I thought they would in the beginning (hence my love for the invoice flow). Specifically, LNURL-pay and its cool hidden features that went mostly unsupported, were all designed with the goal of enabling new use cases for commerce [in the real life](https://github.com/lnurl/awesome-lnurl), outside the web, and Lightning Addresses would have tied nicely into that vision too -- but that was all definitely an irredeemable failure.

I thought I had more things to say about this, but either I didn't or I forgot. The end.

I think it isn't that these flows won't exist but will take more time to cultivate use cases for commerce. I think the general public just haven't caught up yet. Though, this post inspired me to build a LNURL pay e-commerce flow that I designed a while back.

Thanks Grand Uncle Rockstar. I will keep improving the code to make this actually usable rather than a PoC :).

Good feed back. Thanks. Keep in mind this is just a proof of concept. I'm working on turning it into a full MVP. Will take this into consideration with the design.

๐Ÿš€ Exciting news, builders! BitBlockBoom is hosting the ultimate hackathon on starting on April 12, 2024. Lightning X Nostr applications, mind-blowing categories, present Main Stage and a $1,000 prize pool. Designers, developers, marketers โ€“ all welcome! Sign up here: https://forms.gle/mTeAaXLsCan7KtpA6.

Stay tuned for updates! #BitBlockBoomHackathon ๐ŸŒ

Read more โœจ

https://habla.news/a/naddr1qqfxycnz945xzcmtv96xsmmw95erqv35qgsymxft68sj7auxvv6vu07lugpqx7vmlmacfdldtng3z2grg52hkksrqsqqqa28z6zqau

https://void.cat/d/DeuEzTsfxVbeDRtXFBveHp.webp

Esports is close to my heart and has taught me so much. So has Bitcoin. ๐Ÿ–ค

From gaming passion to esports innovation, ZBD intertwines technology and dreams. Embracing Bitcoin's power, the journey fosters global esports inclusivity, turning challenges into opportunities.

Itโ€™s truly awesome to work with such an amazing team to bring this innovation to market and marry the two. ๐Ÿ––

Learn more about my esports journey and what I think Lightning can do for esports ๐Ÿ˜ .

Read more! โฌ‡๏ธ

https://blog.zbd.gg/the-future-of-esports/

Minimal talk, maximum ship.