#musicbrainz

Is it correct that track titles *should* have "(live)" as ETI, even if the tracks are on a live album and their representative recordings contains the disambiguation for being a live recording?

Depends on the source imo, if it has the live tags on say Spotify then it should be in the recordings title as well

Well, to me the guideline for recordings are clear, there it should be in the disambiguation. Track titles seem to be treated differently.

and when an album is mixed with, say, studio recordings and live ones, I can imagine that it can help to have it in track titles

i personally tend to drop them in albums which are obviously live (e.g. release tile is "live at <location>") but keep them when its mixed (e.g. a normal deluxe edition with one or two live performances at the end)

That would be my preference too, but that's subjective ;)

anyone else have issues going from Harmony to MagicISRC? it's my first time using both so I'm not sure if it's an issue on my end or not

What issues? :)

zoedivision[m] you'll have to be more specific - from my logs it seems like it's working fine for plenty of people.

hm, would it be edit warring to suggest an edit to undo an autoeditor edit that i think is wrong

(re: https://musicbrainz.org/edit/124414900 )

I'd suggest adding a comment to the edit explaining why you think it is wrong as a start.

@522: being an auto-editor is not a guarantee that people don't make incorrect or suboptimal edits, but yeah reverting another edit without discussion is usually a bad idea

hey kepstin,

I just moved what I was working on on my desktop, to my phone, and everything worked fine, which is good, altho I'm unsure what problem my PC was having with your website or Harmony 🤷🏼‍♀️

possibly a VPN-related issue

if you see it happen again, I'd appreciate a description of the actions you took and what you saw as a result. consider including screenshots.

there's nothing I can do about "issues"

Oh! It's reproduceable on my end. The MagicISRC page told me Javascript wasn't working, or that there was a problem with my browser

Hmm. That could happen if something in the code is hitting an exception. I think I'd need to see the browser javascript console logs to find out what's going wrong.

I see that someone else has reported this recently: https://github.com/kepstin/magicisrc/issues/17 it's possible you're hitting the same thing?

Here's a screenshot of the what the console shows!

must be something specific to my browser's settings; I just can't figure out what

looks like you might have a browser extension installed which is interfering

the logs don't make sense to me - i don't *set* any content security policy, and the site doesn't have any script named "content.js"

which firefox version are you running?

it's up-to-date — 137.0.1, 64-bit

I'd suggest disabling extensions (perhaps one at a time) to find out which one is causing issues. if you have a userscript extension installed i'd suggest testing that one first.

I went ahead and just disabled all four extensions and turned off aforementioned VPN too — query still fails, albeit slightly different from before

(screenshot forthcoming)

btw, if you take a screenshot or copy the browser console, please make sure the "login" message is hidden, since that shows your musicbrainz access token.

I should stop logging that :/

oop! thanks for the headup

(I don't see the login token visible? I must be missing it)

you have "Logs" turned off so it's hidden

(i've removed the log now, so it won't be shown next time you reload the page)

but the content-security-policy errors still make no sense. I do not set any content-security-policy on the magicisrc page...

Under FF's Privacy and Security/Browser Privacy setting, I only have "Standard" selected

It feels to me like it's probably some setting I tinkered with once and forgot about, but it's stumping me what I could be

maybe a userscript acting on the page?

that's why the first thing i suggested was disabling extensions

could you try clearing your browser cache and then trying again with extensions disabled?

so uhhh I just had the bright idea 🤪 to shift+click reload and that made the page work!

I realized the request was instantly resolving to the error page, so I guessed it must have been cached

now to work back up and figure out what caused the problem in the first place 🤪 I appreciate your taking the time to help troubleshoot it

as a fellow FF user - my current leading guess would be an extension making a call somewhere that the CSP isn't happy about

again - I don't *set* any CSP on the page. The entire JS content of the page is an unsigned inline script, so I can't :)

so there must be some extension which was enabling CSP on the page, and I have no idea what that would be or why.

yeah, that's what i meant to get at w/ better wording

So normally I have uBlock Origin block all Javascript and add sites to the whitelist as needed............ I guess after whitelisting your domain, my browser just kept reloading a cached version. I feel quite silly for not catching on sooner.

Cuz I've set everything back to normal and it still works fine

interesting. i guess ublock origin must implement that feature by setting a csp which prevents inline javascript in the page from running, while also preventing external js files from being loaded through its normal blocking engine

might be worth reporting an issue to the ublock origin folks about this problem; there might be something they can do on their end to flush the cache after enabling javascript on a specific page.

Anyways, I've updated the message displayed when javascript fails to initialize to remind ublock origin users to clear their cache or do a shift+reload.

[12:46] Sciencentistguy i personally tend to drop them in albums which are obviously live (e.g. release tile is "live at <location>") but keep them when its mixed (e.g. a normal deluxe edition with one or two live performances at the end)

^^^^^^^what I agree with

tbh, if you create an edit reverting an autoeditor, it's the same as reverting a regular editor. auto editors aren't "special" we're still humans

<- speaking as the guy in question

I left a note. myself I don't have any investment in its , I don't really agree with the refutement logic, but I'm not going to fight it. it is what it is.