Complete name a lot of times is the directory path?

[dragons4life]

I am wondering if this a bug or not, personally don't like this as this exposes the username made for your computer depending on the location.

[lordmulder]

Hello,

please explain what you are talking about (I have no idea). Maybe a screenshot could help to explain...

Regards.

[dragons4life]

"bug":

General
Unique ID : 182868284484421787873121086008998324244 (0x89932686F4195754A25B9A1E08816814)
Complete name : X:\Movies\Seven Samurai\Seven.Samurai.1954.mkv

normal:

General
Unique ID : 182868284484421787873121086008998324244 (0x89932686F4195754A25B9A1E08816814)
Complete name : Seven.Samurai.1954.mkv

[lordmulder]

How do you define "normal" ❓

MediaInfoXP, being a GUI front-end to MediaInfo, just shows the MediaInfo output as-is. And, as a matter of fact, the Complete name field shows the full path (or URL) to the media file being analyzed.

I don't see how this "exposes" anything. First of all, the username will only appear in the path, if (a) you decided to saved the media file in a path which contains your username, and (b) you asked MediaInfo to analyze that specific file. Furthermore, MediaInfoXP just shows the inforamtion on your local computer. It is not like that info would be "leaked" anywhere. Thus I don't understand what is your concern...

But, in any case, if your request is to change the MediaInfo output, then that would be a MediaInfo change request, not a MediaInfoXP (i.e. GUI front-end) thingy. Please don't shoot the messenger 😏

Regards.

[dragons4life]

I didn't define normal, I was asking if this wasn't normal.. lol.

a. you don't know if the info would be published anywhere
b. what If I do have the file were it exposes my username?
c. thanks I'll ask there.

[lordmulder]

a. you don't know if the info would be published anywhere

Well, I do know for sure that neither MediaInfoXP nor MediaInfo itself will "leak" the reported information anywhere. So, if that information gets "publish" in any kind of way, then because you decided to do so. And, in that case, it would be your obligation to review the information that you decide to publish...

b. what If I do have the file were it exposes my username?

Again, "it" (the aplication) does not expose anything. And certainly not without your intervention.

It seems kind of silly to request that MediaInfo should "censor" its output, just because someone might mindlessly "copy and past" that output to Internet (or wherever). With the same argument, you could request that Windows Explorer should not show the full path of the current directory, because eventually someone might might decide to take a screenshot of his Explorer window and post it on the Internet...

[dragons4life]

Leaks? Censoring? what are you saying? All I said was "expose", and to fix this easily you can have the filename as a complete name. windows explorer is not use in the same fashion as mediainfo windows explorer (stick and stones), why are you making a bigger deal about this than me lol?

[lordmulder]

It still does not "expose" anything to anybody. It does shows technical information to you. And only to you. So, what you do with that information – e.g. whether you decide to publish that information (and if so, what parts of it) – that is your concern! No application in the world can make that decision for you...