# Revitalizing the Discourse Hub **URL:** \ **Category:** Site feedback\ **Tags:** discourse-hub\ **Created:** [24 באפריל,‏ 2014,‏ 7:49am UTC](https://meta.discourse.org/t/revitalizing-the-discourse-hub/15029 "2014-04-24T07:49:55Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![larry](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/larry/32/268016_2.png) [@larry](https://meta.discourse.org/u/larry)\ **Post date:** [24 באפריל,‏ 2014,‏ 9:21pm UTC](https://meta.discourse.org/t/revitalizing-the-discourse-hub/15029/6 "2014-04-24T21:21:05Z")
> [@codinghorror](#): > > There’d need to be a “publish” button on every Discourse profile that would talk to the hub, and when pressed, transmit all those settings up to the hub, keyed on your email address. If you need to push a button, how many people will do it? Seems like the there are two sets of info: general identity info: bio, avatar, background image, long name, username, website, etc. and discourse specific settings. We’ve already got gravatar for avatar. So, if we’re going to ask users to push a button to publish, what about pulling identity info from someplace else that’s not discourse specific? Like the Namecoin blockchain (ie. OneName) For those that didn’t see it, there was a thread about OneName: [https://meta.discourse.org/t/using-onename-namecoin-blockchain-as-global-nickname-registry/140](https://meta.discourse.org/t/using-onename-namecoin-blockchain-as-global-nickname-registry/140) The thread sort of petered out once @ryanshea hit the new user post limit. But most of the discussion about how to proof who owns which OneName isn’t important if it’s just being a used as a source of identity details. And a basic ruby OneName ruby library: [https://discuss.bitcoinhk.org/t/initial-release-of-onename-ruby-library/27](https://discuss.bitcoinhk.org/t/initial-release-of-onename-ruby-library/27) It would be a great for discourse to help build an identity ecosystem that’s decentralized, distributed and not tied to one company. And it would be something that would be useful beyond just discourse instances. It would be nice to be able to update my identity info in one place instead of having to do it across dozens of sites and apps! Centralized or decentralized, this sounds like the right direction for this feature! > [@codinghorror](#): > > should some settings be private? No, it’s already public on their user profiles. --- _[View the full topic](https://meta.discourse.org/t/revitalizing-the-discourse-hub/15029)._