RIP Big 3: FMovies, DramaCool, GogoAnime/Anitaku #917

Merged
krysanify merged 7 commits from dead into main 2025-04-17 20:34:25 -05:00
krysanify commented 2025-04-16 22:19:14 -05:00 (Migrated from github.com)

Closes #907
Closes #610
Closes #507
Closes #458
Closes #399
Closes #335

DramaCool

Official shutdown announcement: https://xcancel.com/dramacoolcom/status/1861628424147869919

FMovies

Forced to shutdown: https://torrentfreak.com/fmovies-piracy-ring-was-shut-down-by-vietnam-assisted-by-ace-240829/
Owner/operator prosecuted: https://torrentfreak.com/fmovies-piracy-mastermind-confesses-authorities-confirm-prosecution-241113/

GogoAnime/Anitaku

None of their official sites are working and their one & only video hosting server have been down for months.
As there's no official shutdown notice, will be marked as Inactive until further notice.

Checklist:

  • Updated extVersionCode value in build.gradle for individual extensions
  • Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
  • Referenced all related issues in the PR body (e.g. "Closes #xyz")
  • Added the isNsfw = true flag in build.gradle when appropriate
  • Have not changed source names
  • Have explicitly kept the id if a source's name or language were changed
  • Have tested the modifications by compiling and running the extension through Android Studio
  • Have removed web_hi_res_512.png when adding a new extension
  • Have made sure all the icons are in png format
Closes #907 Closes #610 Closes #507 Closes #458 Closes #399 Closes #335 ### DramaCool Official shutdown announcement: https://xcancel.com/dramacoolcom/status/1861628424147869919 ### FMovies Forced to shutdown: https://torrentfreak.com/fmovies-piracy-ring-was-shut-down-by-vietnam-assisted-by-ace-240829/ Owner/operator prosecuted: https://torrentfreak.com/fmovies-piracy-mastermind-confesses-authorities-confirm-prosecution-241113/ ### GogoAnime/Anitaku None of their official sites are working and their one & only video hosting server have been down for months. ~~As there's no official shutdown notice, will be marked as Inactive until further notice.~~ Checklist: - [ ] Updated `extVersionCode` value in `build.gradle` for individual extensions - [ ] Updated `overrideVersionCode` or `baseVersionCode` as needed for all multisrc extensions - [x] Referenced all related issues in the PR body (e.g. "Closes #xyz") - [ ] Added the `isNsfw = true` flag in `build.gradle` when appropriate - [x] Have not changed source names - [ ] Have explicitly kept the `id` if a source's name or language were changed - [ ] Have tested the modifications by compiling and running the extension through Android Studio - [ ] Have removed `web_hi_res_512.png` when adding a new extension - [ ] Have made sure all the icons are in png format
Arkai1 commented 2025-04-17 03:51:54 -05:00 (Migrated from github.com)

Don't remove gogo as there is no official announcement made on the server

Don't remove gogo as there is no official announcement made on the server
GregiPlays commented 2025-04-17 03:58:56 -05:00 (Migrated from github.com)

I mean, do we expect it coming back? I'm fine with either tbh to either leave it there or remove it.

I mean, do we expect it coming back? I'm fine with either tbh to either leave it there or remove it.
krysanify commented 2025-04-17 04:19:10 -05:00 (Migrated from github.com)

I hesitated to remove it too at first, but then I thought if new users to the repo install it and see that it's broken, they would submit an issue (without searching, like has been happening again and again). By removing it, at least only old users would complain.

New users would not know it exists in the first place, though they might request it to be added...

I hesitated to remove it too at first, but then I thought if new users to the repo install it and see that it's broken, they would submit an issue (without searching, like has been happening again and again). By removing it, at least only old users would complain. New users would not know it exists in the first place, though they might request it to be added...
Arkai1 commented 2025-04-17 04:20:42 -05:00 (Migrated from github.com)

