Re: [whatwg] Accessing local files with JavaScript portably and securely

2017-04-15 Thread Roger Hågensen
On 2017-04-15 11:58, David Kendal wrote: On 15 Apr 2017, at 01:09, Patrick Dark wrote: So if you put this file in the Windows Downloads directory, then it has read access to all download files even though they aren't related? Ah, well, that's why you

Re: [whatwg] metadata

2017-04-15 Thread Roger Hågensen
On 2017-04-14 22:23, Andy Valencia wrote: Ok. Note that this data structure suffices to encode the baseline information from Shoutcast/Icecast. It does not, for instance, encode "Label", needed to do licensing reporting in the USA. "Year" is another datum often of interest. Only "artist" and

Re: [whatwg] metadata

2017-04-15 Thread Delfi Ramirez
Hi All: Some information that may be of use, concerning to the WPI rules for royalties et al in files. What we know as rights. Uh, Meta elements required * Title : 100% * Artist ( Interpreter): 12% * Time: lenght of the piece. Royalties are assigned by time

Re: [whatwg] Accessing local files with JavaScript portably and securely

2017-04-15 Thread David Kendal
On 15 Apr 2017, at 01:09, Patrick Dark wrote: > So if you put this file in the Windows Downloads directory, then it > has read access to all download files even though they aren't related? > And it grants access to all of those files—some of which may

Re: [whatwg] Accessing local files with JavaScript portably and securely

2017-04-15 Thread Philipp Serafin
If I see this correctly, we're currently talking about two different use-cases for file/directory access: 1) Giving HTML apps the ability to "open" and edit local user-provided files and directories in a similar manner to desktop apps (the soundboard example) 2) Loading (parts of) the app itself

Re: [whatwg] metadata

2017-04-15 Thread Delfi Ramirez
Hi Roger, hi all: My fault WPI, was horrendous mistake due to the keyboard, and other thingsin mind : WIPO, I meant. here below the info to avoid future re-works in the API and teh tag, if it helps. * WIPO stands for _World Intellectual Property Organization_, and the IP acronym for

Re: [whatwg] metadata

2017-04-15 Thread Roger Hågensen
On 2017-04-15 14:00, Delfi Ramirez wrote: Some information that may be of use, concerning to the WPI rules for royalties et al in files. I have no idea what/who WPI is. But StreamLicensing.com (which has a deal with ASCAP/BMI/SESAC/SoundExchange) Only require artist and title, and that

Re: [whatwg] Accessing local files with JavaScript portably and securely

2017-04-15 Thread Patrick Dark
David Kendal 於 4/15/2017 12:54 PM 寫道: On 15 Apr 2017, at 14:07, Roger Hågensen wrote: Patrick makes a good point. For example asking a user if it' sok for the HTML document to access stuff in "C:\Users\Username\AppData\Local\Temp\" what do you think most uses will do?

Re: [whatwg] metadata

2017-04-15 Thread Anne van Kesteren
On Fri, Apr 14, 2017 at 10:23 PM, Andy Valencia wrote: > But the overarching issue is that you're doing JS-initiated > network operations, and origin policy is going to stop you. > You can claim Shoutcast/Icecast should give permissive > origins, but they don't, and

Re: [whatwg] Accessing local files with JavaScript portably and securely

2017-04-15 Thread David Kendal
On 15 Apr 2017, at 14:07, Roger Hågensen wrote: > Patrick makes a good point. > > For example asking a user if it' sok for the HTML document to access > stuff in "C:\Users\Username\AppData\Local\Temp\" what do you think most > uses will do? > Just click OK, after all