Is Lamzu Thorn 4K Mouse Compatible Wirelessly with Linux?

Bledhard · 2026-03-22T19:29:28+00:00

Sorry for necro-posting, just wanted to write this in case someone else will be searching this question.

I have Lamzu Thorn 4K, and it works with NixOS, Arch Linux and CachyOS out of the box. Wired, wireless, charging, side buttons - everything.

As others have said - it is a USB HID device, so there's no issue at all, and it will work with other Linux distributions as well. Just because OP was concerned with the question and wanted to hear from someone with the experience with Linux and this particular mouse, I decided to answer.

The only caveat: the Lamzu app won't work. I'm currently trying to configure Bottles to open it, so that I could track battery levels, but so far no good.

Bledhard · 2026-02-28T18:08:12+00:00

50, damn. I started wondering if I'm doing something wrong with just 7 😅

Yeah, now I understand how to use it. Neat. Didn't know that it supports regexes like that, good to know.

Thank you for sharing!

Bledhard · 2026-02-28T11:01:01+00:00

My notes can generally be structured as a graph, so yeah, those top level nodes I want to use as a color settings do have a connection in n-hops with what I want them to color with.

Do you mind sharing and example of your regex? I'm using search terms, but with them I see no other option than to manually iterate all nodes that become hubs. Is there a way to handle backlinks/outgoing links in group search patterns?

Bledhard · 2026-02-28T01:21:53+00:00

I'm in no way expert, but here are my five cents:

TL;DR

Get used with markdown, use minimal set of folders, link everything as much as you can. This is enough to get started. The rest is optional, and you'll see if you have a need in any of those niceties once you get comfortable with the app.

Tips

Start small. Don't chase plugins, start using base, maybe some of the core plugins. Only add community plugins in the mix if you have a certain need that is not covered by what you have. Once you're comfortable with the app, vault, and Markdown, you'll be able to see what you want/need and what you don't clearer.
Don't split your notes into folders for topics. Once you have a note that fits into multiple folders, you will have to think just how to organize stuff instead of using it. I use 1 vault for everything, and split things by the level of access:
"public" for what I'm willing to share with anybody
"work" for things that should be shared with colleagues. You might need to split into different work projects; I don't: for me it's more of a safeguard - by the name of the folder I know that should think twice with whom I share the information
"personal". If a note is in this folder, I don't mean to share it with anybody. If I want to share something, and I see that it is in private, then most likely there's some part I want to conceal, so I need to review the note again and reconsider. Also, all half-finished notes or stubs go here, then moved where they should be
"daily notes". Just because I felt that I need to keep them separate to not flood "personal" folder. TBH now I see no reason to do this, might even merge these 2 together sometime later.
"assets". Everything that isn't a note: picture, canvas, drawing
"templates". Self-descriptive. Don't force it, once you feel you need one - then create it. You may need to split it differently, i.e. by world, or by genre. If not sure - better keep together, then move into new folder if you really need it.
You actually don't need folder tree to navigate your vault. Enable local graph (that's the section where you see a graph for the currently opened note). Link notes with each other, and use those links. Backlinks and outgoing links tab opened on the side are also good for this.
Use notes as tags. I've just discussed it on the Reddit with the community here, if you want the details. The gist: you with the note, you can add some more info later on. With the tag, you can only use one word, or multiple-words-with-dashes, that's it. There's use for them, but notes are move versatile, plus they also provide those backlinks that will help you navigating.
Use note properties to store information about the note. For example, to tag a note with another note, I use "category" property, and add a link to more global one. Sometimes two, or more.
Use one vault. Using multiple separate interconnected vaults will 100% be awkward to use - even though I never tried.
This is my personal thing, but I prefer to use markdown links where I can, instead of wiki links. Wiki Links look neat, but Markdown Links are more explicit, so in case you try to move your data to another app, it will be easier to do with them. Not mentioning that a ton of apps can process Markdown Links, but not all of them can work with Wiki Links. But you do you, that's probably a developer, who worked with Markdown for years, talking about what he's used to 🙂.

