Release preparation v1.45

[Pac]

@Pentium100

Large files get split up into segments (IIRC by default it’s 64MB).

That’s what I thought but I wasn’t sure it was about those same segments.
Well then it’s even worse? Counting files is easy and makes sense to users, but counting segments? Segments are a technical thing behind the scene, how is a customer supposed to know how many segments their files count?

@SGC

i suppose somebody could upload billions of segments which might be bad for the network, my guess would be it’s to ward against malicious, ignorance and mistaken use of some kind.

I don’t see why billions of files would be bad, and in fact many projects have in immense number of files in the development world, because of wonderful things line NodeJS for instance…

What I would be afraid of would be the use of file names only for storing data for instance: that would be a way to abuse the system, I mentioned it long ago already:

Can Storj can lower costs and increase usage?

I’m wondering if the real pb with not charging objects would be that you could theoretically store data in 0 byte files, just by putting data in file names (encoded in base64 for instance). That would be incredibly inefficient performance wise probably, but it would be free… Hence the fee per object. That’s my 2cts anyway

And that’s why initially Storj charged “$0.0000022 Per Object Per Month”.
But they decided to remove it later on!