Obsidian. Total game changer. Obsidian sync is completely worth paying for as well - firstly it helps support the project but also its slick, so well made, and easier than all the hacked together GitHub / s3 / whatever workarounds. From a content point of view I personally find having structure but not too much structure is the way to go. A bit of yaml if needed but just a gentle “daily notes = meeting notes” (on my…
I really wish that Obsidian Sync had like... 5 megs for free or something. I can't justify paying $8/month for a thing I haven't even started using, and without sync I have a hard time saying "OK let's try this" compared to Joplin or Notion. There's a bunch of cool looking stuff though
My Knowledge Lakehouse
61–70 of 98 posts
Re: My Knowledge Lakehouse
#62Obsidian. Total game changer. Obsidian sync is completely worth paying for as well - firstly it helps support the project but also its slick, so well made, and easier than all the hacked together GitHub / s3 / whatever workarounds. From a content point of view I personally find having structure but not too much structure is the way to go. A bit of yaml if needed but just a gentle “daily notes = meeting notes” (on my…
I really wish that Obsidian Sync had like... 5 megs for free or something. I can't justify paying $8/month for a thing I haven't even started using, and without sync I have a hard time saying "OK let's try this" compared to Joplin or Notion. There's a bunch of cool looking stuff though
FWIW I ended up going all in on Obsidian and paying yearly, but that outcome was far from a forgone conclusion, even a month in. I went through a full cycle of honeymoon phase, then discovering warts, and then workarounds, etc. It does take time.
Re: My Knowledge Lakehouse
#63Re: My Knowledge Lakehouse
#64Thanks for posting this. Currently building out something that is consolidating events from numerous sources and then automatically processing of those. This post helped to give me some additional ideas on the processing of those events.
Interesting, and something I’ve been thinking about. What is your architecture? Using any available workflow products for “retrieve/receive event from X, figure out what do, then do that in Y”?
I have a few sources built out right now and some fun utilities thanks to the browser extension, but in the end, I’m expecting to have 15-20 different data sources that are sent by the browser extension, collected by the daemon, and polled via crons in NestJS.
I’m taking ideas i gleaned from the AI-Town paper about taking “memories” and then generating “reflections” and then doing some other stuff on top of that and also building out a knowledge graph of everything i do, read, listen to, etc..
I’m currently figuring out the standardization of the disparate events into memories to then transform into reflections and knowledge graphs.
I’d love to hear more about what you’ve been thinking of and the issues you’ve had.
Edit: One cool thing you can do with the browser extension for this stuff is to send your cookies and headers to the database and then use in the cron jobs to get the data—think pandora.
Re: My Knowledge Lakehouse
#65Obsidian. Total game changer. Obsidian sync is completely worth paying for as well - firstly it helps support the project but also its slick, so well made, and easier than all the hacked together GitHub / s3 / whatever workarounds. From a content point of view I personally find having structure but not too much structure is the way to go. A bit of yaml if needed but just a gentle “daily notes = meeting notes” (on my…
I really wish that Obsidian Sync had like... 5 megs for free or something. I can't justify paying $8/month for a thing I haven't even started using, and without sync I have a hard time saying "OK let's try this" compared to Joplin or Notion. There's a bunch of cool looking stuff though
Totally understand if you're not employed, or barely making ends meet, but given the forum I'm going to take a shot in the dark here.
Re: My Knowledge Lakehouse
#66The howm-mode shows you a summary view, comprised of information (just the title/heading) from the (configurable) last 20 notes you have made. Everything goes under ~/howm/YYYY/MM e.g. ~/howm/2024/01 for notes I am making this month.
It has a simple way to enter schedule, todo, deadline, etc. which it shows just below the header that has single-key commands (s for case-insensitive searching, c to create a new note, etc.) for searching, navigation, new notes.
The genius of howm is that you can write and have very simple back and forward links to any file, URL, or tag, any kind of text etc., and you write "fragments" that is, whatever the smallest unit of text you want - it just needs a title plus anything else you want to add to it.
When you save the file, you hit Ctrl-C plus ",," and are back in the summary view.
So you can have very small sized units/fragments, which are very fast to create and save, but due to the forward and back links and the ease of searching (which will collate in a temporary list, everything found), you can "create fragmentarily but view/search collectively" as the documentation puts it.
My next step is to author HOWM notes in AsciiDoc or Markdown format which can easily be fed (since each note is a separate text file) into a converter for fancier output.
Syncthing easily keeps things in sync between my desktop and laptop.
In the very best of FOSS tradition, someone else wrote up a full PDF manual, in English. https://github.com/Emacs101/howm-manual/blob/main/Howm_tutor...
Re: My Knowledge Lakehouse
#67There are some good ideas in here. Personally I’ve abandoned all of my complex attempts at productivity and knowledge systems and have recently moved to the ever reliable txt file. You can format it however you want, use fun ascii art, or just plain paragraphs. I’ve got a daily.txt where I prepend a new days section every day and put in whatever I want over the course of the day. I also create other files for courses…
It's clearly a nice and simple way to write data, but what about the other way around? How do you manage to find information when you need it?
Haven't set it up yet, but it's on my TODO list.
Re: My Knowledge Lakehouse
#68Anytime a knowledge management system comes into my head I remember this joke: https://www.reddit.com/media?url=https%3A%2F%2Fi.redd.it%2F2...
Re: My Knowledge Lakehouse
#69Obsidian. Total game changer. Obsidian sync is completely worth paying for as well - firstly it helps support the project but also its slick, so well made, and easier than all the hacked together GitHub / s3 / whatever workarounds. From a content point of view I personally find having structure but not too much structure is the way to go. A bit of yaml if needed but just a gentle “daily notes = meeting notes” (on my…
I really wish that Obsidian Sync had like... 5 megs for free or something. I can't justify paying $8/month for a thing I haven't even started using, and without sync I have a hard time saying "OK let's try this" compared to Joplin or Notion. There's a bunch of cool looking stuff though
Luckily for both of us there is a solution https://github.com/vrtmrz/obsidian-livesync
Works well on ios.
Re: My Knowledge Lakehouse
#70 function note { mg +-1 "/home/user/notes/$(date "+%Y-%m-%d").txt"; }
"mg" is "Micro Emacs clone" and "+-1" opens the file at the bottom for appending, but of course it works equally fine with your choice of $EDITOR.I like this setup because it's plaintext (or markdown if you prefer), easily sorts on filename, and easily greppable. I have a couple years of notes saved this way and it's fun to explore old notes.