Thanks Owocki to open this topic, been already looking some alternatives and want to share my thinking and discoveries around it.
Mastodont
Been reading about it for long time and seems a very nice way to decentralize an open source project.
How it works can be read here Mastodon & The Fediverse Explained | Simply Explained but basically this runs under the activityPub protocol that make possible different instances communicate with each other. (if you want to see how that data looks like check this real life example of a twitter like data)
Mastodont is a twitter like app but there are many diff apps like reedit like, youtube like, medium like etc… all built on activityPub, I only bring mastodont as one of the most successfully and popular apps using it.
In practice
Lets talk for example about bounties, what if someone want to run his own bounties instance? well will be just them going and run the repo on their own servers and then decide which others servers data want to share with.
Data
The other part of it is data owning as you can actually see the data on others instances you actually can walk away with it. Lets say Polkadot folks decide to run his own bounties platform, some user original from Gitcoin can decide start only using polkadot instance instead, so even if gitcoin is turned off the user lives on the “Fediverse”
Innovation
Something I really feel could be explored and not aware nobody is doing, is mixing the best part of 2 worlds web3 and activitypub protocol. So going further seems there is a lot to be explored where we could be, for example, using decentralize DBs to store the data instead of instances DB.
What are the wins? Well we could be providing good way to people run his own instances of “bounties” but at the same time using a well funded protocol like activitypub we provide a solid architecture foundation for makers, where someone could just grab the backend and rebuilt all the product with a diff UI, or even extend the functionality.
Today
As a core dev member this could be a nice way to start thinking a way to build and rebuild things on Gitcoin but in a way we are attached to a pattern that scales and is open by default so as our intention to be more REST like application under json data endpoints and deciding how to open that data from the time the feature / product is build and not something to figure out later, making it more secure.
Im curious to know if there are some others already looking at it and share their ideas, opinions or anything.