Likes and blocks

The short version

Likes and blocks are a few simple rules and some numbers saved for each server. There's no AI model and no listening profile.

• Like makes a track more likely to be picked by radio and autoplay on this server, and saves it to your own liked list.
• Dislike and Not for me block a track on this server so radio and autoplay never pick it, and skip it.
• Not this artist blocks every track by that artist on this server, for radio and autoplay.
• None of this changes what happens when someone plays a song on purpose with /play, /search or a playlist.
• It's shared by everyone on the server and it doesn't wear off. Blocks last until someone runs /unblock.

Like

You can like the current track with the Like button on the player card or with /like. The button needs you in the voice channel with Orpheus. /like works as long as something is playing.

A like does two separate things.

It raises the track's weight on this server

Every track starts with a weight of 1. Each like adds 2, up to a maximum of 10. Liking the same track again keeps adding, so it goes 1, 3, 5, 7, 9, 10.

When radio or autoplay picks the next song, it picks at random, and a track's chance is in proportion to its weight. A track with weight 3 is three times as likely to come up as an unliked track in the same pool. At weight 10 it's ten times as likely.

What a like doesn't do:

• It doesn't get around the rule against recent repeats. A liked track that played recently still has to wait.
• It doesn't add a song to a station that doesn't already have it in its pool.
• It has no effect on /play, /search or playlists.
• It doesn't change which artists autoplay carries on from.

There is one more effect on radio. When a station's pool runs low (under 60 songs), it looks at this server's five most-liked tracks that are still in the pool and adds songs from artists related to theirs. Over time, a station drifts towards what the server has liked.

The weight belongs to the server, so everyone's likes add up together, and it doesn't fade over time. No command lowers a weight directly. Taking a track off your liked list leaves its weight where it is.

Can one person spam Like?

Yes, up to a point. Orpheus doesn't record who added to a track's weight, and there's no cooldown. One person pressing Like five times takes a track from 1 to the maximum of 10, the same as five people would. More likes after that change nothing.

That's as far as it goes:

• The most one track can reach is 10, which makes it ten times as likely to be picked as an unliked track in the same pool.
• It only affects what radio and autoplay pick on that server. It doesn't queue or skip anything.
• A liked track still has to wait its turn under the rule against recent repeats.
• Orpheus saves the track to that person's liked list once, however many times they press Like.

To reset a track to 1, block it with Not for me or /dislike, which also skips it. Then unblock it with /unblock. That's the only way to lower a weight at the moment.

It saves the track to your liked list

Your liked list belongs to you and follows you to every server Orpheus is in.

• /liked list shows your liked tracks, newest first: the first 15, with a count of the total.
• /liked play queues up to 20 of them, shuffled. You need to be in a voice channel, and if Orpheus is already playing, it has to be the same one.
• /liked remove track: takes one track off your list. Start typing and pick it from the suggestions, which search all of your likes. If you type a name instead of picking, it only works when exactly one of your liked tracks matches.

/liked list and /liked play work with your 200 most recent likes. If you have more than that, they say so, and older likes aren't shown or played. /liked remove can still find and remove any of them. Liking a track again moves it back to the top as your most recent like.

Each liked track is found again by its title and artist and has to pass the usual checks before it's queued, so occasionally one can't be found. The reply tells you how many were queued and how many couldn't be found.

/liked play skips tracks that are blocked on the server you're in, including tracks by an artist the server blocked with Not this artist.

Liking a track twice doesn't add it to your list twice. Removing a track from your liked list doesn't take back the weight your like added on any server.

Dislike and Not for me

Not for me, the button under the player card, and /dislike both:

1. Block the track on this server.
2. Set its weight to 0.
3. Remove it from the current station's pool.
4. Skip it. If it was the last track in the queue, that works like skipping the last track: the queue ends, and autoplay or radio take over if they're on.

Both need you in the voice channel with Orpheus, and both count as interrupting the current track, so a DJ role applies. See Controls and permissions.

/dislike lets you say why, with the reason option. The button always counts as "Not this song".

Where blocks apply

A block stops Orpheus picking a track for radio stations, autoplay and /liked play. Track blocks and artist blocks apply to all of them.

A block doesn't stop a person playing a song on purpose. /play, /search, saved playlists and the dashboard's add box all still work for a blocked song.

Blocks are per server and apply to everyone on it. They stay until someone undoes them.

Undoing a block with /unblock

• /unblock on its own lists what's blocked on this server, newest first, showing 15 with a total. Artist blocks show as "everything by" that artist, with the reason next to them.
• /unblock track: has suggestions. Start typing and pick the entry.

Unblocking a track also resets its weight to 1, so if it had been liked before it was blocked, that boost is gone.

An artist block and a track block are separate entries. If you used Not this artist, you'll see two entries, the track and the artist, and you need to unblock both to fully undo it.

By default /unblock needs Manage Server. Someone with Manage Server can let other roles use it in Discord's Server Settings, under Integrations.

How Orpheus tells tracks apart

Orpheus stores likes and blocks against the song's artist and title rather than the channel that uploaded it. That way they match the same song when radio or autoplay picks it later.

The artist is worked out like this:

• For a track that radio, autoplay or /liked play queued, Orpheus uses the artist and title it was looking for. For radio and autoplay those come from the Deezer catalogue.
• For a track from a "- Topic" channel, it uses the channel's artist name.
• For any other upload whose title looks like "Artist - Song", it uses the part before the dash, or the first name if several are credited.
• For a track from a VEVO channel, it uses the channel's name without "VEVO".
• Otherwise the upload doesn't say who the artist is, so Orpheus looks the song up on Deezer, allowing just over a second for an answer. It uses Deezer's artist and title when the matches that fit the song's length all agree on one artist, or when one of them is by the channel that uploaded it.
• If Deezer doesn't give a clear answer, a like or song block is filed under the uploader's name, with "Official" trimmed off the end. Not this artist then blocks only the song, and the reply says Orpheus couldn't tell who the artist is.

The artist and title are then tidied up so small differences don't matter. Capital letters, accents and punctuation are ignored. Packaging like "(Official Video)", "[Remastered]", "(Lyrics)", "HD" or "lyric video" is removed, and "feat." credits are dropped.

Orpheus keeps brackets that describe a different recording, so "tesla (slowed electro mix)" stays a different track from "tesla".

Older versions of Orpheus filed some likes and blocks under the uploader's name. When Orpheus was updated, it moved those over to the artist once, using liked tracks and the songs the server had played to work out who the artist was. Where there wasn't enough to go on, the entry keeps the uploader's name with "VEVO", "Official" and "- Topic" trimmed off. It still shows in /unblock under that name, but it may not match the song when radio or autoplay picks it.

Quick reference