It's up to you, if you want to manage her page, you can write it from scratch or use something like https://jekyllrb.com/ as a static site generator. it gives you a bit more freedom, but at the cost of complexity

if you want to minimize your involvement and let her manage it, use one of the providers. they are very noob friendly, and after the initial setup it's very easy to change or add content, which is probably the only thing she will care about

Logseq is a great opensource tool for that

It's hosted on legend.lnbits , which is a testing service.

Yes 100% . We'll be working on it

appreciate your insights too!

One thing worth mentioning, the complexity of a stateless system is just so much lower than a stateful one, that it makes sense from an engineering perspective to consider if state is really necessary or if it's just an excuse to track users :P

But of course, sometimes you definitely need state/accounts/users , in which case PROXNUT may not help much

I think you could definitely hack something like that, but IMO as soon as you strart to introduce statefulness, other protocols start to make more sense.

Therfore, In the above example, i like number 3 the most, it leverages another protocol that is great for managing state

Ecash is kinda inherently stateless, because links get broken after every token creation. So you would have to manually upkeep that state somehow, which kinda defeats the purpose.

But I think that's OK, because there are other things (like L402, JWT, etc..) that handle state well!

wow, i said state so many times.... We need to separate the web from the state

Yes! I think Very similar to LL's L402 but some nuanced differences.

Check this answer on the AMA post for more details: #268791

oops, @supratic i think the pics/order are out of whack starting after the 'deterministic' chapter

welcome :D

correct, that should be seen as a disadvantage. If PROXNUT gets to a point where it is deployed into production environments and performance and speed are crucial, the mint should either run alongside proxnut, so verification time is negligible, or if we need to squeeze out even more performance, PROXNUT itself should become a mint.

thanks for the great question!

I haven't had the time yet to dive into the details of L402 but as far as i know the main difference is that L402 is stateful.

Meaning that you pay an invoice and you receive back a macroon that grants you access for the next n requests. The server has to keep track of the state, to ensure you don't overdraft.

I think one big advantage of this is that macroons can be used for granular authorization which gives more control if you need to be able to lock specifc things down.

PROXNUT is stateless, which means every request is completely isolated from all other requests. You need to provide valid ecash on every interaction, and there is no linkability (other than network level) between the requests.

The advantage for users is that they benefit from having the 'the data monopoly' on their side (no state keeping on server), and at the same time the provider benefits from a simpler setup.

Another advantage is, ecash is centralized and backed by 'anything', so it is easy to have a system where tokens are representing something other than cash.

Ecash has a very low overhead (even compared to lightning, where you have to rely on the network liquidity and things like that) which makes a lot of sense for high frequency payments.

I hope someone that understands L402 can correct me if i'm wrong, or give their POV on the differences!

That is correct, ecash only makes sense if there is no need for identity.

IMO, this is a whole new (old) way of doing things. It is shifting the data balance back to the users. I think of this as a solution for companies and customers that want to opt out of the data collection business model and just go back to the "I sell this, you pay for this" model.

I think this can be used in any industry, it just depends on what the providers and consumers value.

Me personally, i dislike everything that requires a signup/email just for the purpose of advertising/selling me more stuff, and i would hope other customers feel the same way and force the market in that way.

But maybe it's just me, in which case this will remain niche

yes!

What's even better: the history would be stored on users device (there is no account, so storing on server makes no sense) which gives the user data ownership.

But yeah, a transaction history is definitely possible, and is going to be part of the proxnut-wallet webcompoment in the future 100%!

From direct payments/payment for content.

It's like a subscription, but instead of paying monthly, you "top-up" ecash and pay for each interaction separately.

It gives users the option to cash out back to Lightning if they don't need the tokens anymore

There is a few differences between the account/balance model, and the ecash model. I think there are both advantages and disadvantages:

disadvantages:

advantages:

I don't think one is strictly better than the other, but each of them is definitely better than the other at certain things!

If you need identity, account model if you don't, ecash!

the subscription model is out of fashion. 2weeks ™

a demo is at https://demo.proxnut.com

to implement it on your own infrastructure, peek at:

If they put the nuts on the line, they can use it 🥜🥜🥜