Has been alive and working well (well, it's been working alright most of the time anyway, but not the plugin's/extension's fault!) for several months now on the forum. Any further issues with it should be filed upstream: https://github.com/phw/discourse-musicbrainz-onebox/issues

For the failing requests see also https://community.metabrainz.org/t/rate-limiter-has-changed/14253 and the linked IRC discussion.

For the Wikimedia issue I will add some debug output.

I have fixed that icon loading issue. As discussed on IRC for the other issues it would be helpful to see logs. I just tried it with my local VM: While I have the MB server sometimes failing when generating a onebox it is nowhere near the rate that explains that the onebox creation on community fails most of the time.

Regarding the favicon issue: I just found out I'm doing this the wrong way, https://meta.discourse.org/t/is-it-possible-to-include-background-images-with-a-plugin/36298/3

Cool. Unfortunately this doesn't work too well at the moment.

1. More often than not the onebox doesn't show up at all. This might be related to the fact that the MB server currently frequently reports "The MusicBrainz web server is currently busy. Please try again later.". When using the API I have seen this error quite frequently in the last weeks. But in our Discourse installation the onebox creation fails far more often (just had to try 9 times before it succeeded for one URL) then I get this error locally. Not sure whether those server issues are worked on or whether we can do something else to improve this for Discourse. But it is probably worth to look at the Discourse logs to see what the actual reason is or if it maybe is something else. See also [1]

2. Displaying Wikimedia images seems to be disabled. I added an option to toggle this, but the default is enabled. Did you consciously disable this?

3. Just as in other oneboxes, e.g. the Wikimedia ones, the MB favicon is supposed to be displayed in front of the title. I have added the image asset inside the plugin on the path /assets/favicons/musicbrainz.png. This works on my local Disourse VM just fine, but fails on the MB community installation. Maybe some asset caching or special treatment is in place?

[1] The behavior of Discourse in case of errors in the Onebox creation is a bit special. It will always cache the result (for a day by default), even if an exception happened. That means once the generation for one URL fails it will always return an empty box for the same URL. To work around it or for testing one can append a different query string, e.g. "?a", "?aa"

Zas added this to our Discourse last night, writing changelog topic now.

I managed to get the code into a proper Discourse plugin. Initial version with basic oneboxes for artists, release groups and releases is available at https://github.com/phw/discourse-musicbrainz-onebox . For release groups and releases the cover art from CAA will be shown if available.

I have tried to keep the info minimal for now, I'd like to extend it based on feedback.

I will extend it for the other entity types. It is not really much work, but I probably won't find a lot of time during the next weeks.

I agree with your suggested approach. Just let us know when you're ready to have an iteration go live on the site and zas'll do it when he gets around to it. Remember to "release early and release often".