This is the one I use, too. Learned this and the near-instant one, but this is actually really practical and produces a nice and even knot. Winner!

This has me wondering if I can use my release Switch as an Android TV box

The cost of rest of the hardware, running it constantly, and 'admin' overheads aren't to be scoffed at to be fair.

I worry about potential bans from scraping files through this sort of thing.

No files are involved. It's about backing up the metadata -- your playlists, liked songs.

So you can recreate the playlists on another Spotify account or another music service.

Exactly the same here, I just wanna back up my playlists and liked songs, in an organised and tagged manner, at a non-potato quality.

I miss it deeply.

OiNK before that, too. Once waffles and what disappeared then I was never 'able' to get on to one of the newer ones… the whole process is some real archaic thing. Used to have a great 'profile' on those others, but yeah.

I think it would be very beneficial if the browser vendors, together with screenreader vendors and those who use them, were able to come together to actually unify the approach to how elements/these attributes/etc. are communicated to the end user.

They're working on it in the "Core Accessibility API Mappings" spec

https://www.w3.org/TR/core-aam-1.2/

this part is covered. the issue are the web devs who need or decide that they need to repurpose a set of elements into another set of elements and skip informing the non visual user about that.

I have it pointed at my domains just for basic stuff and luckily that seems to be working at least.

Railgun trail to match the reload time, always!