it's about the blocking occurring in reach of the user (client) or not (infrastructure quirk that has to be worked around)
141 karma · joined July 3, 2024
it's about the blocking occurring in reach of the user (client) or not (infrastructure quirk that has to be worked around)
dns-blocking is evil, no matter who does it.
stop lying to yourself and install contentblocker on your devices
webkit was forked from the kde browser, not the other way.
hearing from someone else is indeed organic
i'd argue that what you describe as "host" is rather a management vm which is allowed to talk directly to the hypervisor. though, through this privilege is most likely able to compromise it and all other guests.
but this doesn't really matter as the attack vector we are talking about already has dma and does not care about any of that.
sending the whole file at network-speed usually works fine, but maybe uneconomical at scale especially if coupled with users that skip a lot and tend to not watch the whole thing anyway.
that sounds a lot
the inverse makes equal 'common sense':
wealth begs complacency and indifference
yes, there may be a correlation but i bet it's insignificant as the factors playing into this are just too numerous.
debatable if it got more prevalent because of them, as afaik the statistics indicate both, less short _and_ less long term relationships, so :shrug:
the political kerfuffle because drm/dmca really has nothing to do with it but i can't shake the feeling that you are involved at this level. god bless
most video players also support http and there is no problem with just putting files up.
imho all the streaming tech, drm, hls, adaptive bitrate selection and whatnot, are just commercial fads to increase margin