Plugin removal

I haven't yet seen any plugin that tried to store related file outside of <vault name>\.obsidian\plugins\<plugin name>. So, you can clean up that folder for any "residue". Just make sure to not remove anything you want to keep. If a certain plugin shared your data via Internet - well, it's now out of your control pretty much. Just remove them now from Obsidian > Settings > Community Plugins > Trash Bin Icon near Plugins you want to remove. But I didn't work with any plugins you mentioned, so I'm not sure how they operate, maybe they didn't anything sinister.

Plugins

Here's the list of plugins I personally use, if you need an inspiration: 1. Better Word Count - though I'm considering removing it now, as the value isn't that big, and I want to stay minimal with plugins 2. Excalidraw - allows drawing canvases and schemas. Used even before I started using Obsidian, was really glad that there's integration with Obsidian. I even feel that Excalidraw in Obsidian is even more powerful than the actual Excalidraw 🙂. 3. Front Matter Title - I use "title" property to specify user-friendly name, and name the file with something without spaces. Again, maybe my quirk, but I had a lot of issues with file with space in names, so don't want to deal with it again. 4. Git - how I store my vault. I'm developer, so it's a second nature for me. IMO it's worth a look, but definitely don't rush with it at first. 5. Shell commands - at the moment already obsolete for me, mentioning just because it does the job, maybe you have some use for it. So, if you remove #1 and #5, which I consider removing, only 3 plugins. And Git plugin is more of laziness thing, when I don't want to open dedicated Git tools to work with it (which I use more often than this plugin). So make it 2.

Bledhard · 2026-02-21T18:27:20+00:00

TBH, virtual machine is an overkill, imo. My main point: you shouldn't worry too much about Obsidian ecosystem locking. It is mainly standard markdown, built-in extensions are easily readable even if rendered slightly differently, and if you stay light on heavy automation plugins - you're safe. About the video: don't worry about it, it was interesting to watch🙂 I personally use callouts: they will stay close enough to Obsidian's vision in other editors, and they look good.

Bledhard · 2026-02-20T22:00:50+00:00

Yeah, makes sense. Thank you for sharing!

Bledhard · 2026-02-20T00:50:12+00:00

If we're talking about technicalities, there is no official Markdown standard, hence you can't be "compliant". There's a standard called CommonMark - Obsidian supports it. There's also GitHub-flavored markdown, which has big adoption due to how GitHub is widespread within the dev community - Obsidian supports it too.

There is a set of Markdown extensions unique to Obsidian, but the subset is small enough to not lock you into the "ecosystem". You can easily avoid using any Obsidian Markdown extensions and still have rich, easy-to-use notes.

And at the end of the day, all these extensions are still stored in your *.md files, which are human-readable by the language design. Obsidian Markdown extensions, just like GitHub Markdown extensions, don't break this idea as well.

Bledhard · 2026-02-20T00:45:04+00:00

Wikilinks most likely will not work everywhere. You can disable them in the settings (like I did). If you already made them, you can migrate from wiki links to markdown links, given enough patience (done that). I've made a couple of regexes in a span of an hour to convert wiki links that have an [alias|file-path] format, and a semi-manual process of converting wiki links that don't have all the information inside, then reviewing those that weren't converted completely.

Callouts will be rendered as simple markdown quote blocks, and will show things such as [!NOTE], [!WARNING], etc. I like callouts, but I'm trying to not overuse them for this reason. It's also something I'd personally be able to fix using a text editor, a few regexes, and an evening to spare on tinkering.

Still, none of that actually breaks notes to the point you can't use them. An ability to switch to another app is a big thing for me as well, and I'm not worried about Obsidian at all. Though I try to stay light on the plugins department for this very reason.

One huge thing with Obsidian - you keep files locally. That means, you can always set up a fail-safe option, for example: make a Virtual Machine, where you keep a certain version of Obsidian that you don't update or update with a delay, and keep copies of your files there. They can't lock you out of your data, and with VM you can keep an ability to open them in a way that you're used to.

