Hacker News .hnnew | past | comments | ask | show | jobs | submit | GregMartinez's commentslogin

Thanks for sharing an in-depth breakdown of your first year. I've been curious on how indie shows can support themselves and it seems like it's really not feasible long term which is very disappointing. After paying for music, talent, hosting, and the payment platform's cut it seems like you'd need a huge listener base to get a small percentage of users that donate.

Patreon donations being higher than the others has to be due to user familiarity. It seems that most indie creators that ask for donations use Patreon so listeners might be more comfortable using that versus something like Liberapay or Interac.


I tried Patreon simply off name recognition as you say. With that said, I did try to switch over to Liberapay after reading this, but they don't support automatic payments via Paypal (only Stripe, which the receiver has to support), so unfortunately a bit of a non starter for a set-and-forget supporter mechanism.


I'm not disappointed because I still think the show will be feasible long term - just longer term than it's been so far! :D


Just checked and you don't even need to say you're making 100k+.

I marked that my liquid assets are under 25k, net worth is under 25k, and yearly income is under 25k (all the lowest you can select) and they approved me for option trading instantly.

Looking at GOOG the UI shows me put where the max loss is $8.5k. Seems reckless if they really use the information I gave them to determine what level of risk is appropriate.


Goland's debugger can evaluate expressions when paused.

https://www.jetbrains.com/help/go/debugging-code.html#924cf9...


It must be some subset of expressions (or I must have set mine up wrong), because anything that calls a function (vs a simple conditional statement) appears to throw an error for me indicating that it cannot execute.


dlv has an open PR to move the config from $HOME/.dlv to $XDG_CONFIG_HOME/dlv so that one should be fixed soon.


The article mentions how they handled it.

> While you’re making big changes, take care of your existing customers. If you’re raising prices, grandfather them to their current plan. If you’re lowering prices, give them some alternative options.


Ah, I missed that. I guess I was more interested in cases where they had difficulty in getting existing customers to accept the changes.


Without knowing their migration strategy it is hard to say. A few things I notice that get borked often with migrations are not handling redirects & internal links properly, not updating sitemaps & canonical tags, and not checking Google Search Console & robots.txt


My question was more specifically about ProtonMail's domain migration which the commenter I was replying to implied to have specific knowledge of.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: