# -rw-r--r-- 4.8 KiB View raw
                                                                                
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
Date: Fri, 10 Jan 2020 14:08:49 -0500
Subject: Excessive disk usage on hg.sr.ht
From: "Drew DeVault" <sir@cmpwn.com>
To: <steve@stevelosh.com>
Message-Id: <BZSCJ9I8HT41.3HGAPGRZIEUDX@homura>

Hi Steve! I'm writing because our automated systems detected high disk
usage from your account on hg.sr.ht. Please note that hg.sr.ht is
designed to host source code, not large binary blobs like images, audio,
video, etc.

===============================================================================

From: "Steve Losh" <steve@stevelosh.com>
To: "Drew DeVault" <sir@cmpwn.com>
Subject: Re: Excessive disk usage on hg.sr.ht
Content-Type: text/plain

Okay.  Can you send me a link to where the space limits are defined?  I can't find any mention of space limits on any of the following pages:

* https://man.sr.ht/hg.sr.ht/
* https://man.sr.ht/billing-faq.md
* https://man.sr.ht/terms.md
* https://www.google.com/search?hl=en&q=binary%20site%3Aman.sr.ht

On Fri, Jan 10, 2020, at 11:08, Drew DeVault wrote:
> Hi Steve! I'm writing because our automated systems detected high disk
> usage from your account on hg.sr.ht. Please note that hg.sr.ht is
> designed to host source code, not large binary blobs like images, audio,
> video, etc.
>

-- 
Steve Losh
steve@stevelosh.com

===============================================================================

Subject: Re: Excessive disk usage on hg.sr.ht
From: "Drew DeVault" <sir@cmpwn.com>
To: "Steve Losh" <steve@stevelosh.com>
Message-Id: <BZSGCLNEY4VV.3I7B7BKFXYCXC@homura>

Hey Steve, the space limits aren't defined. We just monitor the resource
usage of the users, identify outliers, and then make a judgement call as
to whether or not it's considered a reasonable use of the service.
There's no limits you should stay within - you just can't store large
binary files on hg.sr.ht.

===============================================================================

From: "Steve Losh" <steve@stevelosh.com>
To: "Drew DeVault" <sir@cmpwn.com>
Subject: Re: Excessive disk usage on hg.sr.ht
Content-Type: text/plain

Okay.  I guess I assumed a single 1.1 gigabyte repository wouldn't be an
unreasonable use of a $100/year service.  I certainly didn't see any mention of
a ban on large binary files during the sign up or billing process, but I admit I
may have missed it.  I've deleted the repository.  Feel free to delete any backups
you've made of it to reclaim the space, I've backed it up myself.

===============================================================================

Subject: Re: Excessive disk usage on hg.sr.ht
From: "Drew DeVault" <sir@cmpwn.com>
To: "Steve Losh" <steve@stevelosh.com>
Message-Id: <BZSLG8ST3RV4.1GDKZBI1QJLK1@homura>

On Fri Jan 10, 2020 at 5:51 PM, Steve Losh wrote:
> Okay. I guess I assumed a single 1.1 gigabyte repository wouldn't be
> an unreasonable use of a $100/year service. I certainly didn't see any
> mention of a ban on large binary files during the sign up or billing
> process, but I admit I may have missed it.

Your account was the 2nd most expensive account on hg.sr.ht in
terms of disk usage. We don't lay out the limits precisely so that we
can exercise our discretion in these matters. Some repos we turn a blind
eye to - for example, some people have large personal trees for the
Linux kernel, pkgsrc, nixpkgs, etc - these we generally overlook,
because despite their large size they're still composed of files which
Hg is designed to work with, namely small (kilobytes, not megabytes)
plaintext files.

Hg was not designed to store large blobs, and it puts an unreasonable
strain on our servers that most users don't burden us with. I'm sorry,
but hg is not suitable for large blobs. Neither is git. It's just not
the right place to put these kinds of files.

===============================================================================

From: "Steve Losh" <steve@stevelosh.com>
To: "Drew DeVault" <sir@cmpwn.com>
Subject: Re: Excessive disk usage on hg.sr.ht
Content-Type: text/plain

I'm a contributor to Mercurial, but thanks for explaining how it's designed
to me.

I've cancelled my account, and will be moving my other repos once I get
home and can set up self hosting, so you won't have to worry about the
cost of my repos for much longer.  Sorry to be a bother.

===============================================================================

Subject: Re: Excessive disk usage on hg.sr.ht
From: "Drew DeVault" <sir@cmpwn.com>
To: "Steve Losh" <steve@stevelosh.com>
Message-Id: <BZSLXS5PTLOB.XB9XBMY3XBRK@homura>

Support for large binary files is not offered out of the box:

https://www.mercurial-scm.org/wiki/LargefilesExtension

As someone who contributed to Mercurial as recently as 2011, I'm sure
you're aware of this. hg.sr.ht is designed to store code, not your photo
archive. I'm sorry to see you go - it seems hg.sr.ht is not suitable for
your use-case.