It'll be all fine and dandy at first. But I'd suggest RC delegation be more like a test drive. If a product on Hive, like a game or social frontend, gives 1000 new members a free ride, that's okay, because they currently have enough HP. The next 1000 customers expect to be treated the same as the previous 1000. Now you're up to 100k, treating everyone fairly, and realizing you can no longer afford this. Now to make a change for the next 100k customers, you must first inconvenience the previous 100k as they throw a fit and suggest the next 100k run away because insert evil conspiracy here. So it's wise to make those first 1000 realize the free ride isn't permanent to avoid the inevitable.
I rarely delegated HP. Felt like I was getting burned every time I did though. One case a dude accepted my delegation, accepted my promotion in the form of a reblog which led to attention and higher rewards, accepted those rewards, started moving the money out of the wallet and even delegated away some earned HP to a service offering a return, rather than attempting to remove the training wheels I offered.
And yes, the delegations of RC would very much be like a test drive, which is a good way to explain the Splinterlands thing. I just don't explain well :D
But, with dynamic RC delegation, it could support a massive amount of user needs without them having to have HIVE. This would eventually be the move away from Hive rewards onto second-layer tokens, where only those really interested in Hive the baselayer hold and use.
The abuse happens fast for some people, as does the entitlement. I have given away a few delegations only to have them abused and therefore, I pretty much stopped delegating to new users.
We'll see how it goes I guess. I'd prefer to see everyone who needs RC able to provide their own RC at some point sooner rather than later; decentralized as much as possible. I have far too many scenarios running through my head right now thinking about this RC stuff; need to see it in practice before I can pick it apart constructively.
This is interesting:
https://peakd.com/hive-139531/@deathwing/announcing-rc-angel-or-rc-pools-but-better
I wonder what is possible to limit through RC delegation also. Can delegated RCs be used for some operations but not others?
I saw that on day one.
Perhaps on the frontend some functions can be muted combined with the abuse mitigation that comes standard with that service. Not sure how that would gel though when scaled up. Suppose an unauthorized operation could send a command to the service and shut it down for that account, but I dunno.