Arch Linux User Repository

And now that the auth.nim tweak was merged, 1164.patch file no longer needs to be applied. git diff: https://0x0.st/HhwK.patch

@ynakao Thanks for the patch, applied.

One of the latest commits means the videos work again, by the guest accounts are dead, you need a proper account.

See https://github.com/zedeus/nitter/issues/1155#issuecomment-1917167072

Here you are. https://0x0.st/H5MU.patch My local build works fine. Please review :).

That's a good idea. Can you contribute a patch to change it? The symlink in /usr/share/nitter/ needs to change.

Frankly, the main problem is that nitter broke videos on this branch, and there seems to be no way to get them back.

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.