11–20 of 60 posts
This project really needs more attention. Would have resolved the issue we had earlier today. Some others ideas: * Write a client in C, JS sucks * Make a web-frontend for this so average users can jump on quickly.
There’s also git-ssb https://github.com/noffle/git-ssb-intro
Looks like a good fit for youtube-dl
This project really needs more attention. Would have resolved the issue we had earlier today. Some others ideas: * Write a client in C, JS sucks * Make a web-frontend for this so average users can jump on quickly.
The author doesn't think so though https://news.ycombinator.com/item?id=24876815
Hi! I'm the GitTorrent author. It feels strange to have it show up on the front page whenever GitHub does something bad, more than five years later. Bitcoin and BitTorrent v1 were plausible substrates in 2015, but no longer. I think Radicle ( https://radicle.xyz ) is the project most deserving of attention at the moment. The hardest thing about such a project is economic: how do you handle issue/comment spammers? Or…
In effect you can do the same thing better by using a cryptocurrency with cheap transactions, e.g. Bitcoin Cash's Memo.cash. This way git hosts are compensated while at the same time making it too costly to spam.
Longer packfile creation processes will require a greater transaction fee or otherwise be ignored based on heuristics created by the client. This will prevent infinite CPU building packfiles issues in addition to fair compensation for increased computation cost. All while the miner is incentivized to minimize the time to be able to reap that block reward in the context of market competition.
Hi! I'm the GitTorrent author. It feels strange to have it show up on the front page whenever GitHub does something bad, more than five years later. Bitcoin and BitTorrent v1 were plausible substrates in 2015, but no longer. I think Radicle ( https://radicle.xyz ) is the project most deserving of attention at the moment. The hardest thing about such a project is economic: how do you handle issue/comment spammers? Or…
Add:
> And what happens when someone forgets their password or loses their private key?
Here's an approach I found interesting: https://darkcrystal.pw/
The real problem is hosting issues and PRs in such a way. Github has an API and it's possible to script the backup but source code gets backup automatically so when the takedown strikes it's not a big problem.
This project really needs more attention. Would have resolved the issue we had earlier today. Some others ideas: * Write a client in C, JS sucks * Make a web-frontend for this so average users can jump on quickly.
> This project really needs more attention. Would have resolved the issue we had earlier today. Some others ideas: The author doesn't think so though https://news.ycombinator.com/item?id=24876815
Hi! I'm the GitTorrent author. It feels strange to have it show up on the front page whenever GitHub does something bad, more than five years later. Bitcoin and BitTorrent v1 were plausible substrates in 2015, but no longer. I think Radicle ( https://radicle.xyz ) is the project most deserving of attention at the moment. The hardest thing about such a project is economic: how do you handle issue/comment spammers? Or…
Absolutely, because it is truly innovative - and you're mostly in uncharted waters. We're at peak cloud right now, and what projects such as yours offer is a glimpse into the post-cloud future. We're going to look back and say - what were we thinking when we decided to move compute and personal data storage into datacenters while carrying powerful supercomputers in our pockets. Add: > And what happens when someone fo…
Earlier quoted context omitted.
There’s also git-ssb https://github.com/noffle/git-ssb-intro
Unfortunately, SSB uses far more JS than they really should.