liquidex/treehouse
liquidex/treehouse
1
Fork 0
Code Issues 39 Activity

just fix

Browse source
This commit is contained in:
liquidex 2024-04-17 13:31:49 +02:00
parent 1849ae1b85
commit b8ec332de0
2 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
content/music.tree
View file

@ -10,6 +10,7 @@
+ ### fuck DRM + ### fuck DRM
% content.link = "music/spotify" % content.link = "music/spotify"
id = "01HVNX7FMW6KJC9H3CQ7TX8ST6"
+ ### Spotify + ### Spotify
% id = "01H969NN1BR7BH7M7SXBPGB0WC" % id = "01H969NN1BR7BH7M7SXBPGB0WC"

11
content/music/spotify.tree
View file

@ -1,33 +1,44 @@
%% title = "Spot(the user hostil)ify" %% title = "Spot(the user hostil)ify"
% id = "01HVNX7FMSVXFKZDB0K54S96CR"
- this page is dedicated to pointing out stupid design flaws in Spotify's user experience. - this page is dedicated to pointing out stupid design flaws in Spotify's user experience.
% id = "01HVNX7FMSP5CR54MTYRP6B76R"
+ as a paying customer I'd expect it to be better but I guess they're just not making enough money. + as a paying customer I'd expect it to be better but I guess they're just not making enough money.
what a poor, small company they are to be having these problems :( what a poor, small company they are to be having these problems :(
% id = "01HVNX7FMSV3DT95W29TDXG8R2"
- "well then why are you paying them, liquidex?" unfortunately lots of music is only available (*and* UNAVAILABLE!) on Spotify, as seen on [_fuck DRM_][page:music/fuck-drm]. - "well then why are you paying them, liquidex?" unfortunately lots of music is only available (*and* UNAVAILABLE!) on Spotify, as seen on [_fuck DRM_][page:music/fuck-drm].
from a consumer standpoint it's also really nice for discovering new music, because you don't have to pay a large amount just to give a listen to an album you may not end up liking. from a consumer standpoint it's also really nice for discovering new music, because you don't have to pay a large amount just to give a listen to an album you may not end up liking.
% id = "01HVNX7FMSR6TFJK3A9VVQ667K"
- a couple days ago I've noticed the queue in the desktop app has changed... - a couple days ago I've noticed the queue in the desktop app has changed...
% id = "01HVNX7FMSREB52W6J2D8EYK7W"
- this is how it looks now: - this is how it looks now:
![screenshot of my Spotify playlist with the queue open][pic:01HVNW10W65N70ETK28Q4C5DQ9] ![screenshot of my Spotify playlist with the queue open][pic:01HVNW10W65N70ETK28Q4C5DQ9]
% id = "01HVNX7FMS9F8T7GJQ5W3N3YTR"
- while I do appreciate the fact that you can open the queue next to your playlist, which allows you to see more information at a time, there is one very serious problem which unfortunately I cannot illustrate very well with a screenshot (at least as I'm typing this right now). - while I do appreciate the fact that you can open the queue next to your playlist, which allows you to see more information at a time, there is one very serious problem which unfortunately I cannot illustrate very well with a screenshot (at least as I'm typing this right now).
I'll try my best though. I'll try my best though.
% id = "01HVNX7FMSKSPZD19ZZ8HACY5S"
- if you hover over any of the entries in `Next from: joker_stare.png (rolling)`, you'll notice they look a bit like this: - if you hover over any of the entries in `Next from: joker_stare.png (rolling)`, you'll notice they look a bit like this:
![screenshot of a fragment of the queue panel, with a track I hovered over displaying a play button][pic:01HVNW6AQQN9345X3HXY9NN5RR] ![screenshot of a fragment of the queue panel, with a track I hovered over displaying a play button][pic:01HVNW6AQQN9345X3HXY9NN5RR]
% id = "01HVNX7FMS8JN72XSMN7EV2K0C"
- if you hover over _any_ part of the row, you get the <span style="cursor: pointer; text-decoration: dotted underline;" title="yeah, *this* cursor you're seeing right now">pointer</span> rather than default cursor, which suggests that clicking is gonna result in an action being taken immediately - except that's not what happens. - if you hover over _any_ part of the row, you get the <span style="cursor: pointer; text-decoration: dotted underline;" title="yeah, *this* cursor you're seeing right now">pointer</span> rather than default cursor, which suggests that clicking is gonna result in an action being taken immediately - except that's not what happens.
instead, if you click on the blank part, the element is only gonna get selected - as it used to in the old queue, which is _good_. instead, if you click on the blank part, the element is only gonna get selected - as it used to in the old queue, which is _good_.
but if that's what happens, that's definitely not the cursor to use. but if that's what happens, that's definitely not the cursor to use.
% id = "01HVNX7FMST447BMGG1VYARF9R"
- in addition to this, the play button that appears on the album art (pictured on the screenshot) further suggests that clicking anywhere on the row will result in playback skipping to the track you click. - in addition to this, the play button that appears on the album art (pictured on the screenshot) further suggests that clicking anywhere on the row will result in playback skipping to the track you click.
% id = "01HVNX7FMS4J4JXYQQ8D0RNQJT"
+ this threw me off the first time I saw the new panel, because I thought it was a *downgrade* in terms of functionality. + this threw me off the first time I saw the new panel, because I thought it was a *downgrade* in terms of functionality.
"what, I can't select many items in the queue now to delete them?", I thought, but no. "what, I can't select many items in the queue now to delete them?", I thought, but no.
that is still possible; the mouse cursor is just confusing. that is still possible; the mouse cursor is just confusing.
% id = "01HVNX7FMSXTXZQFDE7X5J0AFQ"
- I should probably do a writeup of textures given off by various cursors and other UI interactions someday. - I should probably do a writeup of textures given off by various cursors and other UI interactions someday.