Remove ffwa (Firefox WebApp) support (#2398)

* Delete programs/x86_64/ffwa-gmail

* Delete programs/x86_64/ffwa-github

* Delete programs/x86_64/ffwa-reddit

* Delete programs/x86_64/ffwa-netflix

* Delete programs/x86_64/ffwa-twitter

* Delete programs/x86_64/ffwa-youtube

* Delete programs/x86_64/ffwa-facebook

* Delete programs/x86_64/ffwa-whatsapp

* Delete programs/x86_64/ffwa-wikipedia

* Delete templates/AM-SAMPLE-Firefox-webapp

* Remove ffwa (Firefox WebApp) support

* Update lister.sh

* Update sources-selector.sh

* Update am2pla-site

* Update README.md

* Update template.md

* Update template.md

* Update template.md

* Update template.md

Author: ivan-hc

APP-MANAGER

@@ -1153,8 +1153,6 @@ _check_version() {
 					_check_version_if_version_file_exists
 				elif [ "$arg" = "$AMCLI" ]; then
 					APPVERSION="$AMVERSION"
-				elif echo "$arg" | grep -q "ffwa-"; then
-					APPVERSION="WebApp"
 				elif grep -q "usr/local/lib" "$argpath"/remove 2>/dev/null; then
 					_check_version_if_library
 				elif [ -f "$argpath"/updater ] || grep -qi "version=" "$argpath"/*; then

README.md

@@ -325,8 +325,7 @@ To change locations, remove local apps, and reinstall in the new location, see t
 
 1. **PORTABLE PROGRAMS** from official sources (see Firefox, Thunderbird, NodeJS, Platform Tools...), extracted from official .deb/tar/zip packages.
 2. **APPIMAGES**, from both official and unofficial sources (I also create unofficial AppImages), or compiled on-the-fly with [pkg2appimage](https://github.com/AppImage/pkg2appimage) and [appimagetool](https://github.com/AppImage/AppImageKit), like an AUR helper, from official archives.
-3. **FIREFOX PROFILES** to run as webapps, the ones with suffix "ffwa-" in the apps list.
-4. **THIRD-PARTY LIBRARIES** if they are missing in your repositories.
+3. **THIRD-PARTY LIBRARIES** if they are missing in your repositories.
 
 The database aims to be a reference point where you can download all the AppImage packages scattered around the web, otherwise unobtainable, as you would expect from any package manager, through specific installation scripts for each application, as happens with the AUR PKGBUILDs, on Arch Linux. You can see all of them [here](https://github.com/ivan-hc/AM/tree/main/programs), divided by architecture.
 
@@ -1052,7 +1051,6 @@ Below you can access the documentation pages related to the use of "AM", complet
   - [Option Zero: "AppImages"](docs/guides-and-tutorials/template.md#option-zero-appimages)
   - [Option One: "build AppImages on-the-fly"](docs/guides-and-tutorials/template.md#option-one-build-appimages-on-the-fly)
   - [Option Two: "Archives and other programs"](docs/guides-and-tutorials/template.md#option-two-archives-and-other-programs)
-  - [Option Three: "Firefox profiles"](docs/guides-and-tutorials/template.md#option-three-firefox-profiles)
   - [How an installation script works](docs/guides-and-tutorials/template.md#how-an-installation-script-works)
   - [How to test an installation script](docs/guides-and-tutorials/template.md#how-to-test-an-installation-script)
   - [How to submit a Pull Request](docs/guides-and-tutorials/template.md#how-to-submit-a-pull-request)

docs/guides-and-tutorials/template.md

@@ -10,10 +10,9 @@ This is a step-by-step guide on how to create, understand and test installation
 - [Option Zero: "**AppImages**"](#option-zero-appimages)
   - [If the AppImage is hosted on github or codeberg](#if-the-appimage-is-hosted-on-github-or-codeberg)
   - [If the AppImage is hosted sourceforge](#if-the-appimage-is-hosted-sourceforge)
-  - [If the AppImage is hosted on other sistes](#if-the-appimage-is-hosted-on-other-sistes)
+  - [If the AppImage is hosted on other sites](#if-the-appimage-is-hosted-on-other-sites)
 - [Option One: "**build AppImages on-the-fly**"](#option-one-build-appimages-on-the-fly)
 - [Option Two: "**Archives and other programs**"](#option-two-archives-and-other-programs)
-- [Option Three: "**Firefox profiles**"](#option-three-firefox-profiles)
 
 [How an installation script works](#how-an-installation-script-works)
 
@@ -35,16 +34,17 @@ appman -t $PROGRAM
 ```
 and this is the screen that will appear:
 
-![Istantanea_2024-06-17_21-35-26 png](https://github.com/ivan-hc/AM/assets/88724353/6e11aeff-9a70-44f7-bd73-1324b545704e)
+![Istantanea_2024-06-17_21-35-26 png](https://github.com/user-attachments/assets/81fe12aa-d90c-4707-bb48-bcd0a661c287)
 
 Each option corresponds to a different type of application or helper to target with an installation script:
 
 0. For **AppImages**, [press "0" (zero)](#option-zero-appimages)
 1. To **create an AppImage on the fly** using [appimagetool](https://github.com/AppImage/AppImageKit) and [pkg2appimage](https://github.com/AppImage/pkg2appimage), [press "1" (one)](#option-one-build-appimages-on-the-fly)
 2. For a **portable program** (archive, binary, script...), [press "2" (two)](#option-two-archives-and-other-programs)
-3. For a **custom Firefox profile**, [press "3" (three)](#option-three-firefox-profiles)
 
-**The next four paragraphs will explain in detail how to use the options [0](#option-zero-appimages), [1](#option-one-build-appimages-on-the-fly), [2](#option-two-archives-and-other-programs) and [3](#option-three-firefox-profiles).**
+*NOTE: In the past, the `-t` option included many more template choices, **including creating profiles for Firefox, with the "ffwa" suffix**. These have been deprecated over time, partly due to lack of interest, incompatibility with other shell functions (oriented towards actual apps), Firefox forks or its variants, and changes to Firefox itself. You'll likely see references to them in upcoming videos, but **as of May 2026, only the three options listed above are available.***
+
+**The next paragraphs will explain in detail how to use the options [0](#option-zero-appimages), [1](#option-one-build-appimages-on-the-fly) and [2](#option-two-archives-and-other-programs).**
 
 ------------------------------------------------------------------------
 
@@ -99,7 +99,7 @@ https://github.com/user-attachments/assets/c1c08c93-3a57-45b9-9515-551555eca3c4
 
 NOTE, if the URL does not always appear. In that case, you need to resort to more "drastic" methods. See below.
 
-### If the AppImage is hosted on other sistes
+### If the AppImage is hosted on other sites
 For AppImages published elsewhere, you will need more advanced knowledge of how to find the latest download URL using `curl` and `wget` (preferably the former), as well as knowledge of how to use `sed`, `grep`, and `tr`. Again, you may choose to use repology.org to determine the version if it is not present in the download URL.
 
 When downloading an installation script using the command `am -d $program` you will notice in most cases a variable "`$version`", which represents the URL for downloading the application.
@@ -259,29 +259,6 @@ If in doubt, download the pre-existing installation scripts and analyze their co
 | [Back to "Templates index"](#templates-index) |
 | - |
 
-------------------------------------------------------------------------
-## Option Three: "Firefox profiles"
-Option 3 creates a launcher that opens Firefox in a custom profile and on a specific page, such as in a WebApp. I created this option to counterbalance the amount of Electron/Chrome-based applications (and because I'm a firm Firefox's supporter).
-
-It is enough to give an AppName, a URL to the icon (a correct one, not like the one suggested in the video, down below) and a category.
-
-Here is an example for "ProtonMail"
-
-https://github.com/user-attachments/assets/120012de-777f-4cd0-8324-f761d8d4947a
-
-In practice, all we need to do is create a custom Firefox profile that can be launched from a .desktop file, which is all we are really creating in this process.
-
-**These "objects" are not even classified as applications**, and **therefore are not included in the application count when you run `am -l`**.
-
-As suggested in the video, it is preferable to have these custom profiles for yourself.
-
-Their advantage is to keep the data of the reference site well separated from the system profile used in Firefox.
-
-------------------------------------------------------------------------
-
-| [Back to "Templates index"](#templates-index) |
-| - |
-
 ------------------------------------------------------------------------
 ## How an installation script works
 The structure of an installation script is designed for a system-wide installation (as root), since it is intended to be hosted in this database. But every path indicated within it is written so that "`appman -i`" or "`am -i --user`" can patch the essential parts, to hijack the installation at a local level and without root privileges.

modules/database.am

@@ -246,9 +246,7 @@ _files_if_binary() {
 }
 
 _files_if_script() {
-	if grep "/ffwa" "${LINK:-$FILE}" >/dev/null 2>&1; then
-		echo " ◆ $arg	|	launcher" >> "$AMCACHEDIR"/files-type
-	elif grep '#!.*bash' "${LINK:-$FILE}" >/dev/null 2>&1; then
+	if grep '#!.*bash' "${LINK:-$FILE}" >/dev/null 2>&1; then
 		echo $" ◆ $arg	|	bash-script" >> "$AMCACHEDIR"/files-type
 	elif grep '#!.*dash' "${LINK:-$FILE}" >/dev/null 2>&1; then
 		echo $" ◆ $arg	|	dash-script" >> "$AMCACHEDIR"/files-type
@@ -744,7 +742,7 @@ _list() {
 	fi
 	APPSNUMBER=$((ITEMSNUMBER - LIBNUMBER))
 	# Determine the number of available apps from the list
-	AVAILABLE_APPS_NUMBER=$(grep -v "ffwa-\|\"kdegames\"\|\"kdeutils\"\|\"node\"\|\"platform-tools\"" "$AMDATADIR/$ARCH-apps" | grep -e "^◆.*$" -c)
+	AVAILABLE_APPS_NUMBER=$(grep -v "\"kdegames\"\|\"kdeutils\"\|\"node\"\|\"platform-tools\"" "$AMDATADIR/$ARCH-apps" | grep -e "^◆.*$" -c)
 	if ! test -f "$AMDATADIR/$ARCH-appimages"; then
 		_online_check
 		_sync_appimages_list

modules/install.am

@@ -78,16 +78,6 @@ _check_if_optional_dependences_are_needed() {
 		_check_argument
 		return 1
 	fi
-	# Determine if this script installs a Firefox webapp
-	if grep -q 'ffwa-' ./"$arg"; then
-		ffbrowser=$(find ${PATH//:/ } -maxdepth 1 -name "firefox*" | sort | head -1)
-		if [ -z "$ffbrowser" ]; then
-			echo $" 💀 ERROR: you cannot install \"$arg\" without installing \"firefox\""
-			return 1
-		else
-			sed -i 's#firefox --class#'"$(echo "$ffbrowser" | xargs -L 1 basename)"' --class#g' ./"$arg"
-		fi
-	fi
 }
 
 _check_if_script_installs_a_metapackage() {

modules/template.am

@@ -57,8 +57,6 @@ _template_create_dirs_and_ask_for_source() {
 		_use_online_downloader "$AMREPO"/templates/AM-SAMPLE-portable2appimage ./am-scripts/"$MAIN_ARCH"/"$arg"
 	elif [ "$templatetype" = 2 ]; then
 		_use_online_downloader "$AMREPO"/templates/AM-SAMPLE-Archive ./am-scripts/"$MAIN_ARCH"/"$arg"
-	elif [ "$templatetype" = 3 ]; then
-		_use_online_downloader "$AMREPO"/templates/AM-SAMPLE-Firefox-webapp ./am-scripts/"$MAIN_ARCH"/"$arg"
 	fi
 	sed -i "s/SAMPLE/$arg/g" ./am-scripts/"$MAIN_ARCH"/"$arg"
 	echo "$DIVIDING_LINE"
@@ -433,7 +431,6 @@ for arg in $ARGS; do
 		echo $"  0) APPIMAGE, FROM ANY WEBSITE (BETTER IF FROM GITHUB.COM)"
 		echo $"  1) APPIMAGE ON-THE-FLY, USING A DEDICATED SCRIPT"
 		echo $"  2) ANY ARCHIVE/BINARY/SCRIPT FROM ANY WEBSITE"
-		echo $"  3) WEBAPP BASED ON A FIREFOX PROFILE (REQUIRES \"FIREFOX\" IN \$PATH)"
 		echo ""
 		read -r -p $" WHAT KIND OF PROGRAM DO YOU WANT TO WRITE A SCRIPT FOR? : " templatetype
 		case "$templatetype" in
@@ -529,43 +526,6 @@ for arg in $ARGS; do
 			echo -e $"\n All files are saved in $SCRIPTDIR/am-scripts\n"
 			;;
 
-		'3') # CREATE A CUSTOM FIREFOX PROFILE ("firefox" MUST BE IN "$PATH" TO MADE IT WORK)
-
-			_template_create_dirs_and_ask_for_source
-
-			# USE THE SUFFIX FROM NOW ON
-			mv ./am-scripts/"$MAIN_ARCH"/"$arg" ./am-scripts/"$MAIN_ARCH"/"ffwa-$arg"
-			arg="ffwa-$arg"
-			echo "$DIVIDING_LINE"
-			read -r -ep $" ◆ NAME OF THE APP: " RESPONSE
-			case "$RESPONSE" in
-			*)
-				sed -i "s#GIVEMEANAME#$RESPONSE#g" ./am-scripts/"$MAIN_ARCH"/"$arg"
-				# CREATE A NEW LINE FOR THE APPLICATION'S LIST
-				echo "◆ $arg : WebApp & Firefox Profile for $RESPONSE." >> ./am-scripts/list
-			esac
-			# PUT THE APP INTO A CATEGORY, THIS IS NEEDED FOR OUR CUSTOM DESKTOP FILE
-			_template_desktop_file_select_category
-			# ENTER THE URL OF THE SITE YOU WANT TO CREATE A CUSTOM FIREFOX PROFILE FOR
-			read -r -ep $" ◆ URL OF THE WEBAPP: " RESPONSE
-			case "$RESPONSE" in
-			*)
-				sed -i "s#MYWEBSITE#$RESPONSE#g" ./am-scripts/"$MAIN_ARCH"/"$arg"
-				;;
-			esac
-			echo "$DIVIDING_LINE"
-			# ENTER THE URL OF THE ICON THAT WILL APPEAR IN THE MENU
-			read -r -ep $" ◆ COPY/PASTE THE URL OF THE ICON HERE $(echo -e '\n URL: ')" RESPONSE
-			case "$RESPONSE" in
-			*)
-				sed -i "s#YOURICONURL#$RESPONSE#g" ./am-scripts/"$MAIN_ARCH"/"$arg"
-				;;
-			esac
-			echo "$DIVIDING_LINE"
-			# END OF THIS FUNCTION
-			echo -e $"\n All files are saved in $SCRIPTDIR/am-scripts\n"
-			;;
-
 		# NOTHING SELECTED
 		*)
 			echo -e $"\n No valid argument was chosen: process aborted! \n" | tr '[:lower:]' '[:upper:]'; break

programs/lister.sh

@@ -12,7 +12,7 @@ for arch in $DIRS; do
 					grep "◆ $arg :" "$arch-apps" | head -1 >> "$arch-appimages"
 				fi
 			else
-				if ! grep "◆ $arg :" "$arch-apps" | grep -ie "\"node\"\|\"platform-tools\"\|^◆ ffwa-" 1>/dev/null; then
+				if ! grep "◆ $arg :" "$arch-apps" | grep -ie "\"node\"\|\"platform-tools\"" 1>/dev/null; then
 					grep "◆ $arg :" "$arch-apps" | head -1 >> "$arch-portable"
 				fi
 			fi