holothuroidThis is a proposal to expand the tried tl;dr standard for further usecases.
The authors propose
pw;dr - paywall; didn't read
ai;dr - ai, didn't read
This is a draft.
Kristoffer Lawson@holothuroid honestly for me the most common would be v;dw β video, didn't watch. Could also be v;cr β video, can't read. Sick of people sharing a video explanation of something, rather than just telling.
Jouni SeppΓ€nen@Setok @holothuroid I've been using tv;dw (too video; didn't watch) to stay in the four-character format.
I blame the Google Wave product launch in ca. 2009 which insinuated that you can't understand the product by reading alone, you had to watch the video. (Not even the video helped people get it.)
@jks @holothuroid after typing my post I also realised v;cr is fun for the whole VCR link :)
Alan Langford π¨π¦π§€π§ζ@Setok @jks @holothuroid I'm thinking a site-specific ad-blocker rule for the <video> tag might be helpful here. I particularly detest when you scroll past the clip and it pops up in a sidebar like I wasn't trying to ignore it.
@Setok @jks @holothuroid My current approach is to inspect something close, like a frame or a drop shadow around the clip, then step up to the enclosing tag (often an iframe) and delete the damn thing. It doesn't happen quite often enough for a custom ublock rule, but I'm on the cusp.
@alan @jks @holothuroid this is the real stuff we need to get AI working on: shutting down the annoying crap on the web.
(Actually a previous company of mine, Attractive.ai, was almost on that mission)
@Setok @jks @holothuroid Once this third bubble of AI bursts and generative AI goes back into the lab where it belongs for a few years, that sounds like a useful application (although it will never attract VC because it's effectively counter-culture and anti-capitalist). It would make a decent FOSS project though.