There was no mention of a mistake in the code in any of these posts, just explanations of how the code functions. This platform isn't for musicians who want to be DECENTRALIZED and SELF-CUSTODY their art and sats. No matter how much OP meanswell, rugpulls remain a possibility. If you want MORE details as to MY PERSONAL issue with the code, this platform utilizes the Podcasting 2.0 RSS protocol but (unlike every other P2.0 app) does not share self-hosted RSS feeds due to its walled garden design. I don't like it so I don't use it. Simple. Artists deserve to know THERE ARE OTHER OPTIONS which was why @𝕾𝖊𝖗 𝕾𝖑𝖊𝖊𝖕𝖞 started this thread.

There is so much to respond to here. You clearly dont know who we are nor our role and experience within the v4v music ecosystem. You rush in with an opinion not knowing the facts and project your ignorance on us. The people commenting, including myself, are producing v4v music shows, onboarding v4v artists, developing v4v music apps and/or v4v musicians. These critiques come from a place of intimate knowledge, not speculation. Unlike you, we are the boots on the ground who laid the foundation wavlake was built on. Most, if not all of us, have been active creators and participants in the v4v music ecosystem longer than you've had that npub (Dec 1, 2023). We dont need to audit the github repository, there is no "mistake" in the code. Everything is functioning exactly as intended. Our evidence is based off the facts of reality. It is clearly transparent that our (and everyone else's) music uploaded outside of wavlake does not appear in wavlake. I state that in no uncertain terms and wavlake does not refute it. If you dont believe me, go take a look at the rss feed for any track that appears within the wavlake catalog and you will see that exactly zero are uploaded from outside of wavlake. And I'll say it again, this is a structural design CHOICE made by wavlake. They are free to make those choices and while I dont agree with that choice, I dont fault them for chosing their own path. And in all fairness, they have never claimed otherwise. But freedom of choice does not mean freedom from consequence or critique, especially in an open ecosystem. What most of us have issue with is that this design choice (whether intentional or otherwise) results in a significant portion of the ecosystem to be excluded by the largest platform in the very space that enabled it to exist in the first place. This type of exclusion (again, intentional or otherwise) goes against what we believe to be a core ethos of the valueverse. The bigger issue is that most artists and fans dont know this is the case and thus cannot make an informed decision unless it is in the public discord. As supporters of artists and consumers within the valueverse, its our responsibility to ensure they have the full picture so they can make their own informed decisions. It is unreasonable to expect most musicians to audit code. They are musicians, not devs. That is why we are here putting our necks out and taking the brunt of backlash from ignorant people like yourself so that artists are better informed. We are simply calling it as we see it. Everyone (creators and consumers alike) are free to make their own informed choices after that, but that can't happen until all the cards have been revealed. Telling a "whistleblower" to sit down does not make you the white knight you think you are.