LISTSERV mailing list manager LISTSERV 16.0

Help for ARSCLIST Archives


ARSCLIST Archives

ARSCLIST Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ARSCLIST Home

ARSCLIST Home

ARSCLIST  October 2019

ARSCLIST October 2019

Subject:

Re: Suggestions for Repository or Cloud platforms to host Montreal Gamelan archives

From:

Laurent Bellemare <[log in to unmask]>

Reply-To:

Association for Recorded Sound Discussion List <[log in to unmask]>

Date:

Mon, 7 Oct 2019 19:43:02 +0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (125 lines)

Thanks for all the replies, it sure helps me evaluate how realistic is my
inquiry. I will think about it and choose a compromise solution.

Thanks to all!

Laurent Bellemare,
Étudiant en musicologie


end
--


Le lun. 7 oct. 2019 à 16:44, Eli Bildirici <
[log in to unmask]> a écrit :

> Hi Corey-
>
> ...if there is data compression at all on a server you are uploading to,
> then it is probably lz4 or something, at the filesystem level. This is both
> free from a performance perspective and lossless from a data-integrity
> perspective, provided your host is using an enterprise-grade filesystem
> like ZFS. Which it's practically guaranteed that they are, in 2019. If you
> want to be extra paranoid, you can, before uploading, generated parity
> files using something like QuickPar or similar, and then back those up, but
> this is not necessary, at least not for the purpose of making sure your
> providers aren't messing with your files somehow, because this isn't
> happening. Think about it. If it were, there would be no point of e.g.
> uploading a hash along with a file, if it turns out the file you've
> uploaded is modified upon upload thanks to the compression you seem to be
> afraid of, then that hash'd fail every time. IRL this doesn't happen. Now,
> if you're using a service that explicitly uses lossy compression (e.g. if
> you give it wav/flac, it converts to mp3/mp4/ogg/opus; if you give it a
> tiff/png, it converts to jpg/heic, etc)...well it's told you that in
> advance, and anyway such a service would not be appropriate for this use
> case. But it seemed like you were making a broader claim than that here,
> particularly in your last email.
>
> Laurent--
> I don't think what you're looking for--basically, archive.org, but with
> access control--exists. And if it did, no way it would be free, unless
> ad-supported, which is kind of icky for your use case. You could try using
> a web portal that'll have all your metadata etc that linked to files hosted
> on other service, but this is, obviously, inelegant, and not all that
> different from what you're doing--just more pleasant to navigate than a
> directory at Mega. It also wouldn't really solve your access control
> issue--you could restrict who can see the links to the copyrighted material
> like this, but the links themselves wouldn't be temporary, so you That
> said, it'd probably be cheaper than paying out your nose to host all your
> files, though. Sorry nothing better is occurring to me right now, but
> looking fwd to other responses--hope you find what you're looking for.
>
> Eli B
>
> October 7, 2019 12:56 AM, "Corey Bailey" <[log in to unmask] (mailto:
> [log in to unmask]<[log in to unmask]>)>
> wrote:
>         Hi Richard, Yes, that was a sweeping statement, meant to raise the
> awareness of those who use the internet (Cloud) which, includes the vast
> majority of us and our offspring. The fact is that most, if not all, who
> rent server space use some kind of data compression to save space (and $).
> Most will not tell what they use. You can buy data compression/encryption
> software that will return bit-for-bit. Some are OK with the concept, some
> are not. One possibility is to use a code (There are many variants) in the
> metadata of the files you plan to store to insure that you get the same
> files back. Here is another sweeping statement: I try and avoid those that
> do data tracking. ALL OF THEM (can you say VPN?) and, I plan to disengage
> completely from all social media by the first of the year because of data
> tracking regardless of your settings (preferences). I do however, use
> Dropbox. At least, temporarily. I plan to dump them as soon as my paid
> service runs out due to slow upload speeds. I have a 70Mbps service but
> Dropbox is very slow to upload, about a third, or less, of what I have
> available (Can you say /throttling/?). I don't use Backblaze because I
> clone my boot drives instead of doing backups. Apologies to the list for
> being way off topic. Da Ole' curmudgeon, Corey Corey Bailey Audio
> Engineering www.baileyzone.net On 10/6/2019 11:24 AM, Richard L. Hess
> wrote: Hi, Corey,
>
> That is a sweeping statement that I think needs clarification.
>
> My take on this statement is:
>
> Google Photos: True if you select the unlimited option, not true if > you
> pay for the storage.
>
> Dropbox: The only compression that they use is perhaps totally >
> transparent data compression on the server side (I have no evidence of >
> that) but they deliver files back to you as you sent them. While >
> originally running on Amazon Web Services, they have migrated to their >
> own multi-location cloud.
>
> Backblaze: Although not a cloud service per se, but rather a backup >
> service, I believe they do de-dupe your files and only save one copy, > but
> otherwise they give you back what you sent in (again, they may use > sever
> side lossless data compression).
>
> Amazon Web Services/Glacier/etc: These services give you back what you >
> put in.
>
> There are many others, but these are some I've looked into over the > past
> few years. At the moment, I use the first three and had long had > a
> thought about using AWS/Glacier.
>
> I don't know a good solution that meets the OPs requirements except >
> perhaps splitting items between a service which allows passwords (paid >
> service) and the Internet Archive for the free-access stuff.
>
> Cheers,
>
> Richard
>
> On 2019-10-06 1:44 p.m., Corey Bailey wrote:Hi Laurent,
>
> Know that almost all on line storage uses some kind of data >>
> compression. Besides your password requirement, you need to consider >>
> which type of data compression will best suit the needs of your >> material.
>
> Best,
>
> Corey
>
> Corey Bailey Audio Engineering
> www.baileyzone.net
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager