This is a primary concern for our group as well. Many of the people who participate in our #informationwar group are under 100 SP, brand new people obviously having the default amount upon account creation.
The best way for people to get more followers and interact with people is to make dozens of comments daily on posts they find interesting. We will see a hampering of growth in tota new accounts are not abl to make many comments daily. Reddit for example, you might make 30 to 40 comments there daily pretty easily, theres so many subreddits you can follow and so many things to comment on. Steem is growing and this will be the case here as well. When users find they can't make a reasonable amount of comments they will likely not want to be here.
Are we going to have the ability to sell our excess Resource Credits and or loan excess Resource Credits? As was stated, people with a few thousand SP can basically make hundreds of comments per day and likely never will use all of their bandwidth(resource credits).
I would really like the ability for the InformationWar account to be able to give out our excess Resource Credits, and or have an option that delegates a % of our Resource Credits out to someone else.
A few ways I think it could work, first one being that you do the same as Steemauto upvoting services do it. Give us the ability to set a threshhold/limit to how much % the IW account can give out in a day. So if we have 10 people signed up under us, and we allocated in total 10% of our resource credits out, and we allow each user to only take one full percentage point per day. Very similar to how you setup curation trail upvote following on Steem auto, preset limits based in %.
Or give us the option to give someone the Resource Credit itself, so we could transfer it like we transfer Steem or SBD from account to account.
There should be so much excess Resource Credits that whales will be fighting eachother for who can price it lower, so the price of such a thing shouldn't be very high.
I welcome all criticism/feedback to this suggestion of course.
RE: HF20 Update: Restoring Continuity