#metabrainz

honestly it's yet another reason such edits are a ad idea. they are contra factual (release countries as per the date of entry, not release) "exact data" yes, but "actulaly useful" no. the edits are annoying, it breaks the server!

it should be fixed in a different way. by having a dynamic list attached to the placs it is released instead

eg, spotify, bandcamp, itunes, tidal, eh,, dezer, beatport.. what am i missing? whatever out thre

should have a dynamically thing list which what countries they are all avail in, and then some kind of fetch-by-urls cron will set a releaseas being available in "these services2 for the release placs see (list)"

and we enter "[worldwide]" because

ok so sure, these things aren't available in north korea. (and russia, probably, now) but that isn't the point

people there can use ip's and hax it. wich yes doesnt mean it was released in thoe places

but it wasn't released in norway, india or honduras either. it was released on the internet soand these places have legit interfaces with x service

if yo uput it on th internet it *is* worldwide

<akshaaatt> "Have a look at https://blog...."; <- Yeah, I tried companion objects as well, but there is a problem I was facing.

The value was accessed before it was reassigned , i.e. it was still showing 0 in the Activity despite of the fact I updated the value in PaginSource file.

* The logic for number of pages is data list size divided by offset

[musicbrainz-android] 14yellowHatpro opened pull request #111 (03master…search-pages-fixes): search-feature-improved https://github.com/metabrainz/musicbrainz-andro...

I was able to solve the problem using companion object, but the problem of access before reassignment was nerve-wracking,

* I was able to solve the problem using companion object, but the problem of access before reassignment was nerve-wracking,

* I was able to solve the problem using companion object, but the problem of access before reassignment was nerve-wracking

Great work yellowhatpro!💯

Thanks sempaii( •̀ .̫ •́ )✧

Please do tell if you feel any part needs changes

[musicbrainz-android] 14akshaaatt merged pull request #111 (03master…search-pages-fixes): search-feature-improved https://github.com/metabrainz/musicbrainz-andro...

!m yellowhatpro

You're doing good work, yellowhatpro!

oh no :(

someone reverted my changes i made in https://github.com/metabrainz/listenbrainz-serv...

probably by accident

ooh false alarm i was on my fork

oh i figured out what was wrong

i was passing the auth header

this `@crossdomain(headers="Authorization, Content-Type")` or this `@crossdomain()` is whats used for cors

would anyone be opposed to changing all instances of `@crossdomain()` to allowing the `Authorization` header? this would things a lot easier for people using the listenbrainz api

[listenbrainz-server] 14tandy-1000 opened pull request #1892 (03master…patch-2): CORS: Always allow `Authorization` header https://github.com/metabrainz/listenbrainz-serv...

So now I am done with the search feature for now, I am gonna try to fix the metadata tagging feature.

I would work on some dummy projects for now, where I will use kTagLib ヽ(✿ﾟ▽ﾟ)ノ

Thanks yellowhatpro! While I agree that the tagging feature needs to be worked on more, I would suggest you move on to implementing more features for us. Already a lot of time has been spent on the tagger, if you get what I mean.

I think the addition of collections from MB to the app wasn't done properly. Also, if you're interested, ListenBrainz addition to the app would be wonderful. Other than that if you think the tagger feature is what you wanna work on, go ahead for sure we love help in any field!

Ok then I would try Collections first, then I am going to try ListenBrainz.

So how is the collections feature done wrong??

Ok so collections dont show our collections

One thing I can observe is that only release collections are able to get updated, not others

Great observations yellowhatpro

I think we have a lot to unpack as compared to https://musicbrainz.org/user/akshaaatt/collections and the other tabs present including Tags, Ratings, etc

I think rather than separating just the collections, we can aim to have the user profile available on the app just as the website

Fragments could be used for the different tabs and the user profile page could be worked on if that isn't too big a task

You can break the task into one fragment at a time

This would solve our concerns of not having any Profile section on the app

So that means the collection section will be tranferred to the user profile section, along with other sections, such as profile, subscription,subscribers, tags and ratings

Yes, that sounds good to me

Ok then, I'll work on the basic layout of the profile section , so that it matches with the app theme as well. ヾ(≧▽≦*)o

Thanks akshaaatt sempaii for guiding me on this ( *︾▽︾)

Thanks to you yellowhatpro! 💯