created, $=dv.current().file.ctime & modified, =this.modified
It feels like web applications haven’t caught up with the growing weight of our lists. Depth of function within the lists hasn’t matched with the degree which we rely on them for archival with intent for retrieval.
As an example, my youtube “watch later” list is around 5K videos. As far as I can tell, if I wanted to get to that first video on the list I’d probably have to rely on API calls because the default user front end only allows for progressive loading of the list. I’m sure there are hacky ways in JS to manipulate the frontend but still. The list is simply a list.
NOTE
I’m sure some of this comes down to lack of playlist discipline, but I also keep multiple other playlists that are still growing at an unmanageable pace. My watch later list is more of a relaxed catch-all.
Similarly with Soundcloud, the page of my “liked tracks” will simply stop loading my likes after enough “load more” commands.
The richness of searching these lists is also lacking. Presuming 10+ further years of Youtube, at this current state, seems like all I currently experience will be locked away.
Photo archival services have this type of impenetrability but it’s alleviated somewhat by normally tapping into exif info, which allows for natural filtering. Depending on the service they’ll also scan for features, which can aid in retrieval.
Maybe there’s some incentivization because these older, less frequently accessed media files can be stored on more glacial long term storage. If everything were kept at arms length, there would be overhead.
My solution is personal archival of media. scdl for soundcloud and ytdl
Memorized Excess
I notice that I’ll have notifications for certain apps that are 99+ and just conditioned to be aware of this number in the app. If I notice it is 100, I got a new notification. So I’ll circle around this number with use.