Yeah but 4 months? Doesn’t inspire trust tbh…
2 Likes
So your expectation is for us to backup every Github project in existence every week for free?
2 Likes
All your project says is: “We backup and archive GitHub. Currently tracking 74484701 users/orgs.”
So what am I to expect? 4 months old backups? You don’t specify how often you back up github. 4 months seems like a lifetime.
It’s up to you how often you do it but you should specify it. Starting a github backup project with a not mentioned interval can only lead to high expectations. What good are 4 months old backups? Does it show that your project is doing a good job? Is it what users would expect once they visit your website?
I guess these are questions you have to answer for yourself and maybe the feedback in this thread doesn’t represent a major part of the people stumbling on gitbackup, maybe they do… I can’t tell you that.
What I can tell you is that there is no indication about the backup interval and 4 months old backups do sound rather poor to me.
Yes! It’s not specified on the website differently. So I do expect that all projects are backed up in a timely fashion.
If you had specified that projects get backed up every 6 months, that would be fine. But I didn’t see that anywhere.
8 Likes
I think there are 2 issues here. No. 1 is the indication of an error which should not appear no matter how long the backup interval is.
No. 2 is the interval itself. This really should be specified somewhere. To me to backup is something different than to archive. If the projects get stored to create an archive its use is in question but ok if this is what should be done it’s fine with me.
However if you want to make a business out of it, it really should be offered as service in the market place. Something like: Every 6 months it gets archived for free, but if a project wants more actual backups, then they need to pay for it.
This would result in more frequent backups of the projects in their current state.
4 Likes
Ok thats reasonable to do some expectation setting. Will make a point to be more clear about that in Gitbackup 2.0
8 Likes
If you are planning to make a paid version, I would suggest enabling backing up the issue tracker and other components that are normally ‘outside’ the typical git repo and a pretty UI that provides progress and scheduling (maybe something that looks like GitLab Pipelines or GitHub Flows). A good searching point for things that people would want could start with the whole RIAA youtube-dl fiasco (seems this: https://gitlab.com/Hurricos/gharchive-2-gitlab/ may support issue tracker recovery).
A very similar project that could be worth comparing: http://www.gharchive.org/
A good starting Reddit chat: https://www.reddit.com/r/DataHoarder/comments/jh0ds8/recovering_the_youtubedl_issue_tracker
1 Like
A Youtube backup would also be a hot idea.
1 Like
Cool idea but… realistically? We’d need a massive number of new SNOs for backing up youtube!
And… a dollar faucet for paying’em! 
1 Like
If you build it they will come 
5 Likes
Hmm… perhaps we should back up Google? Backing up YouTube just sounds petty…
1 Like
Start small. SNOs will get happy and will increase space. New ones will arrive.
Now with Storj on Coinbase we are rich and can pay for it. 
That might be true for those who’ve been around for a while, and who held their Storj tokens…
I didn’t 
1 Like
Yeah, looks like I was about a year too late to the party 
1 Like
Let’s see how long this party lasts.
When Theta announced to postpone Mainnet 3.0 the price dropped like 25%.
So I guess we need some good Storj Labs stories soon.
1 Like
Has this project been shutdown? Was looking for a repo that might have been backed up.
2 Likes
I am sorry our devs confirmed that the Gitbackup project was shut down.
2 Likes