Winner with 4 satisfied sats. Great content!

Not currently. Tentative plan is to make the client code (front-end) open-source and integrate backend with open protocols (e.g nostr, CIDs/@-protocol, etc)

Should be resolved now.

Yes, thank you for the call out. That's a bug that went overlooked on my part.

Been playing around with Polar. Big fan so far. It was very easy to spin up a lightning env and connect a local lnurl server (https://github.com/legalizemath/tor-lnurl-lightningaddress) to one of the nodes.

More WordForm updates: #92280

Ah gotcha.

The reason for the is a user account is not mapped 1-to-1 with a wallet, but rather 1-to-many. This gives a user the ability to sign in from multiple wallets/devices.

That being said, your feedback is very helpful. The UX is probably unintuitive for most since it's a new signin flow.

Appreciate the feedback.

What device are you using that's giving the UX display issues?

Check out WordForm.

It's a WIP but aligns with what you're describing.

Added a couple more channels with inbound liquidity. Let me know if you still see the issue.

The main consideration is protecting the rating system from spam since there is no cost to an author buying their own article. So my initial plan was to require users to be logged in and then eventually have people pay for user accounts.

An alternative would be charging authors a percentage of their income to make this costly. This approach would also allow guest users to access content. The down side of this would be charging big content producers more, which I'd like to ideally avoid

I only have a single channel attached to the node currently. I imagine the fees are too high over that route. I'm going to add connectivity and hopefully that addresses the issue

Added inbound liquidity. Let me know if the issue persists

There service does have inbound liquidity. I think it may be the source wallet can't find a route. I'm going to open another channel and see if that fixes it.

Interesting, I use Brave and haven't seen that issue on the Browse page, but I'll look into it. Thank you

Some initial reasons:

I also plan on adding an optional description/preview of content for this reason

Appreciate the feedback. Do want to give the author the abilty to provide a description or preview, might have to bump that in my priorities.

For the blank page, probably a React issue. What page were you on?