Actually I didn’t sign anything. And I will watch online content however I want to. You’re free to paywall it or not put it online at all if you don’t like it, someone else will fill the gap.
How is blocking in-video apps stealing from creators? If the advertiser pays them per view, your view still counts. If they pay a commission per purchase, it doesn't matter if you skipped the ad if you wouldn't have bought the product anyway, and I doubt you buy every single advertised products to support creators.
Posting YouTube videos can just be a hobby - it was in the beginning, and that was fine. It's OK if posting a video isn't a profitable career path. Enthusiasts > "creators".
And in-video ads like these are even less defensible given that they still show up when people are paying YouTube (and creators by extension) to not display ads.
I respect your stance. A couple counter points from personal experience: even if I can't skip the ads, I'm not paying attention - I immediately mute/tune out. And the ads are typically so obnoxious that the reflex to ignore/avoid is only magnified. Is that so different from having a mechanism to auto skip/mute?
Out of the options "creators released content only behind paywalls", "users steal from creators", and "creators incentivised platforms to lobby to remove user freedom so users can't steal from creators", what actually happened was, by far, my least preferable option.
Hey all,
This is my project. Started about 6 months ago and have been working on this last update for roughly the last 3 months.
Cliparr is a video clipper for Plex, Jellyfin, and local video. It's a video editor, but its only job is to export a clip from a video. For things like gifs mostly.
When I went to add subtitle tracks to the editor, it bogged down like crazy. So, probably bigger than Cliparr is the new underlying library for the timeline editor. You can read more about that in the post.
Only if you are using a framework like React, where you create generic Button and other components.
Try using Tailwind with server-side rendered frameworks like Rails or vanilla HTML, and you will find yourself repeating the same stuff over and over again. Basically anytime you want e.g. a <button>, you have to repeat all the inline css for it. (There are plugins for Rails that adds "components", but I found it very clunky)
Not really. Every single button that gets rendered has thirty class names attached to it instead of one. It really bloats markup with duplicated classes.
Very much like map CD-rom updates, I think a lot of people wouldn't mind paying per-update for these models, and would understand the implications. That is, if there weren't so many open models available.
