It's: $("a[rel=xhv\\:last]:first") -- which I can't even parse, let alone figure out what it is supposed to select...
2015-01-02 00206, 2015
hibiscuskazeneko joined the channel
2015-01-02 00220, 2015
xps2 joined the channel
2015-01-02 00219, 2015
VxJasonxV
annnd search server's down
2015-01-02 00217, 2015
CatCat joined the channel
2015-01-02 00202, 2015
xps2_b joined the channel
2015-01-02 00208, 2015
xps2_b joined the channel
2015-01-02 00227, 2015
mezod joined the channel
2015-01-02 00244, 2015
burrowstrike joined the channel
2015-01-02 00237, 2015
xps2 joined the channel
2015-01-02 00235, 2015
murk_ joined the channel
2015-01-02 00223, 2015
Mineo joined the channel
2015-01-02 00202, 2015
reosarevok joined the channel
2015-01-02 00259, 2015
Julior joined the channel
2015-01-02 00228, 2015
chungy joined the channel
2015-01-02 00234, 2015
simukis_ joined the channel
2015-01-02 00238, 2015
yeeeargh joined the channel
2015-01-02 00205, 2015
chirlu`
JesseW: “a” selects all <a> elements. “[rel=xhv\:last]” restricts this set to those elements that have a “rel” attribute with value “xhv:last”; i.e. <a rel="xhv:last">. Finally, “:first” selects only the first of these.
2015-01-02 00205, 2015
chirlu`
The only complicated thing is the (double) escaping of “:”, so that it is not misinterpreted as start of a selector such as “:first”. “\:” is for jQuery, and “\\:” is in the JS code so that the string will contain “\:”.
2015-01-02 00207, 2015
chirlu`
I guess this rel="xhv:last" doesn’t exist anymore on MB pages since RDF got removed.
2015-01-02 00255, 2015
achadwick joined the channel
2015-01-02 00250, 2015
outsidecontext joined the channel
2015-01-02 00258, 2015
atsampson joined the channel
2015-01-02 00243, 2015
gioele joined the channel
2015-01-02 00212, 2015
murk_ joined the channel
2015-01-02 00236, 2015
murk_ joined the channel
2015-01-02 00244, 2015
ruaok joined the channel
2015-01-02 00257, 2015
Jinx joined the channel
2015-01-02 00219, 2015
Julior joined the channel
2015-01-02 00240, 2015
Nyanko-sensei joined the channel
2015-01-02 00251, 2015
demonimin joined the channel
2015-01-02 00203, 2015
CatQuest was just thinking the other day that he'd wnt that usability
2015-01-02 00248, 2015
Nyanko-sensei joined the channel
2015-01-02 00227, 2015
simukis_ joined the channel
2015-01-02 00253, 2015
JesseW joined the channel
2015-01-02 00257, 2015
JoeLlama joined the channel
2015-01-02 00239, 2015
darfo joined the channel
2015-01-02 00205, 2015
hibiscuskazeneko joined the channel
2015-01-02 00211, 2015
ruaok_ joined the channel
2015-01-02 00244, 2015
simukis_ joined the channel
2015-01-02 00220, 2015
JesseW joined the channel
2015-01-02 00215, 2015
CallerNo6 joined the channel
2015-01-02 00208, 2015
hawke2
luks: You around?
2015-01-02 00235, 2015
murk joined the channel
2015-01-02 00215, 2015
simukis_ joined the channel
2015-01-02 00229, 2015
v6lur joined the channel
2015-01-02 00200, 2015
storrgie joined the channel
2015-01-02 00241, 2015
srotta joined the channel
2015-01-02 00219, 2015
hibiscuskazeneko joined the channel
2015-01-02 00245, 2015
CallerNo6 joined the channel
2015-01-02 00244, 2015
reosarevok joined the channel
2015-01-02 00209, 2015
JesseW joined the channel
2015-01-02 00253, 2015
ariscop joined the channel
2015-01-02 00206, 2015
kepstin_
hmm, we should add '.txt' as a supported cover art type ;)
2015-01-02 00229, 2015
hawke2
kepstin_: Oh?
2015-01-02 00209, 2015
reosarevok
Well, I've definitely seen plenty of downloads that come with a .txt
2015-01-02 00233, 2015
hawke2
That doesn’t make it cover art though, does it?
2015-01-02 00248, 2015
reosarevok
Well, if PDF booklets are cover art
2015-01-02 00249, 2015
reosarevok shrugs
2015-01-02 00233, 2015
hawke2
They usually include actual artwork though. :-p
2015-01-02 00231, 2015
hawke2
But yeah, I guess they’re comparable to “liner notes” generally.
2015-01-02 00205, 2015
CatQuest
oh yea
2015-01-02 00212, 2015
CatQuest agrees there
2015-01-02 00219, 2015
CatQuest
in fact I have omething like that
2015-01-02 00233, 2015
CatQuest
and there's ascii art too
2015-01-02 00206, 2015
JesseW1 joined the channel
2015-01-02 00234, 2015
simukis_ joined the channel
2015-01-02 00216, 2015
Diaoul joined the channel
2015-01-02 00234, 2015
KRSCuan joined the channel
2015-01-02 00244, 2015
finalsummer joined the channel
2015-01-02 00203, 2015
finalsummer
hello y'all, i need some help w/ adding a classical release
2015-01-02 00238, 2015
finalsummer
first off: it has the numbers of the movements like 1. 2. 3., not I. II. III.
2015-01-02 00204, 2015
finalsummer
and then there's a track with two movements on the same track
2015-01-02 00242, 2015
finalsummer
what should i put in the track title?
2015-01-02 00249, 2015
reosarevok
That's fine, current guidelines don't force I. :)
2015-01-02 00259, 2015
reosarevok
So put 1. if that's what's there (or nothing, when there's nothing)
2015-01-02 00222, 2015
reosarevok
Two movements... I'd just do n. X / n+1. Y
2015-01-02 00226, 2015
finalsummer
aight, that's what's written in the booklet
2015-01-02 00234, 2015
finalsummer
so 5. / 6.?
2015-01-02 00220, 2015
reosarevok
Yup!
2015-01-02 00251, 2015
finalsummer
it's also not a western classical work, but a contempoary japanese work for a koto quartet. do any specific guidlines apply or something?
finalsummer: none that I know - if it feels classical enough, just follow CSG
2015-01-02 00249, 2015
reosarevok
KRSCuan: just commented on it
2015-01-02 00216, 2015
reosarevok
Basically, simplify pseudos in the DB to the required and useful components
2015-01-02 00230, 2015
reosarevok
Which makes it easier for editors of those artists
2015-01-02 00214, 2015
KRSCuan
The removal part is not constructive though.
2015-01-02 00219, 2015
KRSCuan
Quite the opposite. ;)
2015-01-02 00224, 2015
reosarevok
For cover art, Picard can use the RG image
2015-01-02 00241, 2015
hibiscuskazeneko joined the channel
2015-01-02 00245, 2015
reosarevok
Other things - well, if someone actually cares, I expect they'll figure out how to follow the rel :)
2015-01-02 00206, 2015
reosarevok
I'd like to wait until that happens, but I've been doing that for about a year now and it hasn't happened, so
2015-01-02 00244, 2015
KRSCuan
I don't think we'll never follow the rels.
2015-01-02 00220, 2015
reosarevok
And yes, it is - people working with, say, Japanese label X don't want all the fake releases on the way, for example (yindesu mentioned the issue a few times, I assume that's why he voted for the ticket too)
2015-01-02 00238, 2015
KRSCuan
We'd get rid of pseudos sooner than that. (hopefully in a way that doesn't break things for people who want transl(iteration))
2015-01-02 00214, 2015
reosarevok
Plus it makes it easier to just reuse the same pseudos for multiple releases of the same tracklist (digital vs. CD or whatever) since the actual relevant info is the same
2015-01-02 00229, 2015
reosarevok
Getting rid of pseudos is pretty fucking hard, sadly
2015-01-02 00204, 2015
reosarevok
Since it requires to have not only alternate tracklists, also alternate title and release artist for example
2015-01-02 00211, 2015
reosarevok
So it's not just "implement alternate tracklists"
2015-01-02 00243, 2015
reosarevok
Several people have given it quite a bit of thought and haven't reached any particularly decent options AFAIK
2015-01-02 00205, 2015
reosarevok
I'm pretty sure there's no interest on breaking anything for people who want the stuff. As you'll see, it's easy to go from pseudo to original on the site. Yes, we do need Picard to catch up, but they've caught up to a lot of things when they had to
2015-01-02 00217, 2015
KRSCuan
It will require substantial schema changes, yeah.
2015-01-02 00220, 2015
reosarevok
(not so many when it was just "kinda nice" though)
2015-01-02 00206, 2015
reosarevok
So given the DB is the main product, and we have a way to use the data for external stuff that only needs to get actually used, it seems fairly reasonable to me to prioritise DB concerns over Picard ones
But regarding that guideline, I'd prefer it if it didn't tell people to flat-out delete info that can't simply be retrieved from other releases.
2015-01-02 00235, 2015
KRSCuan
And make other stuff optional.
2015-01-02 00201, 2015
KRSCuan
I don't really buy the clogging up label pages thing.
2015-01-02 00219, 2015
KRSCuan
They'd appear next to each other if given the same dates and cat#s.
2015-01-02 00236, 2015
reosarevok
I will let the Picard devs know the change is happening, anyway, and maybe that will make them look at it
2015-01-02 00253, 2015
reosarevok
Yes, they would. So, double the amount of releases, half of them mostly irrelevant
2015-01-02 00212, 2015
reosarevok
But for me at least the main case is the fact that the more info they have, the least well they do their actual work
2015-01-02 00239, 2015
reosarevok
If you have a catno, suddenly that's no longer both the digital and the CD, or the digipack and the jewel case
2015-01-02 00259, 2015
reosarevok
(which are absolutely equal for what we care about here, the transl(iter)ation
2015-01-02 00200, 2015
reosarevok
)
2015-01-02 00224, 2015
reosarevok
And then you have two pseudos doing the work of one, or three, or n.
2015-01-02 00226, 2015
KRSCuan
Yeah, maybe without that guideline we'd have more pressure to come up with a good replacement for pseudos.
2015-01-02 00239, 2015
reosarevok
Like the last six years?
2015-01-02 00242, 2015
KRSCuan
Rather than purging them out of sight for those annoyed by them.
2015-01-02 00254, 2015
KRSCuan
eh
2015-01-02 00219, 2015
reosarevok
It's not about pressure. It's about having a team of two and a bit developers - we have talked about what to do with pseudos in every summit I've been too :)
2015-01-02 00224, 2015
reosarevok
(so, at least 3 years)
2015-01-02 00202, 2015
reosarevok
We didn't see any easy options, and we don't have the resources to throw someone for several months at the problem
