ButSystem.py (Exclusive) — Full Button & Function Index

This is the complete, practical breakdown: every screen, every visible action, and what each button does — based on the ButSystem.py interface structure.

Note: some controls appear only for admins/mods, or only when a feature is enabled. This page includes those too and marks them clearly.

System overview

ButSystem.py runs a local web UI (self-hosted on your device). You navigate using the burger menu and perform actions inside modules (Chats, Groups, Files, Admin, Settings, etc.).

All screens & buttons (complete)

Instead of a long button-by-button list, this section explains each ButSystem area the same way the Learn page explains tools: by feature area, what you do there, and what kind of controls you will find when you open it.

Navigation & menu flow

The burger menu is the main control hub of ButSystem. From there you move between chats, discussion, groups, calls, stories, live locations, files, profile pages, Profiler, reports, admin pages, settings, help, and login or logout actions, while the language toggle keeps the interface available in both English and Greek.

Authentication & access

ButSystem opens through its landing, loading, login, and signup flow, then adds extra access control where needed. That includes user approval, device access requests, remembered-device login, optional security-question two-factor checks, and password recovery or reset actions so access stays tied to approved users and approved devices.

Direct messages

The DM area is built for day-to-day private conversation. You can open a chat, write and send text, edit or delete messages, search conversation content, attach media or files, use GIFs, record or play voice notes, and work with chat protections such as PIN locks and visible online status where those controls are enabled.

Discussion room

Discussion works more like a shared stream than a one-to-one chat. It is the place for broader entries, category-based posting, search, refresh, loading more content, and opening a specific entry when you want a calmer shared space separate from normal DMs.

Groups

The Groups area lets users build shared spaces with roles and moderation controls. You can create a group, invite or add members, check the member list, manage owner or admin actions such as promote, demote, or remove, leave a group when needed, and continue the conversation through the related group chat with messages and attachments.

Calls & live communication

Where browser support and device permissions allow it, ButSystem includes call flows for starting, joining, accepting, denying, muting, and ending a live call. The exact experience depends on microphone permissions and the current browser environment, so the call layer is treated as a live feature area rather than a static page.

Stories & live locations

ButSystem also covers lighter live-sharing tools. Stories give users a quick post-and-view layer with story creation and viewing controls, while Live Locations is reserved for opt-in location sharing with start, stop, refresh, and clear consent or warning prompts before location data is actively shared.

Files, vault & saved media

The Files and Vault area is the storage side of ButSystem. It gives you upload, download, delete, open, search, new-folder, and folder-navigation controls so the workspace can hold private files, chat attachments, shared material, and organized user content without turning the interface into a separate file manager app.

Profile, account & appearance

Your own profile area handles identity and account presentation. From there users can view or edit profile data, save changes, upload or remove a profile picture, adjust account settings, control appearance options, and access stronger account actions such as account deletion or the self-destruct danger zone where that workflow is enabled.

Profiler, bounty & Face Detector

The Profiler side is where ButSystem becomes a structured information workspace. It supports encrypted profiler entries, view and edit flows, local search, export and combine tools, bounty management where that module is enabled, and the built-in Face Detector area used for local face-detection workflows and similarity-style comparison support inside the broader ButSystem environment.

Reports, admin & security settings

The control layer of ButSystem is split across reports, admin pages, and security settings. This is where users create or update reports, where admins approve or deny access and device requests, manage people and user files, and where account holders configure two-factor settings, device-login rules, password-reset paths, privacy options, and other safeguards that keep the workspace organized and controlled.

Technical map (routes & templates)

Routes (endpoints)

Templates (screens)

This section exists so the UI documentation matches real pages/components in the script.

Core ButSystem feature areas

ButSystem.py brings chats, groups, files, profiles, security controls, admin tools, and local-first workflow features together in one self-hosted interface.

Chats, Groups & Stories

Live direct messages, group chats, saved messages, GIFs, voice notes, file sharing, the discussion room, stories, and call flows where browser and device support allow it.

Security, Access & Control

User approval, device access requests, remembered-device login, optional security-question 2FA, chat PIN locks, online status, reports, admin pages, and appearance or account settings.

Profiles, Vault & Tools

Profile editing, private file vault, opt-in live location sharing, encrypted Profiler entries with local search, export and combine tools, bounty management where enabled, and the built-in Face Detector.

Batman-style checklist (still hypothetical, still lawful)

When you feel the ‘I want revenge’ impulse, switch to a rule-based mindset. In Gotham terms: calm down, observe, document, protect.

  1. Pause (10 minutes minimum). No messages, no calls, no posts.
  2. Write a timeline: what happened, when, and what you *know* vs what you *assume*.
  3. Collect only lawful evidence you already have (screenshots, receipts, your own logs).
  4. Protect your accounts: change passwords, revoke access, review sessions, limit invites/uploads.
  5. Use ButSystem to coordinate calmly (DM/Group), not to escalate.
  6. Choose a lawful outcome: support, mediation, reporting, or professional help.

Scenario D: ‘Shadow discipline’ (no contact)

You block impulsive moves: no late-night calls, no angry texts. You use the system to write drafts privately, then wait. If it’s still valid tomorrow, you send a calm version — or you don’t send it at all.

Scenario E: ‘Alfred protocol’ (trusted support)

You loop in one trusted person. They help you check your thinking, keep you grounded, and prevent you from doing something you’ll regret.

Scenario F: ‘Detective report’ (closure)

You write a final report: facts, impact, what you learned, and what boundary you set. Then you move on. That’s the point: closure, not obsession.

Fight corruption (responsibly)

DedSec’s mindset also applies to corruption: not vigilantism, but responsible action. Use tools to organize information, protect yourself, and push for accountability through lawful channels.

Document & organize

Keep a clear timeline, store lawful documents, and separate facts from assumptions. Clean structure beats chaos.

Protect yourself

Use strong passwords, limit who has access, and avoid risky confrontation. If you’re whistleblowing, consider professional legal advice.

Accountability through law

Choose lawful reporting: internal compliance, auditors, ombudsman, regulators, or trusted journalists — depending on the case.

Rule: if an action could harm an innocent person or break the law, don’t do it. The mission is accountability and protection.

The strongest move is self-control. If you feel you might do something harmful, step away and ask for help.

Back to tools Read our vision