AppImages > Network > NEFORUM


NEFORUM

Screenshot of NEFORUM

NEFORUM is a free and open-source cross-poster. Write a post once: NEFORUM adapts it for each network (character limits, threads, hashtags, links, media rules), shows a live preview of every version, and publishes it everywhere at once or on a schedule.

Three ways to post, per account:

  • Automatic through open APIs: Mastodon and the fediverse, Bluesky, Nostr, Misskey, Lemmy, Matrix, Telegram, Discord, WordPress, Ghost and more
  • Automatic with your own developer keys: X, Threads, LinkedIn, YouTube, Reddit, Pinterest, Tumblr, Facebook Pages and others
  • Hand-off for every other account: the text is copied, the photos saved and the network's composer opened, so you only press Post

NEFORUM is local-first. There is no NEFORUM server or account: posts go straight from your computer to each network, keys and tokens stay in the system keyring, and there are no analytics. An optional update check asks neforus.com for the latest version number only.

Authors: Neforuss

Compatibility: Uses the C library of the system (may need glibc 2.34 or later)


Usage

NEFORUM is available as an AppImage which means "one app = one file", which you can download and run on your Linux system while you don't need a package manager and nothing gets changed in your system. Awesome!

AppImages are single-file applications that run on most Linux distributions. Download an application, make it executable, and run! No need to install. No system libraries or system preferences are altered. Most AppImages run on recent versions of Arch Linux, CentOS, Debian, Fedora, openSUSE, Red Hat, Ubuntu, and other common desktop distributions.

This AppImage uses the C library of the system and may need glibc 2.34 or later. It does not run on distributions that use a different C library (such as musl on Alpine Linux) or an older glibc.

Running NEFORUM on Linux without installation

Unlike other applications, AppImages do not need to be installed before they can be used. However, they need to be marked as executable before they can be run. This is a Linux security feature.

Beware! AppImages are usually not verified by others. Follow these instructions only if you trust the developer of the software. Use at your own risk!

Download the NEFORUM AppImage and make it executable using your file manager or by entering the following commands in a terminal:

chmod +x ./*.AppImage

Then double-click the AppImage in the file manager to open it.

Sandboxing NEFORUM

If you want to restrict what NEFORUM can do on your system, you can run the AppImage in a sandbox like Firejail. This is entirely optional and currently needs to be configured by the user.

Updating NEFORUM

If you would like to update to a new version, simply download the new NEFORUM AppImage.

The NEFORUM AppImage also can be updated using AppImageUpdate. Using this tool, NEFORUM can be updated by downloading only the portions of the AppImage that have actually changed since the last version.

Integrating AppImages into the system

If you would like to have the executable bit set automatically, and would like to see NEFORUM and other AppImages integrated into the system (menus, icons, file type associations, etc.), then you may want to check the optional appimaged daemon.


Note for application authors

Thanks for distributing NEFORUM in the AppImage format for all common Linux distributions. Great! Here are some ideas on how to make it even better.

Pro Tips for further enhancing the NEFORUM AppImage

Please consider making the NEFORUM AppImage self-contained, so that it does not depend on the C library of the system and runs on more distributions: ship the C library including its loader (ld-linux-*.so.*) and use it to launch the application, or link statically.

Thanks for shipping AppStream metainfo inside your AppImage. Please open a pull request on https://github.com/AppImage/appimage.github.io/blob/master/data/NEFORUM if you have changed it and would like to see this page updated accordingly.

If you would like to see a donation link for the application here, please include one in the AppStream data.

History of this page

Edit the input for this page