Home

#!/usr/local/bin/bash

git tag -d $(git tag -l)
BRANCH=`git rev-parse --abbrev-ref HEAD`
if [ "$BRANCH" != "*patches" ]; then
  printf "%s" "Continue? (Y/N): "
  read confirm && [[ $confirm == [yY] || $confirm == [yY][eE][sS] ]] || exit 1
fi
rm -fr ".git/rebase-apply"
rm -fr ".git/rebase-merge"
git clean -f -e '*.*' -e '!*.orig'
git remote update
git tag -d $(git tag -l)
git checkout patches
printf "%s" "Reset? (Y/N): "
read restore && [[ $restore == [nN] || $restore == [nN][oO] ]] || git reset --hard origin/patches
git rebase upstream/main
if [ $(git ls-files -u | wc -l) -gt 0 ] ; then
  exit
fi

git checkout main
git reset --hard upstream/main
git submodule update --init --recursive
git rebase patches
if [ $(git ls-files -u | wc -l) -eq 0 ] ; then
  ./gradlew --write-verification-metadata sha256 clean --rerun-tasks
  git push -f
else
  git rebase --abort
  git clean -f -e '*.*' -e '!*.orig'
fi
git checkout patches

• Signal, like most open-source projects, is funded by public donation. Such projects are typically released in an "as-is" condition, but place higher priority on critical bugs. It is a common practice to establish core functionality before focus shifts to rallying funds. Projects aimed primarily at revenue seek investors or release paid products.

• Signal, unlike most open-source projects, has shown a history of dedicating significant resources to testing and (over)engineering donation banners. Core feature issues, such as the numerous reported problems with backup, are deferred to alleged internal discussions that yield no improvement. These issues remain unresolved.

• The most significant contributor to the inefficiency of both the application and the team maintaining it appears to be an endless string of callbacks and nested packages with no clear purpose beyond minute classification of methods and self-imposed warnings that allude to future intentions without a clear roadmap for implementation.

This fork is an attempt to mitigate some of the frustration.