@nearmax.near [Posted on DevHub](https://near.social/#/devgovgigs.near/widget/Post?id=1034) ## Idea: Bootstrapping Traction Using Shared Content Layer for BOS Apps Today we have the following apps with similar social features that solve similar traction problems but independently: * https://neardevhub.org/ * https://near.org/ main page and feed * https://i-am-human.app/ * https://nearweek.com/ Heroes (cannot find the Mainnet link) * https://near.org/nearhorizon.near/widget/Index Social features that they already implement separately are: * Posts * Communities (Implemented by DevHub and coming to other apps) The obvious problem is that when user makes a post or creates a community in one app it does not appear in the other app, unless a very custom interop layer has implemented for each pair of apps. Specifically, we very much need the following interops already today: * Funding requests posted on DevHub should appear on NEARWeek Heroes so that they can given bounties using NEARWeek Heroes payments process; * Project ideas posted on DevHub should appear on NEAR Horizon so that accelerator team can support their growth as a business; * Posts from DevHub should appear in search results of near.org main page; * Making a post on DevHub should have the same UX as near.org main page, in terms of sign-in and transaction payments, including from mobile phones. Right now the only interop we have is between near.org and DevHub, where DevHub posts are reposted to near.org mainpage, but even this simple interop already requires maintenance due to gateway updates. Having NxN custom interops for each app will not be feasible or sustainable, and it will also fragment the UX. One potential solution that was discussed recently, linked below, is to have unify apps through a shared indexing. However, it is a purely read-only solution, and does not provide interactive/write interoperability, e.g. allowing NEARWeek Heroes users reply/interact with DevHub posts. Imagine, for example, Alice and Bob commenting on the same bounty, but Alice is using DevHub while Bob is using NEARWeek Heroes. IMO the only future proof solution is coming up with the standard for SocialDB posts and communities, with most importantly flexible access-control model (shared access between the users of different apps), and require apps make posts and interact with communities otherwise using SocialDB contract only. App-specific payload (e.g. bounties data in NEARWeek) then can co-exist with shared SocialDB entries as sub-entries. Related discussions: * https://near.social/devgovgigs.near/widget/gigs-board.pages.Post?id=1033 * https://github.com/near/neardevhub-widgets/issues/137#issuecomment-1675013283