“It doesn’t overwhelm you on day one. It doesn’t gamify your productivity. It doesn’t trap you inside someone else’s framework. It just gives you tools. If you’re the kind of person who likes shaping their environment instead of being shaped by it, that’s powerful. #SilverBullet isn’t flashy. It isn’t beginner-coddling. It’s a blank page, running on your machine, waiting to see what you build. And that quiet confidence is exactly why I stayed.”

https://www.makeuseof.com/silverbulletmd-is-the-most-flexible-markdown-notes-app/

“It doesn’t overwhelm you on day one. It doesn’t gamify your productivity. It doesn’t trap you inside someone else’s framework. It just gives you tools. If you’re the kind of person who likes shaping their environment instead of being shaped by it, that’s powerful. #SilverBullet isn’t flashy. It isn’t beginner-coddling. It’s a blank page, running on your machine, waiting to see what you build. And that quiet confidence is exactly why I stayed.”

https://www.makeuseof.com/silverbulletmd-is-the-most-flexible-markdown-notes-app/

4 years of #SilverBullet https://community.silverbullet.md/t/4-years-of-silverbullet/3882

4 years of #SilverBullet https://community.silverbullet.md/t/4-years-of-silverbullet/3882

@zef do you have the daily page open as the default when you starting #SilverBullet ?

First day of adopting the #LogSeq style journaling approach in #SilverBullet, that is:

1. Create a page for the day
2. Primarily take notes on that page as an outline
3. Mention people and topics as page references
4. Rely on Linked Mentions later from those pages, that now automatically collect (relevant) information. This works better in #SilverBullet now that child nodes are also kept as part of the linked mention snippet.

Let's see how this goes!

#pkm

#SilverBullet 2.4 released: improved indexer (performance and correctness), and much more: https://community.silverbullet.md/t/silverbullet-2-4-released/3772

#SilverBullet 2.4 released: improved indexer (performance and correctness), and much more: https://community.silverbullet.md/t/silverbullet-2-4-released/3772

LLM use in community and #SilverBullet core contributions

https://community.silverbullet.md/t/llm-use-in-community-and-silverbullet-core-contributions/3771

LLM use in community and #SilverBullet core contributions

https://community.silverbullet.md/t/llm-use-in-community-and-silverbullet-core-contributions/3771

Wrote a draft of an LLM policy for #SilverBullet. Not final yet, but interested in feedback. TL;DR: #NoAI

https://gist.github.com/zefhemel/077c0b62f54da2cbfcc09c13bfe88ec8

Interesting. Hit 1k subscribers on youtube yesterday, somehow. Has to be due to the #silverbullet videos that get a fair amount of views. There must be some sort of opportunity here.

Can I just make @Codeberg’s OCI container repo the new default for #silverbullet ? Is that recommended? Can’t find any source with limits or recommended use.

Everything on @Codeberg is just straight forward and just works? There's even a docker (OCI) container registry. You just login to it and push your images and... they're there? https://codeberg.org/silverbullet/-/packages/container/silverbullet/latest (just a test for now). Haven't looked at migrating #silverbullet actions yet, but I have already set up a self hosted running that runs in my attic. Kind of excited to start using that instead of the default runners.

So a few steps that I plan to make whether I end up migrating #SilverBullet to Codeberg (or elsewhere) or not:

1. Offer the same level of support for @forgejo hosted repositories as for Github ones in SilverBullet itsel (most notably: implement Share support)
2. Change examples in the docs to be #CodeBerg rather than #GitHub first
3. Change default Docker registries for images back to docker hub (unless people have better suggestions) — had changed those to GHCR before.
4. Emphasize or perhaps even explicitly ask to move people's sponsorships from Github to my LiberaPay account.
5. Attempt to migrate some repos to #CodeBerg, perhaps my personal ones to see how things work there.

I also realized that in #SilverBullet there is direct support for pushing files directly into GitHub repositories via GitHub specific APIs. Luckily I just found that @forgejo supports those as well: https://codeberg.org/api/swagger#/repository/repoUpdateFile

@max ik vecht actief tegen AI code contributie “terrorisme” zoals je misschien al gezien hebt. Ik weet nog steeds niet hoe en of zich dat gaat vertalen naar een policy. Er zijn altijd fundamentele en pragmatische redenen om dingen te doen. Met AI heb ik persoonlijk problemen met beide, maar focus met #SilverBullet vooral op de pragmatische problemen: het is vaak troep.

Recently there's some stream of former #logseq users coming to @silverbulletmd this leads to some interesting observations and ideas on what these users miss compared to their previous workflows: https://community.silverbullet.md/t/coming-from-logseq-outlines-and-linked-mentions/290

I remembered that @toolsontech had a series of #LogSeq videos so decided to revisit them. Good to understand what "the logseq way" looks like, to see if we can somehow support it in #SilverBullet, or if that makes any sense at all.

https://www.youtube.com/watch?v=uJclYLS4oHs

Ok, I think I ended up with a 2x indexing speed-up for #SilverBullet (in my space), that's nice.

Obscure bug I randomly hit yesterday when creating a page in #SilverBullet with a "?" in the page name (which is properly URL encoded to %3F): this is rejected by #Traefik as of 3.6.4 by default: https://doc.traefik.io/traefik/migrate/v3/#encoded-characters-in-request-path

Can be re-enabled with:

entryPoints.<name>.http.encodedCharacters.allowEncodedQuestionMark

apparently.