Attachments vs Filebase: Where Should Your Files Go?

To keep support threads readable and downloads easy to find, LinuxSat-Support splits content into two places depending on what it is: images stay attached to forum posts, and downloadable files go in the Filebase. Here's what that means for you, whether you're posting a screenshot or sharing a plugin.

Why split it this way?

As any forum matures, downloadable files attached directly to posts get scattered across years of pages — page 4 of a thread might have version 1.2 of a plugin, page 11 has 1.3, page 17 has 1.4, and newcomers have no way to tell which is current without reading the whole thread. Filebase exists to solve exactly this: it gives every download a single canonical page with version history, a changelog, download counts, and comments — so the thread stays focused on discussion and support, and the file stays easy to find.

Images: keep them in the thread

Screenshots, error messages, logos and similar images should stay as normal forum attachments, shown inline in your post. This is the most useful way to illustrate a problem or a setup step without sending anyone away from the discussion — keep doing this exactly as before. Supported image types (JPG, JPEG, PNG, GIF) are unaffected by anything below.

Downloads: use the Filebase

Anything another member would want to download and keep — firmware images, plugins, OSCam/softcam builds, scripts, configuration files, channel lists, receiver backups — belongs in the Filebase, not as a forum attachment. If you're not sure how to create a Filebase entry, see our How to Use the LinuxSat-Support Filebase guide.

Posting the file in Filebase instead of attaching it to a post gets you a proper version history, a changelog readers can check before updating, a download counter, and a place for ratings and comments — none of which a forum attachment can offer.

Always keep the latest version in the first post

If you maintain a thread for a tool or plugin, the single most useful thing you can do is make sure the first post always links the current version — whether that's a Filebase link or (for smaller threads) an attachment. Members shouldn't have to read through dozens of pages to work out which download is actually current. If you update a file, update the first post to match, and remove or archive outdated attachments where practical.

What to do with older threads

You don't need to do anything to threads that aren't yours, and there's no rush to fix old content retroactively. If you're the one maintaining a thread and it's grown a long attachment history, moving the current version to Filebase and updating the first post whenever you're next active there is the easiest way to tidy it up — a little at a time, not all at once.