<unnamed>

Public Key

npub1s8udw9qtw4kmensx8g4zwpm9vcqvujesg29duj5759nm8c6et0rq33vq7m

Profile Code

nprofile1qqsgr7xhzs9h2mduecrr5238qajkvqxwfvcy9zk7f202zeanudv4h3spz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsgvyhh4

Publishing to

relay.damus.io

nos.lol

Last Notes

2024-02-21 09:40:25 UTC

- reply

Lightning \*\*cough\*\* \*\*cough\*\*

2024-02-06 07:50:28 UTC

- reply

It's all abstractions and they unfortunately tend to break if not understood well.
In software, we also call abstractions "dependencies" and they too tend to break often when used in a non-standard way.

2024-02-05 12:32:44 UTC

- reply

💕

2024-02-04 14:24:23 UTC

- reply

I wanna zap your comment!

2024-02-04 06:57:42 UTC

- reply

What does "lump sum recurring amount to pay-per use" mean?

2024-02-03 06:38:43 UTC

- reply

SaaS Twitter goes back and forth on what their favourite pricing model is. 4 years ago, subscriptions were all the rage. Today it's one-time payments. At the end, it's really about what pricing model fits your business best.
\- Subscriptions do add additional friction to user signups. Users worry about this recurring expense. Happy to pay $100 once. $10/month ughhh.
\- One time payments don't have this friction. They don't always fit the business though. My Google Drive 1TB Cloud Storage subscription can't be turned into a one-time payment because Googles server costs are recurring.
The trick here is to calculate your users lifetime value. Example:
Your monthly subscription is $5/month. The average users uses the service for 6 month before they cancel.
LTV = $30. Your costs to serve an additional user is low.
Therefore a one-time payment of ~$50 is a good deal for both parties.

2024-02-02 18:17:56 UTC

- reply

Hehe. I will get back to you if I am going to Kenya!

2024-02-01 19:22:36 UTC

- reply

Hello my friend! We should catch up at some point.