I hesitated to remove it too at first, but then I thought if new users to the repo install it and see that it's broken, they would submit an issue (without searching, like has been happening again and again). By removing it, at least only old users would complain.

New users would not know it exists in the first place, though they might request it to be added...

That is true but there are also some people who will make source request for it so removing it will not solve the issue creating problem

> I hesitated to remove it too at first, but then I thought if new users to the repo install it and see that it's broken, they would submit an issue (without searching, like has been happening again and again). By removing it, at least only old users would complain. > > New users would not know it exists in the first place, though they might request it to be added... That is true but there are also some people who will make source request for it so removing it will not solve the issue creating problem
krysanify commented 2025-04-17 04:25:15 -05:00 (Migrated from github.com)

It may reduce it, new users would need to know that they can make a request, know where to make a request and create github account for it.

I'm hoping most of them would settle with other extensions that are already available before they start asking for it.

It may reduce it, new users would need to know that they can make a request, know where to make a request and create github account for it. I'm hoping most of them would settle with other extensions that are already available before they start asking for it.
krysanify commented 2025-04-17 04:33:13 -05:00 (Migrated from github.com)

Of course, to leave it be or remove it, I will comply to whatever final decision made by the maintainers.

Of course, to leave it be or remove it, I will comply to whatever final decision made by the maintainers.
Arkai1 commented 2025-04-17 04:47:07 -05:00 (Migrated from github.com)

Of course, to leave it be or remove it, I will comply to whatever final decision made by the maintainers.

How about writing Broken with the name of Gogoanime like Gogoanime (Broken)

> Of course, to leave it be or remove it, I will comply to whatever final decision made by the maintainers. How about writing Broken with the name of Gogoanime like Gogoanime (Broken)
krysanify commented 2025-04-17 05:05:12 -05:00 (Migrated from github.com)

How about writing Broken with the name of Gogoanime like Gogoanime (Broken)

That might work, but Broken implies it need fixing. How about On Hiatus (to borrow from manga terms) or Inactive?

> How about writing Broken with the name of Gogoanime like Gogoanime (Broken) That might work, but Broken implies it need fixing. How about On Hiatus (to borrow from manga terms) or Inactive?
Arkai1 commented 2025-04-17 05:22:47 -05:00 (Migrated from github.com)

How about writing Broken with the name of Gogoanime like Gogoanime (Broken)

That might work, but Broken implies it need fixing. How about On Hiatus (to borrow from manga terms) or Inactive?

Inactive would be better

> > How about writing Broken with the name of Gogoanime like Gogoanime (Broken) > > That might work, but Broken implies it need fixing. How about On Hiatus (to borrow from manga terms) or Inactive? Inactive would be better
krysanify commented 2025-04-17 06:34:59 -05:00 (Migrated from github.com)

Added Inactive status to extension name, also notice message when user tries to load popular or latest page:

Inactive notice

