NEFORUM: prepare one post for two networks Free software. Your computer. Your choice of where to share. NEFORUM helps you turn one post into versions that fit different social networks. It runs on your device, its source is open under GPL-3.0, and there is no NEFORUM subscription or account. You can explore its sample workspace without connecting any social account. Review status: Official documentation and selected source reviewed for v1.3.5 on 7 November 2026. These are suggested steps, not a completed hands-on test or security audit. Before you begin - Use a computer you control. Windows, macOS and Linux downloads are available; Android uses an APK, and iPhone/iPad installation requires sideloading. - Download only from the project's official page or linked GitHub release. Desktop builds are not code-signed yet. Review the source, release notes and verification instructions before deciding whether to run them. Do not bypass a warning you do not understand. - A download, a social account and an automatic publishing API are different things. The app is free; some networks charge for their API or require approval. - Start without sync, browser extensions, developer keys or a media host. You do not need them for the demo. 1. Practise locally, without an account After you choose to install or run the app, open Settings, then Workspace, and enable Demo workspace. The sample accounts are fictional and their publishing is simulated. Keep practice content fictional too; do not enter real passwords or keys into demo forms. Create a short update about something you made. Choose the sample Bluesky and Mastodon accounts. Read both previews, shorten the Bluesky version if needed, and use Differentiate to adjust each version. Check the link, wording and image description if you add an image. Save a draft and reopen it. Try the sample publishing flow only after confirming Demo workspace is still on. A demo success is practice, not a live post. Copy any practice text you want to keep to a local text file: demo account and post data are held in memory. Your first useful result: two readable versions of one update, without creating a new account or giving the app publishing access. 2. Share manually when you are ready Turn Demo workspace off. Add one existing social account using its Hand-off option. NEFORUM prepares the text and opens the platform's composer; you review it in the correct account and press Post yourself. Check the platform directly afterward. Repeat for a second network only when the content fits that audience. Hand-off is a useful free path when API setup is costly or complicated. It does not provide unattended publishing, and it does not remove the platform's rules. Do not send the same promotional message across unrelated communities. 3. Add automation only where it helps Mastodon and Bluesky are sensible early candidates. Mastodon needs authorization on your server. Bluesky uses a separate app password; the project's guide says to leave direct-message access off. Connecting either gives the app continuing access, so review the requested permissions first. Read the guide for the exact platform before connecting it. Instagram needs a professional account for its API. TikTok's unaudited API route is private-only. New Reddit API access needs approval. X's API charges for posting. These limits come from the destination platform, not a NEFORUM paywall. Keep browser automatic posting off initially. Use official APIs where allowed, respect community rules, and inspect an uncertain outcome before retrying. For most local schedules, the computer must remain running and online; iPhone background scheduling has additional limits. Keep your work portable The Windows ZIP avoids an installer, but it is not a self-contained portable workspace: data stays in OS app storage and secrets in the system keychain. Use Settings > Data & privacy > Move to another device for encrypted migration, and keep the passphrase safe. Photos and videos are not included, so transfer those separately. Imported scheduled posts become drafts to avoid duplicate publication. Local-first does not mean everything stays offline. Publishing sends content to each network. Some APIs also need a public media host, and optional sync sends an encrypted file to storage you choose. Leave those additions out until you need and understand them. What this tool is good for Independent creators, community projects and small teams who want to own their posting workflow, avoid another subscription and learn a few connections at a time. The honest starting point is one useful post and two suitable destinations, not a blast to all 48 entries. Official links Project and downloads: https://neforus.com/neforum/ Source: https://github.com/Neforuss/NEFORUM Licence: https://github.com/Neforuss/NEFORUM/blob/main/LICENSE Platform choices and limitations: https://github.com/Neforuss/NEFORUM/blob/main/docs/platforms.md Bluesky setup: https://github.com/Neforuss/NEFORUM/blob/main/docs/platforms/bluesky.md Migration: https://github.com/Neforuss/NEFORUM/blob/main/docs/backup.md Browser-extension limits: https://github.com/Neforuss/NEFORUM/blob/main/docs/browser-extension.md