Every Noise at Once
@everynoise.bsky.social
everynoise.com and associated curiosity; see also @glennmcdonald.bsky.social
Sometimes I come across a very long playlist and I want a quick sense of how my own listening intersects with it. There are lots of ways to quantify this, but here's one of them in Curio query form (you can copy and paste the query from the alt-text):
![?28pRQNZyF8cHagMgrpLBOR.other playlists.tracks
/my artist=(.artists:@1.id.artists)
||apoints=(.my artist.counts.points...._,(1),total),alignment=[=apoints*count]#alignment](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:v7a2vpz7hyepe2upz6bmxtxe/bafkreieoo53akq4co56g3sdod7hbojhkrlzgjt5ayjljkba5gvqjpkq3dy@jpeg)
July 24, 2025 at 7:34 PM
Sometimes I come across a very long playlist and I want a quick sense of how my own listening intersects with it. There are lots of ways to quantify this, but here's one of them in Curio query form (you can copy and paste the query from the alt-text):
Do not let the world's deluge of grievous wrongs numb you to your own tiny useless delightful errors.
July 2, 2025 at 4:18 PM
Do not let the world's deluge of grievous wrongs numb you to your own tiny useless delightful errors.
If you want to scrutinize algorithmic playlists Spotify makes for you, you can copy their tracks into normal playlists and then use Curio to run queries on those. E.g.:
playlists:~<[DW 2025-06-27].other playlists
.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
playlists:~<[DW 2025-06-27].other playlists
.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
![Screenshot of my Curio query page, showing this query:
playlists:~<[DW 2025-06-27].other playlists.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
returning results like
283 label count↓ of
1 Independent 3 of [...3]
2 Art Gates Records 2 of [...2]
3 Artistfy Music 2 of [...2]
4 FRIENDSHIP. 2 of [...2]
5 QOOLONG 2 of [...2]
6 recordJet 2 of [...2]
7 1964251 Records DK2 1 of [Anteeter]
8 2019 We are Suburban 1 of [Rebecca Lou]
9 2023 maddy irene ©️ 1 of [maddy irene]
10 2023 Wormholedeath Records 1 of [Conspiracy of Blackness]
11 2074559 Records DK2 1 of [Re:O]
12 2080792 Records DK 1 of [DIGITAL LOVE]
13 210485 Manhatten Discs 1 of [DIGITAL LOVE]
14 2285049 Records DK 1 of [Crimson Crisis]
15 3105988 Records DK 1 of [Caldera]
16 3151900 Records DK2 1 of [The Hunt]
17 3304016 Records DK 1 of [DJ MIX-ICON]
18 3677236 Records DK2 1 of [Queen of Dreams]
19 3947540 Records DK2 1 of [DIGITAL LOVE]
20 5880853 Records DK2 1 of [Diamond Riot]
21 655386 Records DK 1 of [Gone Are the Days]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:v7a2vpz7hyepe2upz6bmxtxe/bafkreid5dp2fogkz4tshefuqiebr7t73gvibyztsn7rundxkvcprqp2mxy@jpeg)
July 1, 2025 at 5:20 PM
If you want to scrutinize algorithmic playlists Spotify makes for you, you can copy their tracks into normal playlists and then use Curio to run queries on those. E.g.:
playlists:~<[DW 2025-06-27].other playlists
.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
playlists:~<[DW 2025-06-27].other playlists
.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
E.g. here "Umbral Exorcism" is properly grayed out on _Moonbow Rebellion_, since it was previously released, but not grayed out on the single where it was new.
June 28, 2025 at 6:24 PM
E.g. here "Umbral Exorcism" is properly grayed out on _Moonbow Rebellion_, since it was previously released, but not grayed out on the single where it was new.
Oh, wait, in order to support multiple releases by each artist we need to get first dates by songkey, but mark oldness by track id:
June 28, 2025 at 6:21 PM
Oh, wait, in order to support multiple releases by each artist we need to get first dates by songkey, but mark oldness by track id:
Here, for example, is ?? in a Curio query that gets a playlist and some albums, annotates the track, album and artist overlaps between them (in that order of priority), and flags the tracks in each album that were previously released (by that artist) before their album appearances.
June 28, 2025 at 3:35 PM
Here, for example, is ?? in a Curio query that gets a playlist and some albums, annotates the track, album and artist overlaps between them (in that order of priority), and flags the tracks in each album that were previously released (by that artist) before their album appearances.
Made some improvements to playlist comparisons. (Also, did you know Curio does playlist comparisons?)
June 14, 2025 at 2:34 AM
Made some improvements to playlist comparisons. (Also, did you know Curio does playlist comparisons?)
Here's what you get when your software is built by people who don't live in it. This is Spotify's useful display of what you've recently played, by playlist. But if you tap a song here, it doesn't resume that playlist, it starts playing through THIS view, which is your play-history in reverse.
April 23, 2025 at 1:26 PM
Here's what you get when your software is built by people who don't live in it. This is Spotify's useful display of what you've recently played, by playlist. But if you tap a song here, it doesn't resume that playlist, it starts playing through THIS view, which is your play-history in reverse.
The Spotify iOS app has adopted the annoying habit of starting my playlists over again, so in defense recent Listmarks in Curio can now be expanded to show your recent play history within them, so you can jump back to where you really were.
April 22, 2025 at 6:37 PM
The Spotify iOS app has adopted the annoying habit of starting my playlists over again, so in defense recent Listmarks in Curio can now be expanded to show your recent play history within them, so you can jump back to where you really were.
Hooked up the DACTAL export function. Particularly useful in Curio for copying Listmarks' recent_history to other browsers.
April 14, 2025 at 6:28 PM
Hooked up the DACTAL export function. Particularly useful in Curio for copying Listmarks' recent_history to other browsers.
Also song lists.
April 13, 2025 at 2:38 AM
Also song lists.
I wanted some Curio track-flagging features that were too specific to justify adding as general features, but that in itself justified adding a custom-flagging feature.
April 12, 2025 at 1:48 AM
I wanted some Curio track-flagging features that were too specific to justify adding as general features, but that in itself justified adding a custom-flagging feature.
Curio is mostly intended for desktop use, but I've now made some very basic style tweaks for rudimentary phone-screen support. The only thing specifically tuned FOR phone use is the Listmarks page.
April 10, 2025 at 4:04 PM
Curio is mostly intended for desktop use, but I've now made some very basic style tweaks for rudimentary phone-screen support. The only thing specifically tuned FOR phone use is the Listmarks page.
If you create a playlist from a query in Curio, like NMFinder for example, you can now rerun the query to update it from the playlist's Curio page.
March 27, 2025 at 4:57 PM
If you create a playlist from a query in Curio, like NMFinder for example, you can now rerun the query to update it from the playlist's Curio page.
Some tweaks allow this query to be improved.
.(1);(0) → ...is
/(.track.album).(.of:@1) → /(.track.album).1
#rank to restore the previous sort order
and a table-display tweak to detect nested track IDs/URIs gets rid of the need for the whole final (...) remapping.
everynoise.com/curio.html?q...
.(1);(0) → ...is
/(.track.album).(.of:@1) → /(.track.album).1
#rank to restore the previous sort order
and a table-display tweak to detect nested track IDs/URIs gets rid of the need for the whole final (...) remapping.
everynoise.com/curio.html?q...
![query:
?today=([2025-03-21])._,([3/21/2025],[March 21, 2025]).matching playlists.matches/tracks|-of
:count>=2:(.tracks.album...release_date,(today),datediff:<7:>=0)
#rank=count,(.tracks.duration_ms:>120000...is),-(.tracks.disc_number),-(.tracks.track_number)
/(.tracks.album).1
#rank](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:v7a2vpz7hyepe2upz6bmxtxe/bafkreic3liq4uly4mx6nwphim65ri7bf4vzwlyvmovvqacihmypfw5ql24@jpeg)
March 25, 2025 at 8:06 PM
Some tweaks allow this query to be improved.
.(1);(0) → ...is
/(.track.album).(.of:@1) → /(.track.album).1
#rank to restore the previous sort order
and a table-display tweak to detect nested track IDs/URIs gets rid of the need for the whole final (...) remapping.
everynoise.com/curio.html?q...
.(1);(0) → ...is
/(.track.album).(.of:@1) → /(.track.album).1
#rank to restore the previous sort order
and a table-display tweak to detect nested track IDs/URIs gets rid of the need for the whole final (...) remapping.
everynoise.com/curio.html?q...
I added a "lookup" connector to Curio so that queries can navigate into any api.spotify.com links the Spotify API returns. E.g.
playlists:@1.tracks.href.lookup.results.items:@1.added_by.href.lookup
playlists:@1.tracks.href.lookup.results.items:@1.added_by.href.lookup
March 13, 2025 at 7:27 PM
I added a "lookup" connector to Curio so that queries can navigate into any api.spotify.com links the Spotify API returns. E.g.
playlists:@1.tracks.href.lookup.results.items:@1.added_by.href.lookup
playlists:@1.tracks.href.lookup.results.items:@1.added_by.href.lookup
I spent almost 5 minutes searching the web for liner-notes on this compilation to explain which tracks came from where, and then I remembered that I have a tool for that.
March 11, 2025 at 12:28 AM
I spent almost 5 minutes searching the web for liner-notes on this compilation to explain which tracks came from where, and then I remembered that I have a tool for that.
Can we collate our collective knowledge ourselves? Not as much as should be our right, but sometimes, a little bit.
open.spotify.com/playlist/2BV...
open.spotify.com/playlist/2BV...
March 9, 2025 at 7:55 PM
Can we collate our collective knowledge ourselves? Not as much as should be our right, but sometimes, a little bit.
open.spotify.com/playlist/2BV...
open.spotify.com/playlist/2BV...
The first-letter song links in NRbG were originally a placeholder idea, but I became instantly fond of them, and I'm always pleased when they reveal some pattern that is less obvious in full context, like the way this album was maybe not entirely sequenced for artistic effect:
March 7, 2025 at 4:04 PM
The first-letter song links in NRbG were originally a placeholder idea, but I became instantly fond of them, and I'm always pleased when they reveal some pattern that is less obvious in full context, like the way this album was maybe not entirely sequenced for artistic effect:
In today's big Curio news, I fixed a bug in a feature that I've never explained, and which might be too specific to my own habits to be useful even if I did. But I use it once a week, and I broke it between last week and this week, and now it's fixed again.
February 7, 2025 at 9:03 PM
In today's big Curio news, I fixed a bug in a feature that I've never explained, and which might be too specific to my own habits to be useful even if I did. But I use it once a week, and I broke it between last week and this week, and now it's fixed again.
I added Play buttons to the related-artist view.
February 3, 2025 at 11:38 PM
I added Play buttons to the related-artist view.
One of these came from a data system overseen by a human who loves music even though he personally hates jazz.
January 19, 2025 at 5:13 PM
One of these came from a data system overseen by a human who loves music even though he personally hates jazz.
This one is artist points (y) vs how many of that artist's songs you played (x).
December 31, 2024 at 7:39 PM
This one is artist points (y) vs how many of that artist's songs you played (x).
When I did the Listening Personality for Spotify Wrapped a few years ago, I reduced four measures of listening to single numbers, so I could produce a Myers-Briggs-esque 4-letter coding, because that was buzzy enough to get it shipped. But every number is a spark dreaming of being a heatmap.
December 31, 2024 at 6:42 PM
When I did the Listening Personality for Spotify Wrapped a few years ago, I reduced four measures of listening to single numbers, so I could produce a Myers-Briggs-esque 4-letter coding, because that was buzzy enough to get it shipped. But every number is a spark dreaming of being a heatmap.