Skip to content
TheChatArchiveThe Chat Archive
grok-3-preview-02-24· xAIHugging Face LMArena Human Preference 140K

I'm a new user to obsidian.md, and am interested in a maximalist approach to the…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Qwenqwen3-235b-a22b’s answer.
  1. User

    I'm a new user to obsidian.md, and am interested in a maximalist approach to the obsidian plugin ecosystem. I consider myself to be the textbook definition of "power user", and Im interested in improving my onboarding process with obsidian. currently, the issue is the limited nature of the community plugins browser. I do not need you to try to provide an exhaustive code solution, but I am interested in whether or not it is even possible to interact with the community plugin browser system when creating a plugin of my own.

  2. Assistant

    Welcome to Obsidian! As a self-described "power user" with a maximalist approach, you're in for a treat with Obsidian's highly extensible plugin ecosystem. Your question about interacting with the community plugin browser system when creating your own plugin is an excellent one, and I'm happy to provide clarity and direction.

    Is It Possible to Interact with the Community Plugin Browser System?

    Yes, it is possible to interact with the community plugin ecosystem programmatically, but there are important nuances to consider:

    1. Obsidian's Plugin Ecosystem Overview:

      • Obsidian's community plugins are managed through a centralized manifest file (community-plugins.json) hosted on GitHub in the official Obsidian repository (obsidianmd/obsidian-releases).
      • The in-app Community Plugins browser fetches this manifest to display available plugins, their descriptions, authors, and other metadata.
      • When a user installs a plugin via the browser, Obsidian downloads the plugin files (e.g., main.js, manifest.json, and optionally styles.css) from the plugin's GitHub release page.
    2. Interacting with the Plugin Browser System:

      • As a plugin developer, you cannot directly modify or extend the in-app Community Plugins browser UI (e.g., adding custom buttons or filters to the browser) because it is part of Obsidian's core, closed-source codebase.
      • However, you can interact with the plugin ecosystem in other ways, such as:
        • Fetching Plugin Metadata: You can programmatically fetch and parse the community-plugins.json file to access metadata about all community plugins.
        • Automating Plugin Installation: While not officially supported, it is technically possible to write a plugin that automates the download and installation of other plugins by mimicking the behavior of Obsidian's plugin installer (e.g., downloading plugin files and placing them in the user's vault plugin directory).
        • Enhancing Plugin Discovery: You could create a plugin that provides an alternative interface for browsing, searching, or recommending plugins, using the data from community-plugins.json.
    3. Practical Use Cases for a "Maximalist" Onboarding Plugin: If your goal is to improve your onboarding process with a maximalist approach, here are some ideas for a custom plugin that interacts with the community plugin ecosystem:

      • Plugin Recommendations: Create a plugin that curates a list of "power user" plugins based on metadata (e.g., filtering by tags, popularity, or user reviews) and presents them in a custom UI within your vault.
      • Batch Installation: Develop a plugin that allows you to select multiple plugins from a curated list and automates their installation (e.g., by downloading files from GitHub releases and placing them in the .obsidian/plugins directory).
      • Plugin Management Dashboard: Build a plugin that provides a more advanced plugin management interface, such as tracking plugin updates, enabling/disabling plugins programmatically, or even analyzing plugin compatibility.
    4. Technical Feasibility:

      • Accessing community-plugins.json: You can fetch the manifest file using a simple HTTP request in your plugin. For example, in JavaScript (using the Fetch API or a library like axios):
        const response = await fetch('https://raw.githubusercontent.com/obsidianmd/obsidian-releases/master/community-plugins.json');
        const pluginData = await response.json();
        console.log(pluginData); // Array of plugin metadata
        
      • Installing Plugins Programmatically: To install a plugin, you would need to:
        1. Fetch the plugin's manifest.json from its GitHub release.
        2. Download the required files (main.js, manifest.json, and optionally styles.css).
        3. Write these files to the appropriate directory in the user's vault (e.g., .obsidian/plugins/<plugin-id>/).
        4. Trigger a reload of Obsidian's plugin system (e.g., by calling app.plugins.loadPlugin(pluginId) if the API allows it—note that this is not officially documented and may require experimentation).
    5. Ethical and Practical Considerations:

      • Obsidian Team's Stance: The Obsidian team encourages plugin development but may frown upon plugins that bypass the official Community Plugins browser for installation, as this could introduce security risks (e.g., installing unverified code). If you develop such a plugin, it would likely need to remain a private tool or be distributed with strong disclaimers.
      • Security: Be cautious about automating plugin installation, as it could expose users to malicious code if not properly vetted.
      • Community Guidelines: Ensure that any plugin you develop adheres to Obsidian's community guidelines, especially if you plan to submit it to the official plugin repository.
    6. Alternative Approaches: If your goal is to streamline onboarding without building a plugin, consider these options:

      • BRAT Plugin: The "Beta Reviewer's Auto-update Tool" (BRAT) plugin allows you to easily install and update beta versions of plugins, including those not yet in the community plugin list. You could use BRAT to quickly install a curated list of plugins.
      • Manual Curation: Create a personal "starter kit" by manually installing a set of plugins, then copying the .obsidian/plugins directory to new vaults as needed.
      • Templater or Dataview: Use plugins like Templater or Dataview to create dashboards or scripts that help you manage and document your plugin setup.

    Next Steps for a Power User

    To kickstart your maximalist onboarding process, here’s a suggested roadmap:

    1. Familiarize Yourself with Plugin Development:

      • Read the official Obsidian Plugin Developer Docs: Obsidian Developer Docs.
      • Study the source code of existing plugins on GitHub to understand common patterns (e.g., look at popular plugins like Dataview, Templater, or Style Settings).
    2. Prototype a Plugin:

      • Start by writing a simple plugin that fetches and displays the community-plugins.json data in a custom modal or view within Obsidian.
      • Experiment with programmatically downloading plugin files and placing them in the vault's plugin directory.
    3. Curate a Power User Plugin List:

      • Identify plugins that align with your maximalist approach. Some recommendations for power users include:
        • Dataview: For advanced querying and data visualization.
        • Templater: For automating workflows and templating.
        • Style Settings: For customizing themes.
        • Obsidian Git: For version control integration.
        • QuickAdd: For rapid note creation and automation.
        • Excalidraw: For advanced diagramming.
        • Kanban: For task and project management.
        • BRAT: For beta plugin testing.
      • Consider creating a JSON file or script that defines your curated list, which your custom plugin could use.
    4. Engage with the Community:

      • Join the Obsidian Discord server or forum to discuss your ideas and get feedback from other power users and developers.
      • Share your plugin (if you develop one) with the community, either privately or by submitting it to the official plugin repository.

    Final Thoughts

    While you cannot directly modify the in-app Community Plugins browser, you can absolutely create a plugin that enhances your onboarding experience by interacting with the plugin ecosystem in creative ways. The key is to balance ambition with practicality, ensuring that any automation you build is secure, ethical, and aligned with Obsidian's ecosystem.

    As a power user, you'll likely find Obsidian's plugin development environment incredibly rewarding, as it allows for near-infinite customization. Start small, experiment, and iterate—your maximalist vision is well within reach!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.