Added Inactive status to extension name, also notice message when user tries to load popular or latest page: ![Inactive notice](https://github.com/user-attachments/assets/07bd8c8c-ea27-45d5-8b5a-6ebf49bc358d)
Arkai1 commented 2025-04-17 06:39:43 -05:00 (Migrated from github.com)

Added Inactive status to extension name, also notice message when user tries to load popular or latest page:

Inactive notice

Great work man 👏👍

> Added Inactive status to extension name, also notice message when user tries to load popular or latest page: > > ![Inactive notice](https://private-user-images.githubusercontent.com/3841921/434776621-07bd8c8c-ea27-45d5-8b5a-6ebf49bc358d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDQ4OTAyNDAsIm5iZiI6MTc0NDg4OTk0MCwicGF0aCI6Ii8zODQxOTIxLzQzNDc3NjYyMS0wN2JkOGM4Yy1lYTI3LTQ1ZDUtOGI1YS02ZWJmNDliYzM1OGQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDQxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTA0MTdUMTEzOTAwWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZDNlZGEwMDgwMzg2NGIwYTJiOTg3Njg2MjIwNDY5OWQxY2IzOTc0OWYyMzg4OWE2YjcxMGQxZGI3M2ZlMjU5MCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.EllmE6kZAct-AQsysQE7S0ZJEfYD5_NTqvADzCdpsN0) Great work man 👏👍
itsmechinmoy commented 2025-04-17 07:08:30 -05:00 (Migrated from github.com)

Added Inactive status to extension name, also notice message when user tries to load popular or latest page:

Inactive notice

Would be better if you also add "Be aware of fake/clone sites" so that they don't make new issues again and again

> Added Inactive status to extension name, also notice message when user tries to load popular or latest page: > > ![Inactive notice](https://private-user-images.githubusercontent.com/3841921/434776621-07bd8c8c-ea27-45d5-8b5a-6ebf49bc358d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDQ4OTE5MTUsIm5iZiI6MTc0NDg5MTYxNSwicGF0aCI6Ii8zODQxOTIxLzQzNDc3NjYyMS0wN2JkOGM4Yy1lYTI3LTQ1ZDUtOGI1YS02ZWJmNDliYzM1OGQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDQxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTA0MTdUMTIwNjU1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NzAxZDQ1NWNjNjAwNDI3OTY0MTE0NjRhZDY2OTRhYTlhZGQyNWZkNmU4ZmMwM2VhYTI2NjU5ODg5OWZlMjA5YyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.KlF_-BwmuEumc4N7E2BwpcY21bMhHyCvJnF9JDnR8EM) Would be better if you also add "Be aware of fake/clone sites" so that they don't make new issues again and again
krysanify commented 2025-04-17 07:42:58 -05:00 (Migrated from github.com)

idk man, the past few months since I started being active observing this project have lowered my expectations on people's ability to read and comprehend long text.

that official dramacool announcement? someone literally replied it's a lie because the fakes exists: https://xcancel.com/jjuu11een/status/1861729536036962558

I doubt warning such person about fakes would get through their numb skulls, maybe let's try this first?

idk man, the past few months since I started being active observing this project have lowered my expectations on people's ability to read and comprehend long text. that official dramacool announcement? someone literally replied it's a lie because the fakes exists: https://xcancel.com/jjuu11een/status/1861729536036962558 I doubt warning such person about fakes would get through their numb skulls, maybe let's try this first?
JosefFStraka commented 2025-04-17 07:54:48 -05:00 (Migrated from github.com)

I think removing it altogether is better.

I think removing it altogether is better.
krysanify commented 2025-04-17 08:09:08 -05:00 (Migrated from github.com)
  • gregi & me: either is fine
  • arkai & chinmoy: mark as inactive
  • josef: remove as obsolete

i guess final say is up to hak now?

* gregi & me: either is fine * arkai & chinmoy: mark as inactive * josef: remove as obsolete i guess final say is up to hak now?
itsmechinmoy commented 2025-04-17 08:31:35 -05:00 (Migrated from github.com)
  • gregi & me: either is fine
  • arkai & chinmoy: mark as inactive
  • josef: remove as obsolete

i guess final say is up to hak now?

I’m choosing option 1 because there’s still a chance they might come back or rebrand. If they do, the site structure will likely stay the same, making it easier for maintainers to work on

> * gregi & me: either is fine > * arkai & chinmoy: mark as inactive > * josef: remove as obsolete > > i guess final say is up to hak now? I’m choosing option 1 because there’s still a chance they might come back or rebrand. If they do, the site structure will likely stay the same, making it easier for maintainers to work on
almightyhak commented 2025-04-17 19:27:39 -05:00 (Migrated from github.com)

Removing it entirely is best, and if it does come back, the code for it isn't entirely gone the git history will still be there

Removing it entirely is best, and if it does come back, the code for it isn't entirely gone the git history will still be there
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AlmightyHak/extensions-source#917
No description provided.