MetaBrainz Meeting 2017-06-05
Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs
Agenda
Reviews
@iliekcomputers
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@ApeKattQuest_MonkeyPython
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@reosarevok
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@LordSputnik
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@Freso
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@Rob
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@Quesito
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@Gentlecat
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@bitmap
https://…
@zas
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@samj1912
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@yvanzo
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@ListMyCDs.com
IRC Logs for #metabrainz | MetaBrainz Chatlogs
@ferbncode
IRC Logs for #metabrainz | MetaBrainz Chatlogs
Spam review
IRC Logs for #metabrainz | MetaBrainz Chatlogs
Trying to assess the situation after discussions last week. However, not all measures have been implemented yet and some of the implemented measures may not show their full effect (if any) just yet either. @Rob is going on vacation this week, so we’ll try and get a review on the effect once he’s returned.
ws/2.5
IRC Logs for #metabrainz | MetaBrainz Chatlogs
There was some discussion about looking into alternatives to Kong (3scale was mentioned). There was also some discussion about how this could potentially allow for paid “premium access” to the web service and how to delegate API keys. Ultimately though, the general consensus was to go ahead with the ws/2.5 plans and iron out specific implementation details later.