#musicbrainz

What are you excited about? Going to a sho tonight?

[12:12:22] <MajorLurker> Ok that makes some sense....however yesterday I was getting in to search for a release to add and it was only crashing after that (so ----Enter Artist ---- crash)

Yes, this was fixed yesterday. https://github.com/metabrainz/musicbrainz-serve...

chirlu: Speaking of curiousities related to read-only mode, is https://tickets.musicbrainz.org/browse/MBS-8946 non-feasible or a bad idea?

I’m not sure about OAuth2.

Generally, the right approach would be to move the whole user account thing out of MBS.

We already skip updating last_login_date when in read-only mode.

Freso: Can our Discourse change a post to a wiki like I think I have seen somewhere ?

(btw I remember there were pros and cons when changing a post to wiki but forgot what)

jesus2099: Yes.

(cannot revert to post, for instance, is a cons)

thanks for the info :)

Freso: such a topic is just awful, isn’t it ? https://community.metabrainz.org/t/feature-sugg...

i mean this topic will contain tons of unrelated stuff that could be followed only by a few hardcore feature fans

loujine and I wanted to make a kind of “User script news” topic in which all user script authors could post updates (**new script** announce and **important new features** on existing script)…

User scripts fans could watch the topic…

but, yes, I see how it can turn into something difficult to follow if some discussion slides in

jesus2099: I'd suggest that you agree on a tag instead.

Users can also follow/watch a tag.

I fear having many one post topics…

And it gets popular enough, I can easily select all posts with the given tag and move them to a new category.

You could make a topic per script.

but that sounds interesting, what do you think loujine (when you’re back) ? :)

loujine and I thought it would be fun having a unique news topic, filled with screenshots and such. And that we would split all “off topic” and discussion/question posts to unitary userscript topics (one per script)… so unitary script topic would only exist if someone really wants to discuss it. avoiding single post topics (with only a news inside and no one interested to participate)

I’ve not really used tags in Discourse (especially not as a reader)

It’s true that thanks to CatCat / CatQuest, we have https://community.metabrainz.org/tags/userscripts and https://community.metabrainz.org/tags/userstyles  :)

loujine: check this out and what Freso said ↑ :)

gcilou: https://community.metabrainz.org/t/new-artist-i... - if you care to respond. :)

jesus2099: Aren't you at a level where you can make new tags too?

thanks

anyone can now, I guess

Freso: ↗

I couldn’t then someone said we should be able and now we can, IIRC

at least I can

jesus2099: No, I believe you have to have at least passed the "new user" stage.

But maybe I set it so even new users can.

(so, short answer: yes) :D

Freso: jesus2099: ack

let's start by using a tag then

what’s ack ?

Freso: I had to search shrug, i found that ¯\_(ツ)_/¯

and https://en.wikipedia.org/wiki/Shrug

as long as it is easy to change our mind and regroup in a category later if it is better

Freso: ↗

jesus2099: ack = reçu 5 sur 5 :)

héhé, merci. et :shrug:… ← ça veut dire “j’sais pas / m’en fout” ?

“j’sais pas / m’en fout / ç’pas moi” ?

"hausse les épaules" je crois

hey so with this tag, loujine, are you ready to start the user script screen shot feast ? R U RAYDEE ?

free time permitting, yes :)

same for me, I’m more than ready to post tons of them when I’ll have time ! :D

what tag would be the best? "greasemonkey"? "userscripts"? "addons"?

let’s keep userscripts, no ?

that's probably the most precise, even if not clear for beginners (who are not the main target anyway)

replied. let me know if something I said is confusing

it’s the most frequent word used for repositories. And it’s not making advertisement for any of the engines… even if Greasemonkey is entitled to get tons of greetings (but I think Opera did invent User JavaScript first)

jesus2099: Anyway. On those pages, you should be see https://imgur.com/P5jArF6 - click on that and you're able to watch or track (or mute!) any given tag.

You made me notice that about 20 minutes ago, Freso :)

(don’t forget I’m super intelligent)

Freso: well, I didn't know that, so thanks :)

Freso: you have split that feature suggestion topic : good work ! :)

loujine: Discourse is making local copies of images we post on it, that’s great. Don’t worry about where to host your image.

Also, if you screenshot something directly into the copy/paste buffer, you can just Ctrl-V the image into the post.

You don't have to store it as a "real" file first.

nice

Yep. :)

(Of course, if you want add stuff like arrows etc. to the image, you will want to save it locally to do the editing on it first.)

sure. I actually started taking screenshots yesterday to put on a wiki on bitbucket

:)

« if you want add stuff like arrows etc. » ☞ http://i.imgur.com/Wh7QD.png

haha

reosarevok: srsly, 9gag?

CatQuest: ?

srsly ¯\_(ツ)_/¯

bye :)

Freso: conference pears

are there change notes for the recent schema change release?

Oh.

johtso: Soon™.

awesome :)

johtso: We're still not fully done with the release. :(

(Hence also why we're still read-only.)

How right I was to suggest changing “tomorrow morning” into just “tomorrow”.

:)

it's still morning somewhere :)

But those places may be "the day after tomorrow" by now. :p

(I guess not, but eh.)

ha. it's still morning in half of the US :)

ouch, good luck with the issues

found the schema change details that were posted a while back https://blog.musicbrainz.org/2016/03/15/may-201...

alternative tracklists is very exciting

Ah, I see there won't be UI yet

damn

so, uh... what the hell is postgres doing that it's this broken?

sorry, I guess I should have asked that in a way that doesn't sound so surprised that your database engine is so broken.

darwin: Uh, old C extension that started trimming strings to 64 characters after the Postgres upgrade.

Not really sure if it was relying on undocumented behaviour or if the API got changed in 9.2.

(C extension... in your... database.. ? hurrr?)

(I am pretty ignorant of how unusual or not that might be, in Postgres land, in fairness)

There were also some OS settings that no longer were a good match.

Most of the time was diagnosing, though.

what does the extension do?

It writes changes in rows to a table that is later turned into a replication packet.

it's a... trigger?

uh, also, uh, what?