• 4 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle














  • I used to have this concern myself, but I think there’s nothing to worry about if you label notes properly, giving them full YAML, source links, tags, etc. Searching is an extremely powerful tool, but it’s only as powerful as the information you provide it.

    Additionally, you could provide basic structure to your system if you desire. I personally prefer minimal structure, letting groups of notes emerge, which can later become MOCs (Maps of Content). These are the hubs where all my notes can connect together, which makes finding them later even more simple.

    A lot of my initial inspiration for how I set up my Obsidian workflow came from Aidan Helfant. He has some great resources for how to get started and details about his own processes.

    One more resource that I only recently learned about was Obsidian Publish. These are public Obsidian notes from people that have decided to publish them publicly online. This is Aidan’s for example. It might help you figure out what kind of setup you’d like to try.

    Ultimately everyone creates a system based on personal preference and experimentation so don’t be afraid to try new things :)



  • I started using Obsidian about a month ago. So far I’ve been treating it like a personal wiki. It took me a while to start really figuring out what to create, but now some of my primary subjects are technical notes (programming), ancestry, health, academic notes, etc.

    I mainly feel prompted to create notes based on learned information. I might take an article found online with really interesting information, then convert it into my own words and save that as a note. The more concise I can make the note, the better. It’s preferable to try and get to the main point of a subject in a few sentences or less. Doing it this way makes future me spend less time retrieving the information I need.

    One shortcut that has helped me a lot is CTRL + O. It will open a promp to find a note, or create one if that doesn’t exist. It’s important to give your notes basic tags as well for what topics they pertain to do that you can make searching easier.

    As for how much I use it, currently maybe a couple times a day, but I anticipate my usage growing as my note collection becomes larger.


  • CuriousOttertoManderOn protecting Mander's theme
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 year ago

    I’m very new to this community myself, but I love what is being created here. It would seem to me that this instance is focused more broadly on academics than just science/nature. I believe that’s a good thing though, as it creates a wider array of interesting content.

    The closest space on reddit that I might compare this community to would probably be the DepthHub. One example of the type of subs that they often link to includes r/AskHistorians, which has valuable content, but doesn’t really fit here if there’s a strict curation of science/nature content.



  • I’ve dreamed for years about a decentralized single sign-in method. Some of the worst security issues derive from using passwords, usernames, emails, etc. Two factor authentication is ultimately just a band-aid fix for now. I truly think the killer usecase of web3 will be the ux. I’m glad that there’s someone else that shares this conviction.

    While signing up for Lemmy, I found myself wishing for a web3 sign-in method. Federation is great, but there are so many servers and to have an account on each would be silly. Instead of crossing the server boundary on an account from your home server, why not just have a native account on each, connected by your decentralized web3 sign-in.


  • I’m sure it’s possible. Someone would either need to transpile the current data format to match Lemmys’, or just build a new front-end for it. Also, it might be considerably difficult to host something like this because there’s just so much data. The Pushshift archive alone is 2TB, which is primarily just text.