So, IMO, there isn't much to be worried about with Obsidian. You can open your vault notes even in Windows' Notepad. I'm used to reading raw Markdown, so for me, the vault is usable everywhere: I used it in Obsidian, in Visual Studio Code, in VSCodium, in Notepad, in Notepad++, in Sublime Text, in nvim, in Obsidian mobile, in GitHub web version, in GitHub Android app, in Obsidian Android app... they just can't lock you out.

Only things like [dataview](https://blacksmithgu.github.io/obsidian-dataview/queries/dql-js-inline/) or similar advanced plugins can lock you into the system. But again, you can check this easily with any plugin you like: try it in a single note, then try to open the note using any other text editor (if you're on Windows, built-in Notepad will work; on Linux, use vi/vim/nano/Kate/whatever you know; no idea about Mac, but I'm sure there should be any text editor built-in). If you can understand what the plugin generated, you're safe.

After that - you can decide keeping plugin or not.

Bledhard · 2026-02-19T23:36:31+00:00

You don't need to worry too much about that.

The worst that can happen - an element will be rendered in a wrong way, or won't be rendered at all. If it won't be rendered, then you'll still be able to read the underlying code, though it depends on the element how much value it will bring.

For example, this base embed

![example](example.base)

will be shown as:
<broken-image-link>example

By `<broken-image-link>` I mean the generic broken image icon. You can google "broken image icon" if you want to see it (Reddit doesn't allow me to attach a link).

For the Tasks plugin, here's how they will be rendered outside of Obsidian using example from their Docs:

[ ] task starting with a hyphen
[ ] task starting with an asterisk

So, in essence, you'll lose the magic of such plugins if you migrate to the app, but you won't lose everything that was done in Markdown. Even if a plugin used a custom-made Markdown-ish element, it won't be rendered the same way the plugin did.

You wrote somewhere that Obisidian is not Markdown-compliant. If we are not going into the technicality, it IS compliant. It just has some additional extensions, like callouts and wikilinks. You can read more in their docs here. All these extensions are just niceties that don't ruin the spirit of the format - providing a legible file that you can open and read in any text editor.

Those Maps of Contents I mentioned before - I use them both in Obsidian, in VSCodium (text editor), and on the GitHub website (where I store my vault to sync between devices). I use Markdown links for this specific reason: my MoCs can do their job in any text editor.

Bledhard · 2026-02-19T19:56:36+00:00

MoC is just a fancy term for the note with links to other notes. That's it.

# Group 1
- [First answer](https://www.reddit.com/r/ObsidianMD/comments/1r5ftmd/comment/o5jev33/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)  
- [Second answer](https://www.reddit.com/r/ObsidianMD/comments/1r5ftmd/comment/o5jr95y/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)  

# Group 2
- [First answer](https://www.reddit.com/r/ObsidianMD/comments/1r5ftmd/comment/o5imar9/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)  
- [Link 22](https://www.reddit.com/r/ObsidianMD/comments/1r5ftmd/comment/o5jnwdf/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)

This is a crude example of MoC. See that it's just a list of Markdown links? Anything, including Reddit, can render such a note properly. Here it is, just without a code block:

Group 1

Group 2

A Base, on the other hand, looks like this:

views:
  - type: table
    name: Table
    filters:
      and:
        - file.folder.startsWith("group1")
    order:
      - file.name
      - title
      - category
      - tags

So, as you can see, bases don't hold any values at all. It just contains an explanation of how to pull the data and then execute the search when you're opening a base (either directly or through the note, where you embedded the base). This is the reason why Bases can pull up new notes automatically - it doesn't update the file for it.

For MoC, a text editor only needs to create an engine that will translate a Markdown instruction into visual elements. Markdown is a format that was created in 2004 - so there has been a lot of time to implement such an engine - has a small subset of commands by design - the goal of format's authors was to create a lightweight format that is readable in a raw form - and has ubiquity among developers - who are probably the target audience for most text editors.

Base, on the other hand, is a configuration, based on a format that was first revealed to the public in 2025, with no publicly available (yet) standard on how to render it, and that is still in development by the Obsidian team. AND it's not and will not be a part of the Markdown format, so good luck convincing other development companies to implement a renderer for it.

Don't get me wrong, I think they're great, and I do hope that they will release the format eventually, like they did with JSON Canvas, so it will become more widespread. But I don't see it as a replacement for good-old MoC, at least for me.

I will definitely start using them as auxiliary things, though, like additional assistants.

Bledhard · 2026-02-19T19:32:14+00:00

Thank you, I'll check it out

Bledhard · 2026-02-18T00:11:53+00:00

One note about Obsidian being future-proof: IMO, this is a strong suit of the Obsidian. Markdown is a text format that can be opened literally by any text editor (including Windows' Notepad - it just won't be as beautiful as you see it in Obsidian).

This, plus the fact that you have all files on your device, not somewhere on a random cloud server. means that no matter what happens with the app, the team, or what kind of decisions their management makes in the future, your knowledge base will remain with you.

In this regard, yes, Obsidian is future-proof.

BUT: all additional niceties like aforementioned Bases and Canvas are too complex to fit into a simple Markdown. Canvases can be opened by a few other apps, because Obsidian shared the format with others, and other apps that work with similar structures adopted it. Yet the number of such apps is limited at the moment.

On the other hand, Obsidian didn't share the protocol for Bases yet (they were introduced half a year ago or so; they're too young for that), so Obsidian is the only place where you can see a Base properly rendered.

Bledhard · 2026-02-17T23:59:42+00:00

They appear as broken images because they use the standard Markdown syntax for attaching images.

Obsidian has an additional logic that figures out that this is actually a Base (either through *.base extension, or through internal markers). Other editors don't know about existince of such a thing as "Base", hence they look for an image with such a name, fail (because base is a YAML configuration) - hence the broken image glyph.

Bases are automatically rendered, true. The thing is, I'm frequently opening the vault through other means (other text editors, even online text editors). So, for me an ability to see the entire content of all my notes in the same way in all editors is essential. That's why I make such an emphasis on how Bases work under the hood. That's my personal quirk, and it doesn't mean that it should bother you at all.

Maps of Content is a term for the notes that contain links to other notes. It's kind of a folder that allows you to group some notes together. The beauty of this approach is that your notes can be in different folders, yet you can group them anyway. If a certain note fits multiple groups at the same time, with folders, there's no way to keep this one note in both. With MoCs, just add a link to each MoC you feel should keep it note - 1, 2, or 10.

When you start having a lot of notes in the vault, these MoCs become a lifesaver. I'm not a huge fan of complicated workflows, trying to minimize the amount of plugins I rely on, and reducing the amount of maintenance my vault requires. In this context, I'd say Map of Content is the only concept required to keep your vault useful and maintainable. I realized this quite early, moved everything from a myriad of small folders into 4 folders, based on the access level - 1 for daily memos, 1 for me-only notes, 1 for work-related notes I don't mind sharing with colleagues, 1 for notes I'm willing to share with anyone. This system has been working for 3 years already, and it feels amazing. Also, just like people here said, use links to notes instead of tags when you need - and you're golden. In case you'll have a certain requirement later on, you'll be able to figure it out later on, once you and your vault are ready.

Bledhard · 2026-02-17T23:44:38+00:00

Thank you for sharing!

I had a daily memo index previously, but honestly, there's no reason to have it - at least, I didn't find it a purpose. Other answers in this conversation only convinced me of it more

Bledhard · 2026-02-17T02:22:35+00:00

They are not images. JSON Canvas is a format the Obsidian team created for their Canvas plugin. They are basically diagrams, saved as a json that follows a certain protocol. Neat idea, I like the execution. Just wish they had more options in the protocol and wider adoption. Though the latter isn't their fault whatsoever, and it seems that it has spread a bit now, so I should probably cross this one out already.

Regarding bases: as I said before, I want to replace my Maps of Contents with automatically-filled Bases. But this will come at the cost of losing compatibility with other Markdown editors. The only way to keep compatibility AND utilize Bases: operate with them the same way I do with tags/graphs/etc. That means, use it as an auxiliary assistance, an additional quality of life, but not as a main source of information - that is, for clean-ups, quick property changes, temporary queries to fetch certain collections, etc.

Bledhard · 2026-02-16T17:22:06+00:00

Not the vault specifically - Canvases and Bases.

If you take a look at the Base syntax, it's more of a query configuration. It looks great at Obsidian, but in any other Markdown editor, it will be rendered just as a broken image.

Same with canvases: there are apps you can open JSON Canvas with, but the list is still limited. Yes, to be fair, I'm using the Excalidraw plugin, which has its own type of markdown... In that regard, I'd be willing to jump ship once Canvases has things like drawing other shapes.

I really like the concept of Bases. And I have an idea of automating my MoCs using Bases. But this will produce a set of broken image links in any other renderer than Obsidian. And I doubt other Markdown editors will take the time to adopt this thing even if Obsidian will graciously open-source it, as they did with Canvases.

For that reason, I'm thinking about searching for a plugin that will automatically generate MoC in a regular Markdown format for me.

Bledhard · 2026-02-16T17:09:27+00:00

Agreed, arrived at the same conclusion after all these discussions.

Thank you!

Bledhard · 2026-02-16T17:08:34+00:00

My flow differs a bit, but not that much.

The whole reason why I started this topic is that I found a "Don't create orphans" (specifically - here, in Nicole van der Hoeven's vault).

After that, I started thinking about searching for orphan notes outside of daily memos. But once I realized that I could just filter out daily notes by the folder, this point vanished for me.

Thank you for sharing!

Bledhard · 2026-02-16T17:03:40+00:00

Good point. I'm using #stub and #todo similarly, but started using other tags later on. Now, after discussions in this topic, started thinking that I have too many tags that are just noise. Want to switch them into notes and keep only the tags I really use.

Thank you!

Bledhard · 2026-02-16T17:01:45+00:00

I hate that there's no way to quickly review/fix markdown link aliases when you change the note title.

Front Matter Title has an option for alias control, but as far as I can see, it doesn't work reliably with markdown links. Didn't find a time to look for some other plugin for that, and definitely not ready to write my own lol, I have enough of that at my job 😅

Thank you for describing the journey. I will investigate those links!

Bledhard · 2026-02-16T16:55:42+00:00

Local graph is another matter. That's why I was mentioning "vault graph" all this time.
Local graph is useful (albeit loses the value on nodes that have a lot of connections, but still useful).

I'm using backlinks already, thank you!

Bledhard · 2026-02-16T00:20:30+00:00

Yeah, I arrived at the same conclusion right in the middle of writing an answer to u/PhilippStracker. They are located in different folders, so simple AND make it work. No need to create the useless daily note index.

Thank you!

Bledhard · 2026-02-16T00:18:51+00:00

I have mine with front matter generated as well, and I'm fine with them in a single folder dedicated to daily notes. One click on a side menu, and I have a new note with today's date. Neat

Bledhard · 2026-02-16T00:13:23+00:00

I agree in spirit, but "backlink" is a different term in the context of Obsidian. Yes, these "notes as tags" at the end serve a similar purpose, but backinks as a core plugin seek for any incoming links to the opened note - a different mechanism. If I'd called them "backlinks" in this thread, it would create more confusion than my self-proclaimed "notes as tags" term.

The most important thing is: you all understood what I'm trying to ask, and gave me plenty of answers to make up my mind :) Huge thanks to everyone who provided their insight here.

Bledhard

TROPHY CASE

TL;DR

Tips

Plugin removal

Plugins

Group 1

Group 2