Arch Linux User Repository

Hi, how about installing nitter.conf in /etc/nitter/ instead of under /etc directly in order not to litter /etc directory by following Web application package guidelines?

Moved back to the original repository, this time on a unmerged PR.

Requires manual intervention to get guest accounts, see: https://github.com/zedeus/nitter/pull/985#issuecomment-1690758660

This will all be integrated in the future I think, so don't get too attached. I pushed some changes to properly create all files with the right permissions, and I'm dogfooding it myself, but there might be borkage.

The main case is /etc/nitter/guest_accounts.json being empty, the JSON parser will probably choke and give a weird error. Check that link above for solving it.

In case anyone wants to help take care of all this babysitting Musk's baby, let me know and I will give you co-maintainer status.

Moved back again to PrivacyDevel's fork, now that Twitter seems to be blocking any anonymous access.

Can move back once the "guest accounts" situation is clarified, see https://github.com/zedeus/nitter/pull/985.

@climbTheStairs The package was originally my personal config, that's why the default configuration had weird values. I agree that upstream patches should remain at a minimum, integrated your new patch.

Most of the changes in config.patch seem to be unnecessary or redundant (adding # Change this? everywhere, removing or replacing informative comments, and changing default settings such as port, address, theme, and base64Media for no clear reason), and I believe that the default base64Media setting should not be changed to false, since the only reason it should be used is if there's a network or proxy problem that breaks with URL-encoded media URLs (https://github.com/zedeus/nitter/issues/971); otherwise, it does nothing but obfuscates URLs.

I think it would make sense to reduce config.patch to only changing staticDir:

diff --git a/nitter.conf b/nitter.conf
index 0d4deb7..881be3d 100644
--- a/nitter.conf
+++ b/nitter.conf
@@ -5,7 +5,7 @@ address = "0.0.0.0"
 port = 8080
 https = false  # disable to enable cookies when not using https
 httpMaxConnections = 100
-staticDir = "./public"
+staticDir = "/usr/share/nitter/public"

 [Cache]
 listMinutes = 240  # how long to cache list info (not the tweets, so keep it high)

@kescherAUR Indeed, rebuilt and confirmed it's working again.

Thanks for the heads up, updated the package. If there's any issue I can easily revert back to the old version, and the repository history is available, the fork commit is this:

https://aur.archlinux.org/cgit/aur.git/tree/?h=nitter-git&id=14797b8912d68188d985884808adbf0d289983dc

@somini please move back to upstream - Nitter works again now, without requiring an account on the accursed platform.

@hashworks Thanks, included that change now.

I also moved to this fork that should fix the new Login requirement shenanigans.

https://github.com/PrivacyDevel/nitter

Build fails:

  Compiling tools/rendermd (from package nitter) using c backend
could not load: libpcre.so(.3|.1|)
(compile with -d:nimDebugDlOpen for more information)
Error: execution of an external program failed: '/build/nitter-git/src/nitter-git/tools/rendermd '
       Tip: 37 messages have been suppressed, use --verbose to show them.
     Error: Execution failed with exit code 1
        ... Command: /usr/bin/nim c --noNimblePath -d:NimblePkgVersion=0.1.0 --path:'/build/.nimble/pkgs/jester-#baca3f' --path:/build/.nimble/pkgs/httpbeast-0.4.1 --path:'/build/.nimble/pkgs/asynctools-#0e6bdc3ed5bae8c7cc9' --path:'/build/.nimble/pkgs/asynctools-#pr_fix_compilation' --path:'/build/.nimble/pkgs/karax-#5cf360c' --path:/build/.nimble/pkgs/ws-0.5.0 --path:/build/.nimble/pkgs/dotenv-2.0.1 --path:'/build/.nimble/pkgs/sass-#7dfdd03' --path:'/build/.nimble/pkgs/nimcrypto-#4014ef9' --path:'/build/.nimble/pkgs/markdown-#158efe3' --path:'/build/.nimble/pkgs/packedjson-#9e6fbb6' --path:'/build/.nimble/pkgs/supersnappy-#6c94198' --path:'/build/.nimble/pkgs/redpool-#8b7c1db' --path:'/build/.nimble/pkgs/redis-#d0a0e6f' --path:'/build/.nimble/pkgs/redis-#d0a0e6f' --path:'/build/.nimble/pkgs/zippy-#ca5989a' --path:'/build/.nimble/pkgs/flatty-#e668085' --path:'/build/.nimble/pkgs/jsony-#ea811be' --hints:off '--hint[Processing]:off' -d:danger -r tools/rendermd
stack trace: (most recent call last)
/tmp/nimblecache-1482698451/nimscriptapi_400225858.nim(187, 16)
/build/nitter-git/src/nitter-git/nitter.nimble(34, 8) mdTask
/usr/lib/nim/system/nimscript.nim(273, 7) exec
/usr/lib/nim/system/nimscript.nim(273, 7) Error: unhandled exception: FAILED: nimble c --hint[Processing]:off -d:danger -r tools/rendermd [OSError]
     Error: Exception raised during nimble script execution
==> ERROR: A failure occurred in build().

Adding pcre to the makedepends fixes this.

Prepare fails ATM:

==> Starting prepare()...
renamed 'nitter.example.conf' -> 'nitter.conf'
patching file nitter.conf
Hunk #1 FAILED at 1.
Hunk #2 succeeded at 20 with fuzz 2.
Hunk #3 succeeded at 35 (offset 1 line).
1 out of 3 hunks FAILED -- saving rejects to file nitter.conf.rej

@kescherAUR Thanks, applied the patch. Sorry for the delay.