I've tried to make it as easy as possible by providing the three levels of use: the exception instances for differentiating uses of the exception system, the helpers which you can use in an all-IO stack just to catch things etc, or whole-hog where you write your own functions to return Unexceptional.

I do different ones of each of these depending on context, though of course the last one is my favourite.

Part of an effort to build an open public cellular network "Soprani". Free for 30 days...but might be a hassle to pay the yearly fee since non profits often have difficulty processing payments. I've never used them - so don't know the process.

The fees aren't charged per se, but are values removed entirely from the XRP ledger entirely. Those fees also are less than a few hundred thousandths of one XRP btw.

That said, if you really want to trace back who gets the money for the fees...that would be Ripple Labs since they are the origin of all XRP. So they got paid for the XRP that is getting removed.

Also, account freezes aren't nearly as big of a deal as some people are making them to be...but knowing that might require you to actually read how the freeze function works for XRP ledger accounts rather than spread fear and disinformation.

As a business, why would I not accept a payment that will end up being worth 4x to me what I expected?

Of course, over the long term we hope volatility will slow down, but there will always be some deflationary-looking value growth against inflationary currencies when compared that way, and I think that's a good thing.

Turns out that no matter what is happening to the value, people will spend them if they're getting value out of the deal. I've bought a lot of stuff for BTC, not because I didn't believe in the value, but because I wanted the stuff.

Sounds kinda interesting. I can't tell if there's more than one person working on it. Seems like there are a lot of acronyms/technologies that all work together, with perhaps a single (or a few) points of failure.