Shiroizu

Results 39 comments of Shiroizu

With the current rule set, the off topic content should match the songs listed under the [out of scope (cover unifier) -tag](https://vocadb.net/T/6751/out-of-scope-cover-unifier). Off topic content should also be hidden from...

"Out-of-scope" (=OOS) -field (boolean) could be added to Artist & Song -entries: - All custom tracks in albums could be replaced with proper song entries. - Original versions could be...

@CatgirlFrostmoon Thanks for the feedback. I agree that the approach 2 makes more sense for "other voice synths". For "Other vocalist", it seems like approach 1 is the best choice....

No objections from the other mods: [#mods-and-trusted](https://discord.com/channels/309072240639737866/797103264655081492/1221334684638904441). When some user action is available (tag removal), it makes sense to include the full context (tag voters). Tag removals are trackable through...

Splitting the artist types would bring some informational value, but ultimately I think it might be not feasible for a few reasons: 1) It's common for PVs to include a...

Detailed implementation logic: When a new song entry is created and some original version is specified, if the entry has only one of the three title fields filled (Non-English, Romanized...

Maybe entries with the tag [embedded-playback-unavailable](https://vocadb.net/T/6088/embedded-playback-unavailable) could be skipped by default.

@FinnRG - Probably not, as that would break the link between the relevant entry --> discussion thread. Most edit related questions have some context (entry), and it makes sense to...

External solution (partial): - [export_rated_songs_as_csv.py](https://gist.github.com/Shiroizu/541d7141888a9b22fe53d93cf356d3ad)

@FinnRG - I think this kind of split is the most intuitive: - **Interface language** = UI language, translations through crowdin: https://crowdin.com/project/vocadb - **Display language** = Entry language, translations through...