[-] Rockslide0482@discuss.tchncs.de 1 points 11 months ago

I primarily use logseq but have obsidian configured to use the same directory. I then use logseq for journaling and some tag notes that have searches and links kind of built in. Then I have obsidian for wiki or KB type notes. I can then link to parts of that in logseq. I also use obsidian for a few niche situations where the plugins add value. Its not a perfect solution but it works pretty well for me. I also typically use obsidian to folder directory organize my non journal notes, bit really you could just as easily use your file browser for that.

[-] Rockslide0482@discuss.tchncs.de 2 points 11 months ago

I miss Unity. It never got the love it deserved from a praise nor development standpoint. My typical Gnome desktop typically ends up being a quasi-Unity layout. I need to spin up the latest Ubuntu Unity spin for nostalgia's sake.

[-] Rockslide0482@discuss.tchncs.de 1 points 11 months ago

main thing to note is that NFS is an object based storage (acts like a share) where iSCSI is block based (acts like a disk). You'd really only use iSCSI for things like VM disks, 1:1 storage, etc. For home use cases unless you're selfhosting (and probably even then) you're likely gonna be better off with NFS.

if you were to do iSCSI I would recommend its own VLAN. NFS technically should be isolated too, but I currently run NFS over my main VLAN, so do what ya gotta do

I actually use both Logseq and Obsidian. It's not perfect, but Obsidian is more my knowledgebase and Logseq is my journal and sort of TODO manager. I have them all within the same directory so I can reference my knowledgebase, append to it, etc. from within logseq or the inverse. main issue is since logseq loves the bullet points it tends to whack out my headings and stuff in obsidian made notes

I'm a logseq user of about 6 months and overall really like it. It's mostly built around the daily journal, which mostly works if you lean into it. I basically write what I did, todo's or random thoughts for the day in there. I typically segregate my root bullet points into a handful of main "buckets" like a job, client or project. I used to do those with a hashtag like #job1 but moved to page tags like [[job1]] with sub bullets for main tasks, todos, notes, etc from each. i have many relevant hashtags for relevant subsystems/topics relating to the main ones.

from there I have setup some basic pages for things like [[job1]] with a query to show TODOs with that task (see below), then some relevant reference notes, and sometimes some links to bullets from previous journals if i find i will likely reference them frequently. you also can see below the linked references, which is frequently useful. i also frequently put tags to other tags, pages, etc. within to help map everything together

here's an example of a very basic query I would keep at the top of the [[job1]] page {{query (and [[job1]] (task NOW LATER DOING IN-PROGRESS TODO WAIT WAITING))[[job1]]}}

to your above, you have #workimprovements, you can either just jot those at the root as they come to you and include the full hashtag, or you could have a starting section of either [[workimprovements]] with various ideas below, but i would also suggest adding in other relevant hashtags for subtypes, areas, etc. another tip about hashtags, don't go crazy with them -- too many hashtags just makes a mess -- but don't skimp on them either. If you think you'll use it frequently enough, or at least want to go back and reference it easily in the future, make a hashtag. you can use the hashtag plugin after the fact to find unused and remove hashtags you didn't end up using.

one thing I really wish they would add is similar to hashtags, but for people. Right now, I "tag" people with an @ in front of their name, so I might have @BobS requested X which sort of helps to go back and search for things related to @BobS, but it's not natively done for fully fleshed out. It would be awesome if there was either native or a plugin functionality to more gracefully tie it together

anyway, there's my logseq ramble, hopefully it helps.

Tell me more about your Tumbleweed+NVIDIA problems. I'm on Leap 15.5, but with all this I've thought about moving over to Tumbleweed or Fedora. My card is NVIDIA, so I'm not looking for a big headache.

I don't think it's necessarily universal in US libraries either. I'm not in a big city, but overall our library system is pretty good. They have a number of branches with "maker labs" so there are things like Cricuts, sewing machines, laser cutters, audio recording/production equipment and 3D printers you can rent. I'd recommend at least checking around.

Neat! (As a non-Steam Deck owner but eyeing with desire) I hadn't thought about putting Plex on it.

Man, I learned a TON about the Caribbean sea islands and colonial era big cities from Pirates on the NES. Countless hours spent pouring over this map to find hidden treasure and hunt down leads

http://fandelanes.emu-france.info/images/nop/pirates_nes_carte.jpg

I had to put in extra effort to find a manual (USA), but I was successful. I'm going to hold onto this thing in perpetuity until the wheels fall off or (reliable) fully autonomous vehicles are "standard".

Nice, thanks. I looked before; either I missed it or it was an update feature

Put this on my list of projects to dig into when I have time. I briefly tried Grocy a while back thinking I may be able to use it for inventory mgmt, but it didn't stick. I want to say I found some other self hosted home inventory project at one point but didn't stick with that one either. It's one of those things that I think you have to really invest in to get ROI back, but that's hard to do, especially when it's more than just yourself (wife-factor) planning to utilize it that also has to buy-in and commit.

view more: ‹ prev next ›

Rockslide0482

joined 1 year ago