pull down to refresh
0 sats \ 0 replies \ @fewsats OP 18 Oct \ parent \ on: A machine-friendly economy bitcoin
Did you https://www.firecrawl.dev?
Our example was simpler because it was not crawling but scraping a specific page.
Yes, e-cash presents a solid solution with its own set of trade-offs (centralized/federated), but eliminating liquidity management could be worthwhile in certain cases.
That said, try not to get too attached to any specific technology—it will all take place behind the scenes. What really matters is what “internet-native money” unlocks.
You write the best Trip reports. Best way to stay in touch with the Cities/Conferences we are not able to attend!
Nice! Thank you for sharing @031f2ed60b
Yes, Lightning Labs is where the L402 protocol was invented and implemented. It has been in production for years (Loop and Pool use it for the "accounts")
There is a bLIP for it (https://github.com/lightning/blips/pull/26) but it is pretty much an open source protocol. Many things need to still be added/are being explored right now, like what we did here with the custom URI.
The payment flow for embedding videos is the same as on https://videos.l402.org
The app detects the L402:// URI, fetches the service details, checks for valid credentials, and either plays the video or prompts for payment. After payment, the credentials are used to access the video.
You can check the blockbuster (server) and blockbuster-video-demo repos for more details. If anything is unclear, feel free to open an issue and we will fix it ASAP!
Yes, the L402 is a protocol that integrate payments in HTTP flows.
The payment itself is done using the LN :)
Yes, we do love lightning.video In fact, we are sitting next to Justin right now!
The idea of blockbuster is to host not only video but many other kinds of content (from articles to audio).
On top of that the interesting thing here is the extension of the L402 protocol, using a specific URI to encode metadata about the service that is being paywalled. This will allow NOSTR clients (or any other kind of application) decide what to show to the user or what kind of content and be consumed in that specific app.
If lightning.video already filled your needs, stick to it.
Only one thing matters: make it work.
The key to success is leveraging your unique advantages. For some, it’s their network, for others, it’s experience in the field, and for others, it’s having personal funds. There’s no universal ‘better way’—just focus on what you bring to the table and what your target market needs.
The biggest threat to your company’s success is losing sight of that core goal: making it work. Often, it’s ego that gets in the way—whether it’s wanting to change something for the sake of it or believing your approach should be different from the market’s reality.
The only advice that generalizes well? Fish where there’s fish. Focus on what works, not what you wish worked.
I think it's a meme more than it's actually useful
No no, we are serious! Check out https://L402.org
is a re-arch of that worthwhile just to use these macaroons
The answer is NO and that's why we are not seeing it happen.
Not to mention the clients
BIG chicken and egg problem. The only way around seems to be to actually focus on a niche and let people know "this is our official client but you can build your own". Data applications (a Bloomberg like terminal that can add third party sources with a standard protocol for data, visualizations and payments) may be the killer app to start growing the ecosystem... but it still remains be seen.
Go unlock a video at Lightning.Video and tell me how http and macaroons would make that better for anyone?
You are a bit off here though. You are thinking "people who want to consume my videos can go to my platform and watch them". If you paywall them using the L402 standard, people in MY PAGE (or any other) can watch your videos while you get paid.
The L402 payment protocol has been in production use for several years at Lightning Labs.
At Fewsats, we've explored various applications of L402 like wrapping storage/compute as a service. We've found that one of the most promising areas for L402 is in providing Data APIs though.
I think the protocol shows particular promise for AI applications, especially in agent environments but it's worth noting that we're still in the early stages of exploring these use cases.
Long story short, I would say that while L402 is production-ready, there hasn't yet been a "killer app" built on it.
@031ef7d322 you nailed it!
That's exactly why we built this service. We're still figuring out what the "ultimate L402" experience looks like, but we're certain it involves making integration dead simple for both consumers and providers. And yeah, opening up access to as many people as possible to build and use it is a big part of our vision.
As for @Rsync25, hey, he beat us to posting about our own product on Stacker News! That's pretty cool, and in our book, he has totally earned those sats. :)
Hey there, it appears that someone beat us at posting our latest product release.
We created HUB because we saw a need for a simpler way to handle L402 credentials. For hardcore users (privacy + flexibility), we think Pillbox is a better option but we understand that not everyone wants to dive that deep into credential management.
We're aiming for that "stripe-like" simplicity for L402 clients. The goal is to make it easier for folks to integrate L402-protected services without getting bogged down in the technical details of Lightning payments and preimages.
Right now, it only works on "*.fewsats.com" endpoints (we are not a wallet!), but we're excited about the possibility of opening this up to third-party providers.
We're still a small team, and we're genuinely stoked about pushing the boundaries of what's possible with L402. If anyone has questions or wants to chat more about HUB or Pillbox, feel free to reach out.
We're always happy to geek out about this stuff!
Pretty cool!
I just checked the APIs that @cascdr exposes and most of them seem like a good match for the L402 protocol.
Happy to help in case you want to integrate it to paywall your APIs!