Regardless, I think Apple is getting better at making money off me regardless. Their Apple One subscription is really nice. I pay it quite happily.
4,185 karma · joined October 8, 2007
Regardless, I think Apple is getting better at making money off me regardless. Their Apple One subscription is really nice. I pay it quite happily.
It has become an incredibly valuable community hub. Books are a bit of an excuse to enjoy its architecture and function. I've been there for countless hours with my children as they have grown up.
I'm also consistently impressed by the staff. In a time when every business is complaining about staffing and using it as an excuse for bad quality and bad service, it seems that most libraries are staffed with total professionals who do their job day in and day out and do it well.
God help me if you decide that because you are giving me care, you also get to decide when and how I die. I want to decide that and if I choose to go at an appointed time with my family nearby and in a comfortable setting, then I will go a happy man.
Will everyone make a decision I agree with? Are many lives worth living even when they don't feel like it? Will families and loved ones not want to let go? Are some people not mentally well enough at the time to make such a decision? Yes to all. It's complicated and difficult, but it is only more complicated and more difficult when the state tries to create rules about what is morally right and not.
One thing that really surprised us: a significant number of return users clicked "forgot password?" before attempting signup. We deduced that they believed they had an account but couldn't remember the password (this was before password managers).
When they'd did access their account, it had all their order history, email support history, etc all pre-populated.
This approach did not require us to retain any additional data on top of what we would have retained with only keeping their unauthenticated (guest) checkout orders on file.
Netflix had fine print of convenience that banned this behaviour, but at the same time they encouraged it as a growth tactic.
Now that they are choosing to limit this behaviour, doing so under the guise of copyright is disingenuous. I have no idea why the court would entertain them as an aggrieved party.
Sow and reap.
For the other fees discussed in this article, you do get additional capabilities. Distribution is not one of them, but it's not an apples to apples comparison.
I am actually working on https://tier.run in part to help create a clean separation of interests between billing (and entitlement, and metering, and feature flagging) systems and how you store and access application and user data.
With Tier we have `tier whois` [1] which lets you get the Stripe Customer ID based on your own userId.
I'd love your feedback if you think there are improvements we could make.
I learned that I was much better off integrating my passions in to my life in a more sustainable way rather than trying to turn them in to a 'thing' that I was solely focused on. Perhaps I am just... less passionate about my passions than most people, but that is what worked for me.
She's pretty much back to normal. I might say better than before as she now takes her overall health much more seriously.
Amazing.
For devs who need to implement some type of system to support all these pricing models, we recently started working on https://priceops.org
I'm currently writing "PriceOps for Product Managers" and "PriceOps for Growth" as well. We hear a lot from PMs and PMMs who are eager for something that can allow them to make pricing and packaging changes safely and reliably (and often).
Even after Stripe has been set up, you then get our SDK (node available, Go shortly) which gives you things like .subscribe(), .report(), .whois() (gets stripe ids) and .limits() that you can use to tool your app. The benefit is that when you change your plans or pricing, you don't need to refactor your front end. These are the benefits of the pillars on https://priceops.org
The CLI also acts as a sidecar in your network to do things like rollups and it manages Stripe pretty gracefully (Stripe can often have rate limits or requirements that aren't always clear). It also handles metering for you via the above referenced methods.
Someone made another comment on this thread that outlines some of the benefits vs Stripe raw as well. https://news.ycombinator.com/item?id=33431567
Tier does set up and manage your stripe account based on your pricing.json config, but we go further than that with metering, feature flag style entitlement checks, and other things we plan to provide that you couldn't do as just a provider.
Dynamic pricing works as a mechanism to bring more supply to bear. You can't do that with concert tickets. The only way it would work with concert tickets would be that as an individual concert's seats started to sell at a certain velocity, then another concert would be added for the following night. That would bring new capacity online, which would bring the market back in to "balance". This would go until there was no more demand. Their result would be the maximum number of total tickets would be sold at the maximum price possible. That is different from "15,000 tickets sold at the highest price possible".
This is nothing more than a way to disguise a significant price increase.
Stripe billing is .5%, Invoicing .4%, Tax .5%, Rev Rec .25%, etc.
Products like Checkout are included in your prevailing rate (2.9% or whatever).
You also get to manage the data and where it resides, if that is important to you.
I do agree this would be something a fully commercial project would/should focus on.
They love this project and what they do.