Suggestion to short mediaflow proxy label #487

New issue

Closed

opened 2025-11-06 16:43:52 +00:00 by GLlgGL · 6 comments

GLlgGL commented

2025-11-06 16:43:52 +00:00

(Migrated from github.com)

To be able to show the source name on result you should short the mediaflow proxy name

For ex.

VOE(via Mediaflow Proxy)

VOE(MFP)

In this way the source at the end will easily seen on any type of device.

Hi To be able to show the source name on result you should short the mediaflow proxy name For ex. VOE(via Mediaflow Proxy) to VOE(MFP) In this way the source at the end will easily seen on any type of device. ![image](https://github.com/user-attachments/assets/747a8a10-15e2-41f0-9a10-9cc23f19752a)

👍 1

webstreamr commented

2025-11-06 22:56:58 +00:00

(Migrated from github.com)

I'm OK with adapting all of this in a single PR. But tests and fixtures need updates too. You'd need to make yourself comfortable with running tests and updating them as well or wait.

GLlgGL commented

2025-11-07 06:42:54 +00:00

(Migrated from github.com)

I don't know how to do them lol 😳

Learn me or I will wait no problem...

I don't know how to do them lol 😳 Learn me or I will wait no problem...

webstreamr commented

2025-11-07 07:29:10 +00:00

(Migrated from github.com)

No worries. You can update all code pieces (maybe use " (MFP)" so that we get e.g. "VOE (MFP)") and then you run npm run test -- -u. That might be it already

No worries. You can update all code pieces (maybe use " (MFP)" so that we get e.g. "VOE (MFP)") and then you run `npm run test -- -u`. That might be it already

webstreamr commented

2025-11-07 08:26:50 +00:00

(Migrated from github.com)

Oh and also fix failing tests in case there are some. Until the above command finishes cleanly :) you can do it! 😊 I'll merge then

GLlgGL commented

2025-11-07 09:09:30 +00:00

(Migrated from github.com)

I will try to do as I am using Vercel and not locally testing and Vercel is limited on how many builds you can run...

I have my raspberrypi by I don't want to mess with it anyway I think I can use it because I have (open media vault) installed and has docker composer. I also use it for mediaflow proxy...

What I want to learn and what we have to focus is more on bringing as much extractors as we can because adding new sources after it's easy...There are good websites that uses only VidMoly and Waaw, or only VK and VidGuard. Especially Animation and anime websites but not only...

So the idea is how to properly test or troubleshout an extractor to see whats wrong with it...

For example if you see the issues opened for vidmoly or vk...

I will try to do as I am using Vercel and not locally testing and Vercel is limited on how many builds you can run... I have my raspberrypi by I don't want to mess with it anyway I think I can use it because I have (open media vault) installed and has docker composer. I also use it for mediaflow proxy... What I want to learn and what we have to focus is more on bringing as much extractors as we can because adding new sources after it's easy...There are good websites that uses only VidMoly and Waaw, or only VK and VidGuard. Especially Animation and anime websites but not only... So the idea is how to properly test or troubleshout an extractor to see whats wrong with it... For example if you see the issues opened for vidmoly or vk...

webstreamr commented

2025-11-29 13:19:35 +00:00

(Migrated from github.com)

adapted in 4cd1e09466

adapted in 4cd1e09466a69e27923207a7edb1fd77004e902a