mango
mango copied to clipboard
Hacker news submission
I submitted it to Hacker News. No one seems to care. To me this is such an important repo. https://news.ycombinator.com/item?id=18273335
@runvnc do you know of any efforts to create a similar project?
Maybe only gittorrent
On Mon, Oct 29, 2018, 11:45 PM Alex Leung [email protected] wrote:
@runvnc https://github.com/runvnc do you know of any efforts to create a similar project?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/axic/mango/issues/6#issuecomment-434189666, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVOnO6eTUA2PMq9xqO2_m2CENwUMMrsks5up_WPgaJpZM4XzHo_ .
git-ssb seems somewhat similar (though it uses scuttlebot instead of IPFS): https://git.scuttlebot.io/%25n92DiQh7ietE%2BR%2BX%2FI403LQoyf2DtR3WQfCkDKlheQU%3D.sha256
git-remote-ipld is an IPFS as git remote implementation; probably the most popular one at the moment (June 2019).
I think github decentralized may be too narrow a view. I'm getting the same feeling when I watched the JS Conf announcement of entropic, which is basically NPM decentralized. See:
- https://youtu.be/MO8hZlgK5zc
- entropic-dev/entropic#137
Someone needs to create a decentralized platform that ideally solves all the following problems in one fell swoop:
- package hosting
- source repository hosting
- creating greater incentives for people to contribute to open source
- a more accurate way of determining the value added by a contributor to a project than activity count
- open source contributors compensated relative to the value they add
- decentralized governance of open source projects
that sounds like something only a huge corporation can takkle. ;-)
I see it more realistically comming (in a good way) in the unix way, as in, putting together many small things. In that scenario, having well defined, open interface standards becomes crucial. We would have a standard API abstracting different distributed file systems (DFS), and the same for source code management (SCM), for the issue DB, for distributed indices, and so on. Then one can put together ones system out of different implementations. over time, favourites would emerge. this approach allows to harness all that is already there, and would foster collaboration between the people working on different ends of the whole system.
No one seems to care.
In my experience the HN demographic is very interested in IPFS and git, but really hates cryptocurrencies, blockchains, ... The dependency on Ethereum might be the reason