5 ms·
We are building https://gitopia.org https://gitopia.org - Permanent Data Storage provided by Arweave - Works from within git with the help of git-remote-helpe
by htrap 6y ago
We are building https://gitopia.org https://gitopia.org
- Permanent Data Storage provided by Arweave
- Works from within git with the help of git-remote-helper `npm install -g git-remote-gitopia` so no need to learn new tooling
- Built-in incentivization to token holders who also take part in the governance of Gitopia
- Token holders share revenue made by the platform
- You can mirror your GitHub repositories now using the Github Mirror Action. Follow step by step from here -https://thetechtrap.com/posts/push-your-code-to-gitopia/ https://thetechtrap.com/posts/push-your-code-to-gitopia/
- We are now working on the governance and collaboration workflows that will enable transparency in open source development and provide the stakeholders to have a say in the direction of the project.
You can reach out to us on
https://twitter.com/gitopiaOrg https://twitter.com/gitopiaOrg
https://discord.gg/mVpQVW3vKE https://discord.gg/mVpQVW3vKE
- htrap 6y agoLink to git-remote-gitopia source hosted on Gitopia: https://gitopia.org/#/z_TqsbmVJOKzpuQH4YrYXv_Q0DrkwDwc0UqapRrE0Do/git-remote-gitopia https://gitopia.org/#/z_TqsbmVJOKzpuQH4YrYXv_Q0DrkwDwc0UqapR...
- SamuelAdams 6y agoHey FYI your landing page gave me this error, Firefox ESR 78.5.0. Right now it's a big blank screen with no content. {…} code: "EACCES" errno: 13 message: "Error: EACCES: Permission denied." path: undefined stack: "n@https://gitopia.org/main.js:277:55609\non/<@https://gitopia.org/main.js:277:136762\n" https://gitopia.org/main.js:277:55609\non/<@https://gitopia.... syscall: "" <prototype>: Object { constructor: n(t, n, r), toString: toString(), toJSON: toJSON() , … } main.js:339:94885 c https://gitopia.org/main.js:339 https://gitopia.org/main.js:339 configure https://gitopia.org/main.js:277 https://gitopia.org/main.js:277 store https://gitopia.org/main.js:277 https://gitopia.org/main.js:277 on https://gitopia.org/main.js:277 https://gitopia.org/main.js:277
- lftherios 6y agoThank you for sharing your work and great to see more attempts on the same problem. I am one of the maintainers of the Radicle project. The main problem we encountered with similar systems that rely on blockchains / dht for storage is the problem of 'blockchain poisoning'. This is when someone deliberately adds illegal content to an append-only source in hopes to make the sole act of replicating the project legally problematic, as correctly pointed out by Konstantin Ryabitsev of the Linux foundation with regards to a previous version of Radicle that was relying on IPFS. see https://radicle.community/t/the-radicle-social-model/317 https://radicle.community/t/the-radicle-social-model/317
- htrap 6y agoConsidering the illegal content is added by someone who has access to the repository. The right way to address that would be via community voting, which then can decide to hide it from the platform since the data is permanent on Arweave. This governance workflow will enable the community to make such content policies.
- enw 6y agoI just want to publish some code. Now I need to worry about blockchains and tokens and voting?
- Taek 6y agoI think you could add moderation to a project like this much the same way you can add moderation to a centralized project. You don't need to be as heavy handed as "community voting", you could just have each client nominate a moderator who is able to append instructions to ignore content that the client would follow. Under this model, every user (or project) can choose their own moderators, which means you don't have to worry about other parts of the community having different ideas for ideal moderation - each project/user can subscribe to the moderation feeds that they like, and ensure that they get a clean experience. This type of moderation is actually an upgrade from centralized systems, because it is much easier to nominate new moderators if you don't like what the old moderators are doing.
- simias 6y agoI'm not sure I see the point of building a complex platform with governance and whatnot. What I want is an easy way to publish my projects and for other people to contribute, I need something more like email (independent, self-hosted servers with a well defined protocol to communicate between them) than Facebook. I don't care about the governance of my git remote, or getting money out of it. I care about it being reliable, fast and simple. If I'm unhappy with it I want to be easily able to switch to a different host, or create my own. Frankly I would be perfectly fine with the current situation where you have a bunch of effectively centralized code hosting solutions (github, gitlab, bitbucket etc...) if you could trivially move your project from one to an other. For the code it's easy, git is built that way. For issues, PRs and the like it's trickier. For me that's the problem that needs solving, I don't need an ultra complicated blockchain-powered solution where people can vote for the font of the UI with cryptotokens. At a glance, and if I understand it correctly, Radicle seems more pragmatic in that way. Cryptocurrency is used for donation and securing entries in the global namespace in a decentralized way, the rest is just a bunch of standalone servers. Then you can decide to host your code on an existing instance or spawn your own. A bit like how Mastodon works for instance.
- htrap 6y agoI feel that there is a real need for permanent Storage with respect to Open Source. Code breaks when old packages are unpublished or repositories deleted. Push once and fetch forever solves this. Also Centralized solutions are providing open source collaboration tools for free, storage for free, because of their revenue from enterprise customers. What happens when they decide to shut down? or change their policies? or just comply with wrongful takedown notices?
- olah_1 6y ago> - Permanent Data Storage provided by Arweave This kind of thing always makes me sweat. Are deletes at all possible? What if someone accidentally pushes keys to the repo? On regular github, at least you can nuke the whole repo and start over if need be.
- jasonpeacock 6y agoThose keys absolutely need to be rotated, regardless of whether you delete the commit or repo after accidentally pushing them. At which point you may as well leave them there...
- olah_1 6y agoI agree, but is it possible to delete at all on ARWeave? Let’s say someone accidentally puts their full name and address in a repo.
- labawi 6y agoKeys probably aren't the best example. What about PII, accidentally committed "test" data, documents, nudes, whatever..
- jasonpeacock 6y agoIf repos are public, then you must assume that once something is pushed then someone has copied it. You may get lucky and remove/hide it fast enough, or think you did... This is an with Github today, all public repos are being watched by bots reviewing all commits for accidentally-pushed credentials. The only solution is to not use a public repo.
- olah_1 6y agoYou’re not answering the question. Is it possible to delete or not? On GitHub yes someone might be watching, but deletes are still possible.
- okokok___ 6y agowhat blockchain are you using?
- okokok___ 6y agonvm found it. It's something I've never heard of called `arweave`