this post was submitted on 20 Feb 2025
683 points (98.0% liked)
Technology
63082 readers
3563 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I actually find the lack of distinction between a tag and a wiki link a breath of fresh air. So many other apps make a meaningless distinction between them and make you choose ahead of time a styleguide for how you plan to use both. Logseq makes a queryable style enforced and then you adapt to using it. Very different
Yes, but the syntax and documentation on the queries is obtuse as hell in logseq. Like it is ridiculous how granular you have a to get of you want to return all links within a time period or something. If I need to write SQL to pull notes, I should just use a database, lol.
The nice thing about tags as a distinct entity is it offers the option you can utilize if you choose. It gives you two buckets you can sort into and connect between. And it does make creating "topic groups" easier than manually linking them all to a tag page in logseq, imo.
Conversely, I would massively prefer of Logseq abolished support for hashtags entirely if they are functionally identical to wikilinks. Or combine them so the hashtags auto-convert to wikilinks or vice versa. But supporting hashtags in any manner when they are frankly not a "real" feature is more frustrating. Making topic links in Logseq is harder because of this.
Also, the existence of tag pages themselves is a confusong abberation given the above...
Logseq is a great tool, but very different in terms of what it is best suited to handle. I think I will revisit it for if I do a lot of writing, but for disparate ideas or notation it is good but could be better.
Just because other tools use # in other ways doesn’t mean they aren’t useful the way they are now in Logseq. It’s just a one character shorthand rather than four characters. I find tags as they are in Evernote and Obsidian exceedingly worthless for all but the most strictly organized individuals, not so in Logseq. Call them what you will.
A query is helpful when you need it, but rarely needed.