home.social

#logseq — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #logseq, aggregated by home.social.

  1. Ich bin jetzt schon einige Zeit dran, alle meine Aufgaben und Projekte sowie die größeren Ziele im Leben in #Logseq zu pflegen. Gerade bei Projekten möchte ich auch die zeitlichen Aufwende tracken. Das kann Logseq zwar auch, aber #TimeTagger scheint mir dafür viel besser geeignet zu sein. Klappt auch prima mobil mit dem Smartphone.

    Vielleicht blogge ich dazu bald mal was. Bis dahin einfach mal die Demo anschauen tt.z3h.de/timetagger/app/demo

  2. "Kinda like #logseq, but in two dimensions instead of one" is how I would attempt do describe #TreeSheets
    strlen.com/treesheets/

  3. Managed to get both #syncthing and #logseq up and running on my #Uconsole. Quite pleased this is now possible.

  4. Logseq Brain v0.6.0 released!

    Claude's persistent memory plugin now:

    - Journey Log — every save/load lands as a bullet in today's journal
    - section-targeted Reads — real token savings on big project pages
    - sharper skill descriptions

    GitHub: github.com/jame581/LogseqBrain

    #openSource #AI #AIAgent #ClaudeCode #logseq

  5. The (mental) model behind #Logseq is really nifty and might work for my brain. The current beta of the new "DB" branch works pretty well already, UI wise.

    *But* the pivot away from plain text storage ("Markdown extended") is removing one of the major selling points of these tools.

    I really like SQlite, but the way Logseq DB is using it, a single key-value table with basically all data stored in the highly app-specific structured value field/DSL, doesn't promise a lot of interoperability. 😟

  6. And... officially has a split product with db and og. It could work.

    But honestly.. I'm kind of liking obsidian now. 🫠 Sure it does 0.1 of what logseq can do. At the same, maybe that's ok? 😅

    Like if you enrich frontmatter, use tags, and follow principles, obsidian can do a lot.

    You don't need an everything tool. Just enough flexibility to shape your needs. 😉

    logseq.io/page/b2ad9ce1-9cb7-4

  7. @groberschnitzer What a huge fail. 👎

    File-based work was 100% the main reason for the great popularity.

    Any plans for a file only fork?

    #logseq

  8. The file-based markdown version of #logseq is officially put into maintenance-only mode or rather fully retired. The software has not even reached version 1.0 and will be stopped being developed.

    Sadly that's what many warned of, when the devs started working on the database version.

    logseq.io/page/b2ad9ce1-9cb7-4

  9. "Capacities" gefällt mir wirklich gut.
    Eigentlich genau das, was ich lange gesucht habe.
    Aber ZeroKnowledge / E2E wäre mir für eine dauerhafte Lösung schon wichtig. (Trotz Servern in der EU)

    #Obsidian #Noteplan #LogSeq

  10. @chiply @petrillic Unfortunately, the syntax #logseq is producing in Org-mode setting is far from being the same as how #Emacs is creating syntax elements: karl-voit.at/2024/01/28/logseq

    Reading logseq files in Org-mode is probably fine. Modifying Org-mode generated/modified content in logseq most probably has some issues.

    I've set up #logseq for my wife, now as logseq is going south (adding DB, losing org support, unclear future of file (sync) access,...) and I do have a medium-sized conversion problem with her data. 😞

    It's better to start with #Orgmode right away: karl-voit.at/2020/01/20/start-

    #orgdown #publicvoit #PKM #PIM

  11. @chiply @petrillic Unfortunately, the syntax #logseq is producing in Org-mode setting is far from being the same as how #Emacs is creating syntax elements: karl-voit.at/2024/01/28/logseq

    Reading logseq files in Org-mode is probably fine. Modifying Org-mode generated/modified content in logseq most probably has some issues.

    I've set up #logseq for my wife, now as logseq is going south (adding DB, losing org support, unclear future of file (sync) access,...) and I do have a medium-sized conversion problem with her data. 😞

    It's better to start with #Orgmode right away: karl-voit.at/2020/01/20/start-

    #orgdown #publicvoit #PKM #PIM

  12. @chiply @petrillic Unfortunately, the syntax #logseq is producing in Org-mode setting is far from being the same as how #Emacs is creating syntax elements: karl-voit.at/2024/01/28/logseq

    Reading logseq files in Org-mode is probably fine. Modifying Org-mode generated/modified content in logseq most probably has some issues.

    I've set up #logseq for my wife, now as logseq is going south (adding DB, losing org support, unclear future of file (sync) access,...) and I do have a medium-sized conversion problem with her data. 😞

    It's better to start with #Orgmode right away: karl-voit.at/2020/01/20/start-

    #orgdown #publicvoit #PKM #PIM

  13. @chiply @petrillic Unfortunately, the syntax #logseq is producing in Org-mode setting is far from being the same as how #Emacs is creating syntax elements: karl-voit.at/2024/01/28/logseq

    Reading logseq files in Org-mode is probably fine. Modifying Org-mode generated/modified content in logseq most probably has some issues.

    I've set up #logseq for my wife, now as logseq is going south (adding DB, losing org support, unclear future of file (sync) access,...) and I do have a medium-sized conversion problem with her data. 😞

    It's better to start with #Orgmode right away: karl-voit.at/2020/01/20/start-

    #orgdown #publicvoit #PKM #PIM

  14. @chiply @petrillic Unfortunately, the syntax #logseq is producing in Org-mode setting is far from being the same as how #Emacs is creating syntax elements: karl-voit.at/2024/01/28/logseq

    Reading logseq files in Org-mode is probably fine. Modifying Org-mode generated/modified content in logseq most probably has some issues.

    I've set up #logseq for my wife, now as logseq is going south (adding DB, losing org support, unclear future of file (sync) access,...) and I do have a medium-sized conversion problem with her data. 😞

    It's better to start with #Orgmode right away: karl-voit.at/2020/01/20/start-

    #orgdown #publicvoit #PKM #PIM

  15. @petrillic

    A couple years ago I switched from Obsidian to LogSeq because it has org-mode support OOTB. I really am only using for it's syncing capabilities across devices and availability of mobile apps. It is a far from perfect experience, but the pain is hardly noticeable if you predominantly edit the files in org-mode like me. logseq.com

  16. @itsfoss I wish Logseq had an Edit Lock, so when I'm just looking for something I'm not triggering an edit.

    #Logseq

  17. Start a task in Claude Code on your desktop. Say "save to brain". Walk to the laptop. Switch to Copilot. Say "load MyProject" — everything's there.

    logseq/brain: persistent memory for Claude Code, Copilot CLI & Gemini CLI, stored in a Logseq graph you own and sync yourself.

    Session logs, decisions, plans — all markdown, written surgically so Logseq Sync doesn't cry.

    v0.5 out. Feedback + ideas very welcome.

    github.com/jame581/LogseqBrain

    #Logseq #ClaudeCode #AI #OpenSource #SelfHosted

  18. @anderelampe I use markdown in #logseq. Logseq makes linking between pages super easy which really helps with organization.

  19. Information overload alert 😪

    After 3 tears of using #obsidian #obsidianmd , I wanted to try something lighter and #opensource (important to me). I did some #joplin , some #logseq ...

    I have too many notes where I didn't put a hashtag to categorise the information, didn't migrate everything from one to another... So my stuff is all over the place, not organised, and it drives me nuts 🙁

    At the end of the day, I don't even know which one I'd use. Probably #logseq . maybe I could script something to dump useful content of other apps onto a big note in Logseq, so that a full text find works? #1bigtextfile @ellane ?

    Or go to the shop and buy a notebook!

  20. Logseq Brain is persistent memory for Claude, GitHub Copilot or Gemini.

    A plugin that lets Claude save project context, decisions, and progress into a Logseq graph you own, then load it back in any future session.

    Because Logseq syncs across devices, your Claude context travels with you. Start on desktop and continue on your laptop.

    Just markdown files and four skills: brain-init, brain-load, brain-save, brain-status.

    github.com/jame581/LogseqBrain

    #Claude #Logseq #AI #github_copilot

  21. Logseq Brain is persistent memory for Claude, GitHub Copilot or Gemini.

    A plugin that lets Claude save project context, decisions, and progress into a Logseq graph you own, then load it back in any future session.

    Because Logseq syncs across devices, your Claude context travels with you. Start on desktop and continue on your laptop.

    Just markdown files and four skills: brain-init, brain-load, brain-save, brain-status.

    github.com/jame581/LogseqBrain

    #Claude #Logseq #AI #github_copilot

  22. Logseq Brain is persistent memory for Claude, GitHub Copilot or Gemini.

    A plugin that lets Claude save project context, decisions, and progress into a Logseq graph you own, then load it back in any future session.

    Because Logseq syncs across devices, your Claude context travels with you. Start on desktop and continue on your laptop.

    Just markdown files and four skills: brain-init, brain-load, brain-save, brain-status.

    github.com/jame581/LogseqBrain

    #Claude #Logseq #AI #github_copilot

  23. Logseq Brain is persistent memory for Claude, GitHub Copilot or Gemini.

    A plugin that lets Claude save project context, decisions, and progress into a Logseq graph you own, then load it back in any future session.

    Because Logseq syncs across devices, your Claude context travels with you. Start on desktop and continue on your laptop.

    Just markdown files and four skills: brain-init, brain-load, brain-save, brain-status.

    github.com/jame581/LogseqBrain

    #Claude #Logseq #AI #github_copilot

  24. Started looking into alternatives for #logseq as the #android app keeps crashing. #trilium looks very promising and has more features...but also a steeper learning curve.
    Many thanks to github.com/HG00/logseq_to_tril for the excellent migration script

  25. @afewbugs #logseq can be made to do this. I'd need to look up a little bit of code to plug in, but happy to do so if that would be useful - let me know

  26. Hi #LazyWeb my #KDE on #NixOS no longer differentiates my #Jitsi meet app from my #Logseq windows, and it really messes up my alt-tab / command-tab game. (I do love getting things out of browsers into apps for this reason.) Any quick fixes or contributable fixes (if Logseq is even maintained in the classic, files-based way anymore). Thanks!

  27. I left for .

    The tool continues to work. Yet, I know focus is on database version. Meaning current stable is a bit lacking. 🫠

    What's interesting is how difficult finding an outliner as good as logseq. There's really none.

    Venturing out isn't THAT bad... Let's see in 3 months. 😅

  28. @alxlg @rae The indented list "feature" in #Logseq is both puzzling and a total deal-breaker for me. I also couldn't really understand how you're *supposed to use* the app.

  29. New release of markdown-neuraxis desktop v0.0.11 has collapsible headings/bullets, which I think qualifies it as an #outliner

    github.com/timabell/markdown-n

    Another #SideProject #SmallWin for the love of #FOSS #Markdown #Privacy and #SelfHosting

    I'm hoping eventually this will be a haven for others like me looking for an alternative to the inspiring #LogSeq

    Not ready for dog-fooding yet, but the pieces are falling into place and I'm determined to make it useable!

  30. I really like the decentralized wiki concept of Logseq, but its usability just frustrates the crap out of me.

    - Needs an edit lock per page, so things will stay put when no edits are required. Easy to break things.

    - Make referenced lists to other pages stay put. Touch them and they will change their order, or bump you out while editing.

    - Unknown development timeline.

    I deflected back to Obsidian, but I will see if Logseq DB handles these better. Next year?

    #Obsidian #Logseq #PKM

  31. I've been head down for the past few months this year, working on a major overhaul of Fern, the note-taking, journal, knowledge-management shell script that I made over a year ago. Super excited to be able to share the new project, which is inching closer to v1.

    It's now a beautiful Terminal UI (TUI), written in Go, leveraging the amazing BubbleTea, Glamour libraries. I wanted to make something that could be powerful like
    #Obsidian or #Logseq while keeping the footprint low as possible. Binary is around 28MB and it runs on that much Memory at fresh start.

    Still a bit of a ways off to declaring v1.0 ready, but I'd love love love if anyone wants to be a beta tester of v0.9.0(main). Any feedback, feature ideas that fit your workflow, or bug reports would be hugely helpful.

    If you can't beta test that's okay, just share this with friends who might enjoy it. Boosts are most welcome! Thank you!

    https://codeberg.org/InodeLabs/fern #knowledgemanagement #notetaking #journaling #tui #bubbletea #golang #terminal

  32. Мечтают ли папки с заметками об отдельном бэкенде? От ресерча к MVP

    Привет, Хабр. Несколько месяцев назад я вышел ближе к ночи в магазин и, проходя мимо стойки с яблоками, придумал рабочую мысль, которую, как обычно, скинул себе в Telegram. Дома меня ждал знакомый ритуал: включить ноут, открыть Telegram, скопировать текст, открыть Obsidian, найти нужную заметку с идеями и только после этого вставить мысль туда, где она и должна была оказаться изначально. Меня в тот момент зацепили не сами действия, а их архитектурная странность. Формально мои заметки лежали в обычной локальной папке и принадлежали мне. Практически же доступ к ним был завязан на конкретный десктопный клиент, плагины, sync и костыли. Попробуйте, например, нормально достучаться до своей локальной базы заметок с телефона или прикрутить к ней простую автоматизацию и быстро обнаружите БОЛЬ. Именно тогда у меня появился не ответ, а вопрос: это моя частная боль или уже ставший привычным сценарий у других людей, которые уже ведут большие vault'ы в Obsidian, Logseq, Zim и других PKMS? И если проблема реальна, то чего им на самом деле не хватает — стабильной синхронизации, нормального плагина, ещё одного клиента... или отдельного серверного слоя? Этот текст — не история в духе «смотрите, я сделал notes‑as‑a-service». Хотя соблазн подать его именно так есть, говорить об этом пока рано. Это дискавери о том, как из личной боли, ресерча и создания MVP у меня сложилась гипотеза, что части пользователей markdown‑заметок нужен не новый редактор и не мощные плагины, а бэкенд поверх уже существующей папки с заметками.

    habr.com/ru/articles/1012030/

    #product_discovery #mvp #obsidian #logseq #pkm #pkms #markdown #rest_api #автоматизация #selfhosted

  33. Has anybody ever written a conversion tool from the #orgmode syntax by #logseq to a cleaner version of #orgmode syntax for Emacs?

    Background: logseq has a unique interpretation of the #orgdown syntax as each element is also a heading on its own (in order to allow element references):
    karl-voit.at/2024/01/28/logseq

    I'm happy to lose element references if they are replaced by "page references" instead somehow.

  34. Has anybody ever written a conversion tool from the #orgmode syntax by #logseq to a cleaner version of #orgmode syntax for Emacs?

    Background: logseq has a unique interpretation of the #orgdown syntax as each element is also a heading on its own (in order to allow element references):
    karl-voit.at/2024/01/28/logseq

    I'm happy to lose element references if they are replaced by "page references" instead somehow.

  35. Has anybody ever written a conversion tool from the #orgmode syntax by #logseq to a cleaner version of #orgmode syntax for Emacs?

    Background: logseq has a unique interpretation of the #orgdown syntax as each element is also a heading on its own (in order to allow element references):
    karl-voit.at/2024/01/28/logseq

    I'm happy to lose element references if they are replaced by "page references" instead somehow.

  36. Has anybody ever written a conversion tool from the #orgmode syntax by #logseq to a cleaner version of #orgmode syntax for Emacs?

    Background: logseq has a unique interpretation of the #orgdown syntax as each element is also a heading on its own (in order to allow element references):
    karl-voit.at/2024/01/28/logseq

    I'm happy to lose element references if they are replaced by "page references" instead somehow.

  37. Has anybody ever written a conversion tool from the #orgmode syntax by #logseq to a cleaner version of #orgmode syntax for Emacs?

    Background: logseq has a unique interpretation of the #orgdown syntax as each element is also a heading on its own (in order to allow element references):
    karl-voit.at/2024/01/28/logseq

    I'm happy to lose element references if they are replaced by "page references" instead somehow.

  38. @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: karl-voit.at/2025/08/17/Markdo

    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: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: 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.

    #PKM #PIM

  39. @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: karl-voit.at/2025/08/17/Markdo

    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: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: 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.

    #PKM #PIM

  40. @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: karl-voit.at/2025/08/17/Markdo

    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: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: 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.

    #PKM #PIM

  41. @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: karl-voit.at/2025/08/17/Markdo

    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: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: 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.

    #PKM #PIM

  42. @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: karl-voit.at/2025/08/17/Markdo

    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: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: 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.

    #PKM #PIM

  43. I’ve tried #AppFlowy as a #Notion alternative and while it is close, I’m not quite sold on it yet as I’ve had issues syncing and general stability.

    I’m also trying #Logseq as an #Obsidian alternative. They aren’t quite the same as Obsidian is a markdown text editor with huge customizability, while Logseq is a more focused block-based markdown text editor centred around bullet point notes made in a daily journal. I like the way both function and I’m not sure how to effectively execute a transition to Logseq given how I use Obsidian currently.

  44. Yesterday, I managed to read the whole #Orphans adv. for the #Mothership #TTRPG in about 20-30 min. Although I would like to see a little more structure, as a fan of #LogSeq & #Markdown, I think the very accessible structure is a step in the right direction. #DeltaGreen is welcome to imitate this.

    RE: https://bsky.app/profile/did:plc:xdjqpqlccq57rplc6ulr73rp/post/3meoq75osec2r

  45. RE: graz.social/@publicvoit/115875

    I really do like how #SilverBullet is explaining the consequences of using their version of #Markdown on 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: karl-voit.at/2021/01/18/tool-c

    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.

    #PIM #publicvoit

  46. @ac @ente @elementary That's a interesting tool, it lists many niche options also, like the convenient email provider Migadu 👌 I made one about me too, it was fun! As DNS I usually prefer OpenNIC but it's not listed, I will open a pull request as well

    #migadu #proton #kagi #zenbrowser #simplex #logseq #gopass #aegis #nextcloud #fdroid #homeassistant #osmand #matrix #archlinux #endeavouros #lineageos

  47. RE: mastodon.uno/@giuseppegv/11573

    I like the idea of this post. Here is mine with some additions of my own:

    OS
    - Desktop and laptop
    - #Debian 13 with #Cinnamon
    #homelab server
    - #Proxmox 9 with #Debian and #HomeAssistant OS VM's
    Email
    Service providers
    - @disroot and @Tutanota
    Client
    - #Betterbird
    Notes
    - @logseq
    Browser
    Desktop
    - @librewolf , and @torproject
    Mobile
    - #IronFox
    VPN
    - @mullvadnet
    Password and TOTP Manager
    - @keepassxc with #Syncthing
    Search
    - #DuckDuckGo , @ecosia , and @marginalia
    Social
    - @Mastodon and @pixelfed

    Edit: Today I ran ``` sudo apt remove --purge firefox ``` because of statements from Mozilla CEO today.

    #FOSS #Debian #GNULinux #GNU #Linux #Proxmox #homelab #homeassistant #disroot #tuta #tutanota #betterbird #logseq #Mozilla #Firefox #Librewolf #Tor #Torproject #IronFox #Mullvad #MullvadVPN #VPN #TOTP #KeePassXC #Syncthing #DuckDuckGo #Marginalia #Mastodon #Pixelfed