Alright so onboarding has been discussed and complained about quite a lot lately and while I understand the complaints and inconsistencies, many of which are of course due to the very few who keep attempting to abuse the services offering free account creation, I wanted to talk about a possibly quite simple solution to it and see what others think and if it could be done. Believe it or not, I've had this idea for years but there was always a lack of want from developers to look into it deeper or consider building it, maybe times are different now with the DHF.
As pretext, though, I may be bringing up OCD quite a bit in this post as I have for quite some time been considering it having its own front-end and a possible token, just so you know and don't think I'm just trying to shill it or bring attention to it when I shouldn't, I'll save a direct shill post for it later that I have planned. (:P) But considering the idea and that we'd be able to provide the resources to maintain it, I will be mentioning it here and there, so fair warning.
The idea
Imagine you get invited to a website which from the outside may look similar to condenser, peakd or any other tribe frontend you may be used to. To register, all you have to do is authenticate with twitter or reddit or facebook or the old way of email verification. Instantly you can start using Hive.
How?
Alright so for this part, be aware that I haven't received much input from devs on the possibilities, I'm not a dev myself to be aware of all the limitations and complications this may bring up, but I welcome any comments from devs reading this.
Simply, 
When a user registers in the #web2 ways, he gets assigned an account that's not currently being used.
On the frontend, the temp account name is displayed in the username the user registered with, either his twitter account or facebook, or they can choose one but be aware that its not going to be immutable and they may have to change it later. This means that whenever that user leaves a comment, a vote or writes a post, everyone else using that website sees his username, not "ocdbtemp3". On Hive it could be included at the end of the post/comment so people are aware of what's going on as "This was posted on ocd-frontend from user Moonboi69".
The temporary accounts would exist as a roster, depending on the demand we'd create more of them, if there are 5000 users currently using Hive through our frontend and thus the temporary accounts, we'd have 5000 of them available, if more people join, we'd create more if the roster is full.
The plan would be that once a user "earns" their way to a real Hive account, they will be able to finish this "trial period", 3 hive would be deducted from their earnings or paid by the DHF or generated in other ways because after all, these users have proven themselves to be "regular" users who've been active enough to earn some Hive and deserve a real immutable web3 account.
Then the temp account would be removed and stand idle until a new registered user needs it, they and others wouldn't be able to see the history of the account on the front-end, it would receive a new displayed username and clear history. All rewards earned from the previous user would through beneficiaries have been collected and sent to the real hive account as HP once it is created. On the other front-ends it would just start displaying a different username at the end of posts and comments.
What are the benefits of doing it this way?
I assume you all imagined that the first con of this idea is that we'd have to generate quite a lot of accounts that will forever remain as temporary accounts rather than going to real users straight up. While we will still continue to offer real accounts for certain users, I think this idea will almost completely remove the abuse vector we see today where a few bad actors keep for some unknown reasons cheating their way to free accounts and the checks for abuse don't always work because IP, SMS and emails are so easy to change, access temporary ones, etc.
Registered users would be made aware of from the beginning that their trial account is temporary and on a possible clock, they'll have x amount of time to do things on Hive until they have to re-apply for one. If they don't earn their way to a real account and go afk they may lose past activity, history and earnings. This would give them a bit of a push to go out there and explore Hive after they get invited to it. Abusers would never be able to earn their way to a real account with fake or bot activity because curators wouldn't reward said activity while with initiatives like 
Why yet another frontend?
Well, this is one of many ideas I've had which I think would make Hive better. I'm not going to go into all of them now but I don't see them being included in the current big Hive frontends. If it so happens that I don't see a new front-end panning out for us I may be open to collaborate with others and hope they'd see the value in the ideas I'd want implemented and why'd they'd work well together.
Ending note
I really think this is something we should give a try and would love to hear what you guys think about it. I realize it's kind of bandaidy and there could be other possible solutions through hardforks on the blockchain level but I don't really see them being tackled or existing in the near future. At the same time getting this idea up and running as a concept and with minimal additions to the front-end while it already works and provides a solution to a big problem we've had for years, I don't think it would be too expensive or take too much time and work, but I hope devs can correct me there if I'm wrong.
There are other variables, incentives and solutions this could be built up as and with but I'd rather get into that once I know if there is an interest in getting this going to begin with. The main problem I'd want to solve as a minimum viable product would be for free accounts not to end up as keys in abusers notepad files but in genuine unique users cold wallets and if that helps other stakeholders and front-ends to save account credits, post rewards going to wrong users, etc, it'd be a win and worth all the funding it may require. Not to mention the instant access and retention to Hive for normies without needing to deal with 4 sets of keys, 4 different ways to login on our front-ends and have to learn how to use it before they know anything about it.
Worth noting that if this were to move to a proposal and receive funding, I'd want to be as transparent as possible that all and any rewards it would receive would go directly only to developers and other various costs. I wouldn't take anything for my own time and ideas spent on it, if it means making a new front-end for ocd and anyone who wants possible, I'd just be happy for it to exist as it would of course be open source.
Note: I'd be open to also collaborating with projects such as SuperHive ran by 
