Search
100 results for “silverbulletmd”
-
Services I'm currently #SelfHosting in #Docker (managed via #Dockge):
* @silverbulletmd (notes, tasks, life)
* Miniflux (RSS reader)
* Jellyfin (local media streaming)
* Linkding (bookmarks)
* N8n (workflow automation)
* SearXNG (private search engine)
* Syncthing (sync)
* Minecraft server (for the kids)
* Calibre web (Web UI to my Calibre e-book collection) -
New post: The Markdown Link no. 13
Among today’s links are markdown editors Minknote, @silverbulletmd and MKeditor, markdown reader/viewer Readdown, a mini guide to Neovim/Vim, and the ultimate markdown set up in the Micro Journal Rev. 2.
https://md-handbook.com/blog/markdown-link-no-13/
#markdown #markdowneditors #Readdown #Minknote #Neovim #Vim #MicroJournal #SilverBullet #MKeditor
-
New post: The Markdown Link no. 13
Among today’s links are markdown editors Minknote, @SilverBulletMD and MKeditor, markdown reader/viewer Readdown, a mini guide to Neovim/Vim, and the ultimate markdown set up in the Micro Journal Rev. 2.
https://md-handbook.com/blog/markdown-link-no-13/
#markdown #markdowneditors #Readdown #Minknote #Neovim #Vim #MicroJournal #SilverBullet #MKeditor
-
New post: The Markdown Link no. 13
Among today’s links are markdown editors Minknote, @silverbulletmd and MKeditor, markdown reader/viewer Readdown, a mini guide to Neovim/Vim, and the ultimate markdown set up in the Micro Journal Rev. 2.
https://md-handbook.com/blog/markdown-link-no-13/
#markdown #markdowneditors #Readdown #Minknote #Neovim #Vim #MicroJournal #SilverBullet #MKeditor
-
New post: The Markdown Link no. 13
Among today’s links are markdown editors Minknote, @SilverBulletMD and MKeditor, markdown reader/viewer Readdown, a mini guide to Neovim/Vim, and the ultimate markdown set up in the Micro Journal Rev. 2.
https://md-handbook.com/blog/markdown-link-no-13/
#markdown #markdowneditors #Readdown #Minknote #Neovim #Vim #MicroJournal #SilverBullet #MKeditor
-
New post: The Markdown Link no. 13
Among today’s links are markdown editors Minknote, @silverbulletmd and MKeditor, markdown reader/viewer Readdown, a mini guide to Neovim/Vim, and the ultimate markdown set up in the Micro Journal Rev. 2.
https://md-handbook.com/blog/markdown-link-no-13/
#markdown #markdowneditors #Readdown #Minknote #Neovim #Vim #MicroJournal #SilverBullet #MKeditor
-
Let me try to explain what frustrates me about #AICodingAgent generated (or assisted) PRs by example. This is just one example, but it's quite typical of what I see a lot:
https://github.com/silverbulletmd/silverbullet/pull/1731
First of all: very elaborate PR description that ostensibly sounds like some deep analysis happened here. I'm not sure what the original prompt was here, but I suspect (based on some others by the same author — which I all closed) he has some "magic prompts" along the lines of "find performance bottlenecks and fix them."
And lo-and-behold, Claude found one (and probably more that are shared with yours truly in the 17 other PRs that this author opened):
"Syscalls: Reduced from 4 → 3 per write (25% reduction). This optimization is in the critical user latency path - every file save operation hits this code."
Now you will probably think: sounds reasonable, thank you!
But... is this REALLY a critical user latency path? Every file save does hit this path, but how many of those happen, really? SilverBullet is a single user app, and saves happen (with a sync lag) at most every few seconds if you're actively editing and Internet connected. Is this a path worthy of even a minute of performance optimization? I can think of hundreds that would way more interesting. But here we are.
Now this PR also adds a full benchmark suite to prove the made claims. I haven't actually looked at this code, to be honest because honestly it's pretty irrelevant because I don't feel there's a performance issue to be resolve here at all. I also haven't checked if all those stats in the PR are actually accurate. Again, doing so would take time, which I would consider 100% waste.
But here's the kicker: this PR actually introduces possibly two bugs in the ~10 lines that it actually changes: one definite bug (as I comment in the PR): it sets the creation time of a file to be the modified time, which is just wrong, but actually the only "sensible" think you can do to avoid making the syscall which this PR eliminates.
Second, more subtle, is a second bug is that it introduces a discrepancy between the OS reported file modified timestamp and the "unix clock" one, which it claims is "a few microseconds at most", but that's likely not true (and very filesystem dependent) and ANY discrepancy will mean that the sync engine breaks because it uses those last modified timestamps to check for changes.
And here's the thing. Me explaining this, thinking about it, commenting on it took likely 10x more time than the author spent on producing this piece of art. It doesn't solve an actual problem, it adds 150 lines of useless benchmarks and to top it all off introduces 2 bugs. In this case I think there's no actual way to do this properly, the PR cannot be fixed, it is just based on a wrong analysis. But in many other cases it's possible to get it to some place "good" as in: correct, but STILL it would be a waste of time, because the problem doesn't exist or at least is not worth addressing.
sigh
-
Besides not using a better #LML syntax such as #Orgdown, I really do like the way how @silverbulletmd is transparent about its #Markdown downsides.
That's why I extended my article on the downsides of Markdown with it as an example: https://karl-voit.at/2025/08/17/Markdown-disaster/
-
So, I just decided to fix that. Took an hour or so: https://github.com/silverbulletmd/silverbullet/commit/eb3af597be3bb46eca86a2eda1bfecf0f94dc145 There was already an excellent library (turndown) that turns HTML (rich text) into Markdown, I just had to mix the two. Now I can happily copy and paste rich recht from websites, Google docs and even spreadsheets and have them cleaned up into nice Markdown. So nice. Less than 100 lines of code on my side. #PowerOfOpenSource
-
Just #donate 'd to 11 #foss projects, despite my irregular income ( #artist #life ). Besides money it also did cost some time due to so many different #donation platforms, unfortunately. 😬
I'll try to list the projects as accounts or at least a tag (not all are on Mastodon, unfortunately). ❤️
#aveslibre @davx5app @kde #keepass #keepasdx @ShareX @silverbulletmd #stratum #authenticator #tasksorg @termux @signalapp
-
While I'll admit this is somewhat self serving, I do believe that web apps rather than "native" apps remain the best path forward for most things, also on mobile.
The web remains the only platform that is not (entirely) controlled by #BigTech. There's no approval process. Web apps cannot (easily) be pulled. Whoever builds them is in full control of their distribution. There's no tax on "in app" purchases. Yes, the browser landscape is not as diverse as it ought to be and hopefully that will improve, but if you compare it to Apple and Google-controlled ecosystems like iOS and Android, it's still miles ahead. Also, they're way cheaper to build.
In 2026 I'm aiming to be more deliberate in filling up my dock and home screen (yes, I will likely stay on Apple operating systems for pragmatic reasons) with more and more web apps, replacing native apps. I think this doable now. OS support for PWAs has improved a lot (even on iOS). They can be icons on your home screen/dock, they can be fast, they can be offline capable, they can send notifications.
On my home screen right now some daily driver #PWAs: @silverbulletmd (notes), @phanpy (fediverse), #Miniflux (RSS reading), Voyager (Lenny and PieSocial client), @linkwarden (link collection), @homeassistant (still the native app, but 99% web tech), #Ghost (blogging), @plausible (analytics). #Feishin (@navidrome_releases streaming), @fastmail (email).
-
I've been trying to make sense of staff/chief/distinguished level engineers being enthusiastic about #AICodingAgents. Intuitively you'd assume they're the adults in the room and should easily detect the quality and bullshit that such agents pull.
Mindsets I can explain:
Junior engineers: oh my, I'm getting super powers!
Mid engineers: I thought I had so much left to learn, but maybe I don't have to!
Senior engineers: this looks cool, but hang on let's have a closer look 🤔 — err... wtf!?
Staff engineers: now I no longer have to work with junior-senior engineers to work out the details!
That last bit is key, I suspect. At the Staff level, you're less involved with the details, mostly with the bigger picture and bigger ideas. At that level, AI code looks fine. You're used to having people you can leave ironing the details to, now those are just automated. The trap here is that the people you handed work to weren't professional bullshitters. Likely you had trained them yourself, you could gauge their skillset and knowledge or get hints of what they were based on their communication. That's no longer the case with coding agents. They always sound "PhD level" no matter what. Therefore it's very easy to miss the garbage they produce.
In some contexts I acted at a Staff-level and it took be considerable time to "poke" through this reality distortion. Maybe all those enthusiastic Staffers we hear now are simply not there yet.
The sooner the beter, though. I'm still cleaning up the mess after my own "AI coding power trip" in the @silverbulletmd code base.
-
For those able to read (or translate) Chinese, a nice review of SilverBullet: https://sspai.com/post/109399
-
Ok, let's do this. SilverBullet+ (#SilverBullet on your desktop) is officially on the loose! https://silverbullet.plus
Release announcement and backstory:
https://community.silverbullet.md/t/silverbullet-release/4142
-
#SilverBullet 2.7 released!
This one lands with a brand-new Configuration Manager: a proper UI for editing common configuration options, managing key bindings, and installing libraries. The CLI has been renamed from `silverbullet-cli` to `sb` with reworked commands. There's a new (experimental) Anchor syntax ($name) for stable, space-globally unique names on almost any object. And... “Lua Integrated Query” (LIQ) has been rebranded to Space Lua Integrated Query — SLIQ!
https://community.silverbullet.md/t/silverbullet-2-7-released/4112
-
A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef
-
A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef
-
A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef
-
A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef
-
RE: https://graz.social/@publicvoit/115875810144458821
I really do like how #SilverBullet is explaining the consequences of using their version of #Markdown on https://silverbullet.md/Markdown (#CommonMark).
With statements like that, people learn about the consequences of using that tool.
They can either accept this or think about the negative effects before investing too much energy and data.
I really urge any (#MD-)tool to include such a warning statement on their project page. It's for the benefit of your users.
One of the reasons why I most probably would recommend switching to SilverBullet if you - for some reason - can't use #orgmode with #Emacs which is IMO the optimum tool for many set of requirements: https://karl-voit.at/2021/01/18/tool-choices/
I'll migrate my wife's #PKM from #logseq (recent changes are a no-go to me) to SilverBullet or preferably Emacs. My upcoming #GLT26 Org-mode workshop (no recording) will tell her.
-
I'm definitely having fun hacking away at #silverbullet. 😄
Right now, getting used to using the #javascript import. Which can effectively pull almost any js module. And with #jsr being a thing... let's just say silverbullet instance is going to get weird. 😅
I'm honestly surprised it took this log to learn of this gem. Likely due to my still very much liking #logseq. Although... give me a few weeks... I'll likely build my own journaling system on this thing. 😇
-
A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef
-
ABC (update 2)
Scientific info management.
SilverBullet Community：https://community.silverbullet.md/t/abc-accurate-bi-directional-cursor-level-linking-system/3536/20?u=chenzhu-xie
#PKM #biDirectional #noteTakingApps #personalWebsite #selfHosting #silverBullet #Lua
-
ABC (update 1)
Aiming to reduce frictions in daily workflow.
SB Community：https://community.silverbullet.md/t/abc-accurate-bi-directional-cursor-level-linking-system/3536/18?u=chenzhu-xie
#PKM #biDirectional #noteTakingApps #personalWebsite #selfHosting #silverBullet #Lua
-
I was using (and loving it) #LogSeq to take notes, but there are problems in having it in sync with my phone, as iPhone does not allow you to easily open the files synced with #NextCloud in #LogSeq, and editing the MD files directly in #NextCloud break the formatting.
After some search for a substitute, I can already say that #silverbullet (https://silverbullet.md) might end up being a good substitute for it (hosted in my personal server, behind VPN + #Authelia) -
[[Silver Bullet]], a backlink enabled #opensource #ToolsForThought app https://silverbullet.md/
#TypeScript, #React, uses #CodeMirror as editing interface, #Markdown native, supports Jekyll-style front matter for custom attributes.
Experimental “Google Doc style” real time collab using #Yjs and a central #WebSocket server.
via @walkah
-
@miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: https://karl-voit.at/2025/08/17/Markdown-disaster/
Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: https://karl-voit.at/2024/01/28/logseq-from-org-pov/
Die DB-Version werden wir garantiert nicht mitmachen.
Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt https://karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: https://silverbullet.md/Markdown
Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔
Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.
-
@miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: https://karl-voit.at/2025/08/17/Markdown-disaster/
Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: https://karl-voit.at/2024/01/28/logseq-from-org-pov/
Die DB-Version werden wir garantiert nicht mitmachen.
Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt https://karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: https://silverbullet.md/Markdown
Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔
Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.
-
@miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: https://karl-voit.at/2025/08/17/Markdown-disaster/
Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: https://karl-voit.at/2024/01/28/logseq-from-org-pov/
Die DB-Version werden wir garantiert nicht mitmachen.
Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt https://karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: https://silverbullet.md/Markdown
Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔
Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.
-
@miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: https://karl-voit.at/2025/08/17/Markdown-disaster/
Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: https://karl-voit.at/2024/01/28/logseq-from-org-pov/
Die DB-Version werden wir garantiert nicht mitmachen.
Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt https://karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: https://silverbullet.md/Markdown
Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔
Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.