Hi there!
I've noticed that the new update brought us DLC feature and some people are pretty familiar with it (according to discussions in the MMD-thread) while others (including me) are not. Not gonna ask questions like "what is it" and "how do i use it" (I did some research after all), but rather "what is the intended usage" and "how is overall experience".
Suppose Alice wants to share some files in the thread, Bob wants to download them and Chuck is the rightful owner of these files armed with DMCA-hammer.
Without DLC the scenario goes like this:
- Alice uploads files to pixeldrain, gofile, etc.
- Alice posts message like:
- (optional) Bob asks how to decode these things for the nth time per month
- Bob decodes url to the service of his choice
- Bob manually downloads files from the url or put it into some downloader (JDownloader, gallery-dl, curl, wget, etc.)
- Chuck opens anime-sharing.com, searches for posts containing "Chuck69", "Q2h1Y2s2OQo=", "Y2h1Y2s2OQo=", ⒸⒽⒽⒸⒽ⑥⑨
- Chuck follows the steps of Bob
- Chuck sends takedown notices to the services
With DLC it will look like this:
- Alice uploads files to pixeldrain, gofile, etc.
- Alice compiles/encodes urls in a single DLC-file
- Alice posts the DLC-file to the thread
- Bob puts DLC-file into JDownloader
- JDownloader automatically selects available services and downloads files
- Chuck now have to manually extract urls from DLC-file
- Chuck also have to takedown all of the urls to prevent sharing of the content
Do I get it right?
It seems more resilient compared to "raw" base64-encoded urls at the price of losing transparency. By "transparency" I mean that now I have many options to choose from (download using browser or some other tools), but DLC is tied only to JDownloader.
I've noticed that the new update brought us DLC feature and some people are pretty familiar with it (according to discussions in the MMD-thread) while others (including me) are not. Not gonna ask questions like "what is it" and "how do i use it" (I did some research after all), but rather "what is the intended usage" and "how is overall experience".
Suppose Alice wants to share some files in the thread, Bob wants to download them and Chuck is the rightful owner of these files armed with DMCA-hammer.
Without DLC the scenario goes like this:
- Alice uploads files to pixeldrain, gofile, etc.
- Alice posts message like:
Q2h1Y2s2OQo='s new content:
pixeldrain: aHR0cHM6Ly9waXhlbGRyYWluLmNvbS9sL0V4QW1QbGUK
gofile: aHR0cHM6Ly9nb3lpbWZpbGUuaW8vZC9zSWtFCg==
- (optional) Bob asks how to decode these things for the nth time per month
- Bob decodes url to the service of his choice
- Bob manually downloads files from the url or put it into some downloader (JDownloader, gallery-dl, curl, wget, etc.)
- Chuck opens anime-sharing.com, searches for posts containing "Chuck69", "Q2h1Y2s2OQo=", "Y2h1Y2s2OQo=", ⒸⒽⒽⒸⒽ⑥⑨
- Chuck follows the steps of Bob
- Chuck sends takedown notices to the services
With DLC it will look like this:
- Alice uploads files to pixeldrain, gofile, etc.
- Alice compiles/encodes urls in a single DLC-file
- Alice posts the DLC-file to the thread
- Bob puts DLC-file into JDownloader
- JDownloader automatically selects available services and downloads files
- Chuck now have to manually extract urls from DLC-file
- Chuck also have to takedown all of the urls to prevent sharing of the content
Do I get it right?
It seems more resilient compared to "raw" base64-encoded urls at the price of losing transparency. By "transparency" I mean that now I have many options to choose from (download using browser or some other tools), but DLC is tied only to JDownloader.