5 ms·

Major fan of this idea. But how does one address the GUI challenges presented by leaving GitHub behind? It can't be understated that GitHub provides an amazing

Major fan of this idea. But how does one address the GUI challenges presented by leaving GitHub behind? It can't be understated that GitHub provides an amazing (communal/social) user experience.

scotchmi_st 11y ago
It's the same old problem of trying to build a peer-to-peer social network. How do you ensure that large files are distributed correctly and quickly with minimal security implications in an environment where nodes are constantly joining and leaving the network? Perhaps it's possible, but if it were an easy way of doing it, there would be more of that sort of thing around.
- amirouche 11y ago
  > How do you ensure that large files are distributed correctly and quickly with minimal security implications in an environment where nodes are constantly joining and leaving the network? The owner of a project will keep a node always online to fight its own churn. There is no big files in the case of issue tracker. This is not video social network. Also, video social network do work, e.g. private trackers, the only thing is that they use the web publish magnet links which can be done over a DHT cf. PPSP and tribler.
johndevor 11y ago
Wouldn't it be the equivalent of creating a BitTorrent client? There are lots of attractive and functional clients for that.
- woah 11y ago
  I think they are talking about the issue tracking etc
towelguy 11y ago
I guess the projects that can't be on github won't mind the GUI challenges as long as they have some way to have a central repository without having to maintain a server on their own.
cjbprime 11y ago
(Author here.) You're right, of course. This is just a first step. One interesting followup idea might be that the BitTorrent library I'm using, webtorrent, also works in browsers over WebRTC. But I'm not using that because I wouldn't know what to do with a git cloned repo inside of a browser tab. Maybe someone else will though. :)
- fao_ 11y ago
  Perhaps approaching it the way (I assume) TPB does it, and have the comments section, etc, handled through BitTorrent?
  - toomuchtodo 11y ago
    Comments, issues, etc could also be objects that are updated through the protocol, and signed with a public key.
    - fao_ 11y ago
      That's roughtly what I was thinking, yeah.
  - rakoo 11y ago
    TPB is just a website and doesn't use bittorrent at all.
- exDM69 11y ago
  What about using git notes (`man git-notes`) for tracking issues, comments, etc? They are stored as git objects (right?) and could be used for this task?
  - gbog 11y ago
    I thought about using git notes for this and didn't how it is better than adding issues, comments and wiki inside the repo itself. We are used to put documentation and tests alongside the code in our repo, why not add wiki and issues?
mcdonji 11y ago
Do the same thing you did for the Gittorrent. A GUI client that runs a torrent of a php file that connects to a torrent of a database file. You just need to always be connecting to the latest and greatest.

Major fan of this idea. But how does one address the GUI challenges presented by leaving GitHub behind? It can't be understated that GitHub provides an amazing (communal/social) user experience.

scotchmi_st 11y ago

It's the same old problem of trying to build a peer-to-peer social network. How do you ensure that large files are distributed correctly and quickly with minimal security implications in an environment where nodes are constantly joining and leaving the network? Perhaps it's possible, but if it were an easy way of doing it, there would be more of that sort of thing around.

amirouche 11y ago
> How do you ensure that large files are distributed correctly and quickly with minimal security implications in an environment where nodes are constantly joining and leaving the network? The owner of a project will keep a node always online to fight its own churn. There is no big files in the case of issue tracker. This is not video social network. Also, video social network do work, e.g. private trackers, the only thing is that they use the web publish magnet links which can be done over a DHT cf. PPSP and tribler.

johndevor 11y ago

Wouldn't it be the equivalent of creating a BitTorrent client? There are lots of attractive and functional clients for that.

woah 11y ago
I think they are talking about the issue tracking etc

towelguy 11y ago

I guess the projects that can't be on github won't mind the GUI challenges as long as they have some way to have a central repository without having to maintain a server on their own.

cjbprime 11y ago

(Author here.) You're right, of course. This is just a first step. One interesting followup idea might be that the BitTorrent library I'm using, webtorrent, also works in browsers over WebRTC. But I'm not using that because I wouldn't know what to do with a git cloned repo inside of a browser tab. Maybe someone else will though. :)

fao_ 11y ago
Perhaps approaching it the way (I assume) TPB does it, and have the comments section, etc, handled through BitTorrent?
- toomuchtodo 11y ago
  Comments, issues, etc could also be objects that are updated through the protocol, and signed with a public key.
  - fao_ 11y ago
    That's roughtly what I was thinking, yeah.
- rakoo 11y ago
  TPB is just a website and doesn't use bittorrent at all.
exDM69 11y ago
What about using git notes (`man git-notes`) for tracking issues, comments, etc? They are stored as git objects (right?) and could be used for this task?
- gbog 11y ago
  I thought about using git notes for this and didn't how it is better than adding issues, comments and wiki inside the repo itself. We are used to put documentation and tests alongside the code in our repo, why not add wiki and issues?

mcdonji 11y ago

Do the same thing you did for the Gittorrent. A GUI client that runs a torrent of a php file that connects to a torrent of a database file. You just need to always be connecting to the latest and greatest.