This is going to be my rant. Ignore it as you wish.
Consider the following:
- Silverbullet was developed by @zef for his use.
- @zef decided to make silverbullet available to those with a “hackers mindset” to use as they see fit.
- @zef is working full-time, as I understand it, while continuing to work on Silverbullet.
- As Silverbullet becomes ever more complex and huge, a time will come where @zef will no longer be able to maintain the system.
- There are a number of people here that act as though they are typical users. They make requests/demands, criticize, and complain without lifting a single finger to help.
@zef, I would encourage you to only put into Silverbullet what you will use and nothing else.
Any other functionality should be developed in the form of scripts and plugins or as code which should be implemented into a fork of Silverbullet. Then, the developer bears all responsibility for the results while adding nothing to @zef’s work load.
To My Fellow Users: My message is simple, either find a way to use Silverbullet as is or write scripts, plugins, or additional code probably in a fork which you are willing to maintain and support to make it into something you can use.
Stop acting like a typical computer user who expects the developer of the software to create and maintain everything he wants while he acts as the critic and judge. Be willing to take part. You create and maintain what you want in Silverbullet yourself. Demonstrate that “hacker mindset”. Otherwise, there are plenty of other more complete note taking applications developed with the typical user in mind.
I came from Logseq. Logseq had everything that I wanted in a Note Taking app and I was ecstatic. Then the developers decided to move from basing it on markdown files to basing it on a database of their own design. While they insisted that they would provide a way to extract the data back to markdown files, doing so will become ever more difficult as they add more functionality to the database until they will inevitably decide to no longer provide database to markdown conversion capability. I want full control of my data. So, this was unacceptable.
Silverbullet isn’t Logseq. Attempting to make Silverbullet act like Logseq would be an arduous task indeed. I chose, instead, to see if I could create a different workflow using what Silverbullet already made available. After all, if @zef could use it, then maybe I could too.
I have come a long way down that path. I am using Silverbullet full-time. Logseq is still on my system giving me access to those files for the time being. Eventually, I’ll either incorporate some of those files into my Silverbullet PKM or I’ll delete them.
I’m still in the midst of building and modifying my Silverbullet workflow. So, I’m going to wait until my workflow stabilizes a bit more before I attempt to integrate some of the Logseq content into Silverbullet.
End of rant.
@zef, I strongly encourage you to keep Silverbullet as a system that is primarily for your use. This will keep it manageable for you. Let others fork it or modify it for themselves. I would discourage turning it into a multi-user system since the security issues alone would be a full-time job which seem to be getting more difficult as time goes on. Besides, you will never be able to please all of the user minded people since they cannot even agree among themselves. They are spoiled children. Keep silverbullet a system for the “hacker minded” only. Keep it a system that you want to use and are able to easily maintain.