The Bitcoin Economist Name and picture from twetch — not on-chain. The signature is; the profile is not.

So yeah, you still need the address of the referrer embedded in any payment for an external Paychain app to gen a paychain.

If you want to make a linked list of referral payment transactions that is necessary to generate a paychain, the Paychain app must generate a referral URL that includes the address from which the referrer paid for the content.

Joe Rogan would also do great on Twetch.

I really like Ubuntu Linux 20.04. It's the first time I've ever liked Gnome. If you haven't tried it, it's pretty good. Everything I wanted to install was readily available in the repositories or as a snap. That includes NodeJS and Visual Studio Code.

Bitcoin is beautiful. It's one huge linked list of transactions from which you could generate many meaningful linked lists of transactions. In my paychain use case, I just use the linked list to pay for successful referrals.

If you have a high volume/low fee business, your biggest goal is to increase volume to the point it is profitable. Sell every feature that might increase volume at cost. If you get rare sales on features, those features essentially don't exist anyways.

As long as you used the same address for a particular piece of content, it wouldn't be difficult to create a paychain just from the transactions without embedding any further IDs.

Froggy caught me. I know nothing about business. LOL!

Twetch is run by very stubborn youngsters, but I still hope it kicks Twitter's ass. Lately Twitter has been self destructing..and all I've been asking of Twetch is that they put in the infrastructure for the new people who will want to make money.

Paychain will make it possible for Peter Schiff to come on here and have a marketing team promote the shit out of his feed and get seriously paid...Youtube level income. And there are plenty who are making money there.

Paychain:

https://powping.com/posts/81ea02abdf78766cf4144fbfd9c0a4f331645f801f950b5027b1fd26f85c4fd8

The post for Paychain on Powping isn't even as complete and fun as it can be. It has fixed payee slots, variable payee slots. But it can have "sticky" slots, where first purchaser becomes a fixed payee. Curation heaven!!!!!!!!!!!!!!!!!!!!!!!!!

Froggy, troll toll really? Maybe you're too temperamental if you can't tell I'm not a troll.

Implement a revenue share first, which is fundamental. See Streamanity. See Paychain. Then implement a mobile app. Then reevaluate pricing. Or don't and fail.

Another business bug is charging additional money for features that would bring in volume. You forget Twetch is fundamentally a high volume low fee business?

Twetch is beautiful and easy to use. Your bugs are business bugs.

A systemic mistake you're making is monetizing poorly.(need auto revenue shsre).

Make a mobile app if you're going to build infrastructure you need to support. Desktop app? LOL!

Absolutely nothing until you implement automatic revenue share infrastructure. That feature first. Paychain ideally, But even something like Streamanity implemented at a minimum.

Twetch is beautiful and easy to use. Your bugs are business bugs.

A systemic mistake you're making is monetizing poorly.(need auto revenue shsre).

Make a mobile app if you're going to build infrastructure you need to support. Desktop app? LOL!

When I was a kid I gave my pet frog a funeral and carefully disassembled his lego estate. To mom's dismay and father's delight, I used the garbage disposal for his funeral.

So let it never be said that I do not hold a warm place in my heart for frogs.

You're right of course.

I guess that is all. See you next month.

4/Just a reminder..I was talking about Paychain and automated revenue splitting/sharing in May of this year. It is a great way to monetize apps. It literally creates a curator market. And content creators don't have to work as hard promoting content.

3/I think referral chains add a lot of excitement and incentive to curate. That said, if you're not at least implementing a revenue sharing infrastructure like Streamanity is doing, you are limiting your app's ability to monetize.

2/Embedding referral records into payments provides all the info required to construct a referral chain to dynamically add to some sort of revenue share similar to what is implemented on Streamanity.

1/One way to implement referral chains is to embed referralIDs in links. Then embed referral records in payments (contentID, myReferralID, refererID).

So yeah, like Streamanity every app should empower content creators by allowing a revenue share. Include a referral chain for a few of those slots and you have curator heaven.

Streamanity implemented revenue share! That Jack Liu guy is always ahead of the curve! If he adds referral chains to that revenue share he will steal my thunder completely, which is great.

Is buying the chat feature a test? On one hand I want to support Twetch but on the other I want to smack froggy for pricing it so ridiculously.

Honestly I didn't realize economics is so hard. But all the BTCers and other projects that totally screw up the economics proves that it must be harder than I think.

@4 App devs, if you don't want to implement infrastructure for content creators to split their income automatically, have the courtesy letting them choose an external address.

That way I can write my own external Paychain.

Every month I check in on Twetch. Everything gets much better except the economics.

It's easy..don't be greedy and empower the content creators with full control of splitting the revenue (cough paychain).