Community
Being designedWhat one listener fixes, everyone gets.
Shared by choice, never by default.
The Community Database will let WaveFlow servers share what their listeners add: synced lyrics, artist bios, album corrections, tempo and key. It fills the gaps the online sources leave, and it takes nothing from your library.
Nothing is shared yet: the design is still open.
Settings
Community
- On
Look up the Community Database
Only when your tags, your cache and the online sources have nothing.
- Off
Share my corrections
Off until you turn it on.
- Not set
Shared pool
None set: your server keeps a private pool.
What it will share
Facts about music, each kind voted on by itself, so a good bio never rides on a bad lyric.
Lyrics, plain and synced
Time-coded lyrics, word by word or line by line, and plain text, each with its language.
Artist bios
A short and a long version, in your language first when there is one.
Album corrections
Release date, label, genre and number of tracks, each field voted on separately.
Tempo and key
BPM and musical key from WaveFlow's audio analysis, so smart playlists can use tracks you have not analysed yourself.
Cover art, later
Planned for a second version, once there is a review process fit for images.
What is shared, and what never is
Shared, when you choose to
- The correction itself: the lyric, the bio, the date, the number.
- A key made from the artist, album, title and length, scrambled into a hash, so the same song finds the same entry.
- The votes the entry receives.
Never shared
- Your library: a lookup asks about one song, not about what you own.
- What you play, when and how often.
- Your ratings, likes and playlists.
- Who you are, when you look something up.
How it stays right
Votes, not algorithms
Every entry starts at zero and gains or loses one vote at a time. The best-voted one is served first; the others stay available.
Bad entries drop out
Once its score falls below −3, an entry is no longer served. Moderators can remove abuse, and their log is public.
Limits per account
Thirty contributions an hour per account, and identical entries merge into one, so repeating something does not make it win.
Each server decides
A server chooses which shared pool to follow, if any, and can drop one it no longer trusts. A family or a club can keep a pool of its own.
Where it stands
The Community Database is being designed. Its plan, RFC-004, is a draft: the data, the privacy rules and the interface are written down, four checks remain before it is accepted, and no code has shipped. It will run on WaveFlow Server.
The apps will reach it through one address on waveflow.app, so the service behind it can move without an app update. That address is already in place, and answers that the service is planned.
The plan, step by step
- Planned
Server
Storage, lookups, contributions and votes, starting with lyrics.
- Planned
Player
The Community Database joins the player's sources, and its settings appear.
- Planned
Moderation
The review queue and moderators; tempo, key and album corrections.
- Planned
Shared pools
Following another server's pool, cover art, and switching between versions of an entry.
Help shape it
Before the first entry is stored, the plan can still change. This is the moment to weigh in.
Read the plan
RFC-004 sets out the data, the privacy boundary and the interface, and says why for each.
Review the privacy rules
Before it is accepted, the plan waits for a review of its privacy section by someone outside the project.
Say what is missing
Which lyrics, bios or corrections does your music lack? Say so in the discussions.
Rather work with words? WaveFlow is translated by its listeners too. Help translate