Der Beitrag Solidaritätsadresse für Brosius-Gersdorf: SPD verteidigt „Richterin“ erschien zuerst auf
Here are some details of the new #logseq DB variant (currently in alpha):
discuss.logseq.com/t/logseq-db…
TL;DR:
- you can't edit the #Markdown files directly
- #orgdown support is lost
- EDN export is introduced besides MD export
- sync and RTC require a subscription
- practically, you can't run the sync on your own
- #Zotero no longer part of the core app
If this holds true, I can't endorse use of logseq any more.
I need to migrate other people's setups I was maintaining to a different solution. Too bad as it was the only good #PIM tool option I could find outside #Emacs #orgmode. 😔
Background: karl-voit.at/2024/01/28/logseq…
Logseq DB Unofficial FAQ
WARNING: Logseq DB is still in alpha. Use only at own risk of losing data. This post is for people who have questions about the new database (DB) version of Logseq.Logseq
Roland Häder🇩🇪 likes this.
Sci-fi author Yudhanjaya Wijeratne and I are working on a script that extracts economic concepts from reviews of science fiction novels. We are interested in observing convergences: are there alternative economies that feel believable to several authors? Here is a first shot, using reviews mostly written by myself over the years. Authors reviewed include @pluralistic , @bruces @annaleen, @KarlSchroeder, Kim Stanley Robinson, and others.
edgeryders.eu/t/what-if-we-tur…
What if we turned the sci-fi economics wiki into data?
Many moons later, somehow, the stars aligned, and it came to pass that @yudhanjaya came to visit us in Brussels.Edgeryders
reshared this
DEV-005-25
#art #ConceptSketching #DailySketch #drawing #FediArt #MastoArt #ScienceFictionArt #SciFiArt #Sketch #SketchBook #sketching #StoryTelling #SubOrbitalMachine #SciFi #ScienceFiction #design
Sub Orbital Machine | Science Fiction Art
Sub Orbital Machine is lines of graphite, ink and pixels from a conceptually abstract corner of the science fiction universe.I Am Gerard Thomas
World shares retreat after Trump's order imposing new tariffs on 68 countries and the EU
https://apnews.com/article/trump-tariffs-asia-wall-street-5bf5640b85f63cf7db292d0aaf26e97a?utm_source=flipboard&utm_medium=activitypub
Posted into Asia @asia-AssociatedPress
Want to run AmigaOS 4.1 FE on QEMU easily?
George Sokianos has created Kyvos. Kyvos is a GUI-application that makes installing AmigaOS 4.1 Final Edition extremely easy. No more long command lines – now it’s just a matter of point and click.
You can get AmigaOS 4.1FE for AmigaOne at our dealers.
(1) Cemil Şanlı on X: "🔴 « Vous pouvez user votre salive, je ne vais pas vous répondre ! » me lance la porte-parole du gouvernement. Ma question est simple : n'est-ce pas problématique que d’avoir un lobbyiste #FNSEA comme collaborateur parlementaire puis directeur de cabinet ? #Duplomb #LoiDuplomb https://t.co/06vKyTI9j1" / X
#politique #agriculture #environnement #pollution #corruption #lacorde #guillotine2025
xcancel.com/Cemil/status/19508…
like this
President Donald Trump warned Canada on Wednesday evening it would now be “very hard” for the two countries to come to a trade agreement after Canadian PM Mark Carney announced his intention to recognize a Palestinian state.
“Wow! Canada has just announced that it is backing statehood for Palestine,” wrote Trump in a late-night Truth Social post. “That will make it very hard for us to make a Trade Deal with them. Oh’ Canada!!!”
youtube.com/watch?v=J4O8B76S1W…
🕎 🇵🇸 ☮️
#Gaza #Palestine
#Press #News
- YouTube
Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.www.youtube.com
I don't understand at all why, for example, the EU is so submissive toward Trump. They would rather do business with Asia and other countries that do not threaten and harass them on a daily basis.
VU DANS LA RUE : UN LEXIQUE DU CAPITALISME
«Charges sociales», «flexibilité», «start-up» ou encore «compétitivité» : ces mots ont colonisé le langage pour imposer un imaginaire néolibéral, mais ne sont jamais vraiment définis.
Dans les rues de Nantes ces derniers jours, un «lexique du capitalisme» est apparu sous forme de pochoirs : il propose aux passant-es les véritables définitions de ces concepts capitalistes, directement sur les murs.
Le lexique à voir ici : contre-attaque.net/2025/08/01/…
VU DANS LA RUE : UN LEXIQUE DU CAPITALISME
Dans les rues de Nantes ces derniers jours, un «lexique du capitalisme» est apparu sous forme de pochoirs.B (Contre Attaque)
Contre Attaque reshared this.
Avant de partir en vacances, StreetPress fait le bilan
streetpress.com/sujet/17539581…
"Comme chaque été, StreetPress ferme en août. Avant de partir, on fait le bilan d’une année comme toujours riche et mouvementée.News"
(1) Tribune Populaire🌐 on X: "🚨ALERTE INFO Un soldat israélien témoigne devant la commission de la Knesset. « Nous avons reçu l’ordre des commandants de la brigade Golani le 7 octobre d’annuler toutes les patrouilles le long de la frontière de Gaza de 5h20 à 9h00.. » https://t.co/oSf1YTFKRH" / X
Étonnant non?
Weird uh?
#Israël #Israel #Gaza #7octobre #October7th
xcancel.com/TribunePop23/statu…
Pascal Le Crom likes this.
Roland Häder🇩🇪 likes this.
xro [39C3📞2976]
in reply to Karl Voit • • •Am currently trying #Silverbullet and it's not bad at all. 😊
Clean and simple.
Possibly could have better Phone UI for Todo-Items and PageNames in folders, but it's all extendable anyway....
Maybe you want to fork it and replace the markdown with orgdown? 😁😊
#logseq #Markdown #orgdown #Zotero #PIM #Emacs #orgmode
Blf_tpe
in reply to Karl Voit • • •Karl Voit
in reply to Blf_tpe • • •@Blf_tpe I particularly avoid Markdown as much as I can for reasons.
Furthermore, I don't think that the project will support the non-DB version in the long term.
Alex L 🕊 🇵🇸
in reply to Blf_tpe • • •Logseq DB is a new mode (like MD and Org ones) in which the in-memory database (Datascript) is dumped to disk and used as storage instead of text files. Later MD files will be restored and kept in sync with that DB, so that the two modes becomes one. You can just keep using the MD mode until that moment.
Karl Voit
in reply to Alex L 🕊 🇵🇸 • • •Alex L 🕊 🇵🇸
in reply to Karl Voit • • •@Blf_tpe
Mastodon has not an easy way to tag multiple people that replied to you in different threads. I included you in all replies to make you understand that it's easy to spread misinformation and hard to fix it.
Karl Voit
in reply to Alex L 🕊 🇵🇸 • • •Alex L 🕊 🇵🇸
in reply to Karl Voit • • •@Blf_tpe
> TL;DR:
> - you can't edit the #Markdown files directly
> - practically, you can't run the sync on your own
This is TEMPORARY (and optional). Yet in the comments there are people that want to move away because of this.
Karl Voit
in reply to Alex L 🕊 🇵🇸 • • •@alxlg @Blf_tpe I'm sorry. This contradicts the linked FAQs and therefore your information is your personal assumption unless this gets at least put on the roadmap.
Don't blame me for spreading misinformation unless you can prove your personal assumptions.
My personal assumption - if you'd like to know - is that logseq is trying to become a Obsidian-rip-off with limited functionality unless you pay. This would be a fundamentally different project goal then. I won't bet my data on that.
Besides: you realize the downsides of your habit of copying the same answer to different sub-threads instead of using links? 😜
Blf_tpe
in reply to Karl Voit • • •Karl Voit
in reply to Blf_tpe • • •@Blf_tpe @alxlg It's not about replying to several people with one message.
If you open the whole(!) thread, you'll notice that he began to post identical messages to multiple sub-threads. This is what I meant and criticized.
Alex L 🕊 🇵🇸
in reply to Karl Voit • • •@Blf_tpe
Mastodon (or ActivityPub in general, I can't remember) has a fundamental issue that makes threads inconsistent across instances: depending on which instance you are and how well they are connected you will see different sets of replies.
Alex L 🕊 🇵🇸
in reply to Karl Voit • • •@Blf_tpe
You linked an UNOFFICIAL FAQ (it's literally the title) and it doesn't contradict the official announcement from more than one year ago:
discuss.logseq.com/t/why-the-d…
> Are you going to deprecate Markdown files support?
> No, we’ll continue to support both file-based and database-based graphs, with a long-term goal of achieving seamless two-way sync between the database and markdown files.
This has been discussed many times for 1.5 years.
Why the database version and how it's going?
LogseqAlex L 🕊 🇵🇸
in reply to Alex L 🕊 🇵🇸 • • •@Blf_tpe
It's also in the roadmap:
trello.com/c/0hUluTN4/1128-dat…
> Experiment with two-way sync between db and Markdown files
Trello
trello.comKarl Voit
in reply to Alex L 🕊 🇵🇸 • • •Alex L 🕊 🇵🇸
in reply to Karl Voit • • •@Blf_tpe
So are you now going to fix your original post with official statements and roadmap?
Or are you really that kind of person that will try to depict Logseq team as evil just because they choose to support Markdown instead of your preferred Org?
Karl Voit
in reply to Alex L 🕊 🇵🇸 • • •@alxlg @Blf_tpe Excuse me?
I never wrote that the team is evil.
I won't change my original post as everything is exactly as I wrote. You can't change my personal preferences, my judgment on future experiments of the project or endorsements.
Another allegation like that and I need to report your account to your instance moderators so that they decide on your way of communicating.
You should not follow my account of my blog because I'm about to publish a series of articles about Markdown and its lock-in-effect despite being human-readable. 😉
Alex L 🕊 🇵🇸
in reply to Karl Voit • • •@Blf_tpe
1. You asked what was misinformation in your post. And I explained.
2. You said those were my personal assumptions. And I provided you the official announcement and roadmap.
3. You replied by changing the subject... out of embarrassment maybe?
4. Now you threaten to report me to silence me instead of fixing your original post.
I think you are a despicable person and a fascistoid. I will just block you: problem solved.
GaryO
in reply to Karl Voit • • •Karl Voit reshared this.
Mike Hostetler
in reply to GaryO • • •GitHub - protesilaos/denote: Simple notes for Emacs with an efficient file-naming scheme
GitHubKarl Voit
in reply to Mike Hostetler • • •@mikehoss @oberbrunner Thanks for the tip.
I know denote and I don't see any use for me as I do have bi-directional links longer than denote exists: karl-voit.at/2020/07/22/org-su…
Since I'm using Org-mode for way over a decade, I think I'm settled.
The logseq setups in question are the one of my wife and my father. Both may not be very happy with an Emacs-based solution, I'm afraid.
UOMF: Linking Headings With org-super-links (Poor-Man's Zettelkasten)
public voit - Web-page of Karl VoitAlex L 🕊 🇵🇸
in reply to Karl Voit • • •It's not like that. The real TLDR is:
Logseq DB is a new mode (like MD and Org ones) in which the in-memory database (Datascript) is dumped to disk and used as storage instead of text files. Later MD files will be restored and kept in sync with that DB, so that the two modes becomes one. You can just keep using the MD mode until that moment.
About Org mode I doubt it will be maintained.
Karl Voit
in reply to Alex L 🕊 🇵🇸 • • •@alxlg With users not being able to edit the text files (only one-side export, no 2-way-sync), a lot workflows die.
Furthermore, I won't use Markdown for good reasons.
Given totally different requirements, logseq may be fine. However, I have carefully collected my requirements where logseq will be dead to me. Unfortunately.
Alex L 🕊 🇵🇸
in reply to Karl Voit • • •> With users not being able to edit the text files (only one-side export, no 2-way-sync), a lot workflows die.
Again:
**You can use MD mode until the DB mode regains the ability to use MD files as storage.**
I don't care if Logseq is good for you or not because of MD/Org. I am just trying to fix misunderstandings so that some people can keep using Logseq.
Alex L 🕊 🇵🇸
in reply to Karl Voit • • •> With users not being able to edit the text files (only one-side export, no 2-way-sync), a lot workflows die.
Maybe it was not clear enough:
I am not talking about the current export to MD feature. I am talking about 2-way-sync.
This whole transition to DB on disk is to decouple these two operations:
RAM <-> disk
Logseq's internal data structures <-> MD
Because currently they are mixed and the root of many issues.
Alex L 🕊 🇵🇸
Unknown parent • • •Logseq DB is a new mode (like MD and Org ones) in which the in-memory database (Datascript) is dumped to disk and used as storage instead of text files. Later MD files will be restored and kept in sync with that DB, so that the two modes becomes one. You can just keep using the MD mode until that moment.
Karl Voit
in reply to Alex L 🕊 🇵🇸 • • •Alex L 🕊 🇵🇸
in reply to Karl Voit • • •@norberteder
Mastodon has not an easy way to tag multiple people that replied to you in different threads. I included you in all replies to make you understand that it's easy to spread misinformation and hard to fix it.
Alex L 🕊 🇵🇸
Unknown parent • • •@norberteder
There won't be several storages in the end. There will just be MD files.
This whole transition to DB on disk is to decouple these two operations:
RAM <-> disk
Logseq's internal data structures <-> MD
Because currently they are mixed and the root of many issues.
Karl Voit
in reply to Alex L 🕊 🇵🇸 • • •Alex L 🕊 🇵🇸
in reply to Karl Voit • • •> TL;DR:
> - you can't edit the #Markdown files directly
> - practically, you can't run the sync on your own
This is TEMPORARY (and optional). Yet in the comments there are people that want to move away because of this.
Karl Voit
in reply to Alex L 🕊 🇵🇸 • • •@alxlg @norberteder I'm sorry. This contradicts the linked FAQs and therefore your information is your personal assumption unless this gets at least put on the roadmap.
Don't blame me for spreading misinformation unless you can prove your personal assumptions.
My personal assumption - if you'd like to know - is that logseq is trying to become a Obsidian-rip-off with limited functionality unless you pay. This would be a fundamentally different project goal then. I won't bet my data on that.
Besides: you realize the downsides of your habit of copying the same answer to different sub-threads instead of using links? 😜
Alex L 🕊 🇵🇸
in reply to Karl Voit • • •@norberteder
You linked an UNOFFICIAL FAQ (it's literally the title) and it doesn't contradict the official announcement from more than one year ago:
discuss.logseq.com/t/why-the-d…
> Are you going to deprecate Markdown files support?
> No, we’ll continue to support both file-based and database-based graphs, with a long-term goal of achieving seamless two-way sync between the database and markdown files.
This has been discussed many times for 1.5 years.
Why the database version and how it's going?
LogseqA. Sebastian Dietzel 😎🥳
in reply to Karl Voit • • •Karl Voit
in reply to A. Sebastian Dietzel 😎🥳 • • •@dietzel My file sync solution of choice for everything is Syncthing.
So if a tool is able to deal with changes on file level, it doesn't re-invent the wheel by implementing its own synchronization mechanism using a cloud I don't trust anyway.
So I circumvent the issue otherwise than via E2EE and a public cloud: Syncthing is using E2EE without a public cloud.
HTH
Simon Dückert
in reply to Karl Voit • • •Nils Müller
in reply to Karl Voit • • •I am a little confused. In your article you state, that use use Logseq to avoid vendor lock-in. Yet, now you have to migrate several setups because of a "vendor" decision...
So where's the advantage of non-vendor-lockin compared to a more closed solution with full data access (e. g. Obsidian)?
Karl Voit
in reply to Nils Müller • • •@Weltenkreuzer
Usually there is no such fundamental change, turning a whole project in something different, losing ways of working with that tool such as generating content externally which then gets re-used in the tool via bi-directional file sync.
Advantages of FOSS:
I may run the old version as long as I like.
I can look up the details of parsing or writing in the source & re-use that knowledge myself.
I may fork the project & continue with the fork.
Since I prefer a migration to the effort of above processes, I chose migration.
I never wrote that FOSS has no lock-in. I only wrote that I want the lock-in effects of closed tools like Obsidian.
Using FOSS doesn't mean that there is no lock-in.
Same goes for the data format: using proprietary (but human-readable) Markdown doesn't mean that there is no lock-in.
However, the downsides of a closed solution like Obsidian are pretty obvious to me - as with all proprietary software solution out there.
Karl Voit
in reply to Nils Müller • • •The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy
public voit - Web-page of Karl Voit