Because you were always a reply guy, on the inside.

fediEngine is a Free and Open Source (GPLv3 licensed) desktop client for ActivityPub and related projects such as Mastodon, Pleroma, and Misskey. It is written in Python and PyQt5, isn't a web browser, and because it's not a web browser, it uses a lot less memory than a web browser, even with tens of thousands of statuses loaded.

fediEngine is designed to give you a complete view of the fediverse, one free of the restrictions and inefficiencies of normal server-to-server federation. fediEngine dynamically fetches statuses both directly from the servers they originate from, and from any servers they federate with. It also enables you to instantly view any instance's public or federated timelines, and search every instance at the same time.

Because the designer of a specific fediverse daemon gaslights users and calls that "security", fediEngine goes above and beyond to protect user safety and security. Powerful content-shaping utilities, some of which cannot be found on any other client, are here to provide you the security you've been begging Eugene to give you for literally years! List subscriptions, dynamic lists, and better tunable block logic keeps out, what you want out.

Alpha Features


  • Native multi-account support
  • Post from any/all accounts at once
  • Like/Boost from any/all accounts at once
  • Unified notifications tab


  • Public timelines, anonymous or authenticated
  • Federated timelines, anonymous or authenticated
  • Full text and hashtag search
  • Firehose view shows combined federated timelines of every instance your client knows about
  • Content Shaping

  • List creation and subscriptions
  • Lists can contain any number of actors, instances, keywords, and hashtags, in any combination
  • Any list can be used to block, mute, allow, highlight, or direct statuses to a special tab
  • Lists can be exported, so others can subscribe

  • FAQ

    How could you do this?

    I already told you. Python and PyQt5.

    When can I get it?

    2023-02-14: This project has been on hold for some time. Ironically the stumbling block was the interprocess nonsense I had to fix for as:Public. So maybe I can pick it up again.

    The code is currently shittier-than-alpha quality. Follow the development/testing announcements account for links to each pre-alpha release.

    An open alpha, including a public git repository, will happen once the internal structure is more solid.

    Will there be any hard-coded login blocks?

    No. You may import or subscribe to lists to block on an automated basis. You can also mark any instance as "excluded", which entirely prevents communication with, or the processing of information regarding, an entire instance.

    If you are concerned about people using your computer to log into sites you don't like, you should put a password on that computer.