I haven't Smart Comic before. Thanks for the recommendation. Definitely going to give it a try. (I admit that panel handling is a nice to have feature, but what makes or breaks a comic reader for me is how easy is to sync comics---but this is a long departure from the thread).
YAC Reader [1] has great panel recognition. My other favorite comic reader has attempted but never got something that I could use.
> It identified a culture where Tessier-Lavigne “tended to reward the ‘winners’ (that is, postdocs who could generate favorable results) and marginalize or diminish the ‘losers’ (that is, postdocs who were unable or struggled to generate such data).”
I am honestly very curious who hasn't observed the same behavior in large corporations too. (And to be clear, I'm not defending this behavior; rather curious if it's not an unfortunate generalized situation that occurs not only in academia).
I'm using Scrolla. Initially I had used vim-like extensions for browsers. Obviously Firefox and Chrome extensions are eras ahead of Safari's. Scrolla was like: "hey, I can get this everywhere on my system".
Wooshy and kindaVim are more or less in trial mode (I'm paying for the latter). I'm not yet relying on them heavily.
I do appreciate the foundation of these apps though and I'm very happy to have them around.
thanks for the feedback. personally, not sure if it's because i've been using the apps so much while developing, but i can't use macOS without them now. it's a bit like Alfred to me. as soon as i start my Mac, i need those running. anyways, whether paying or not, i'm happy that they're useful to you. i've spend almost three years fulltime building them for myself for various reasons. the fact that they help other people is definitely a massive bonus!
It was no further than 1 week ago when I was talking with my spouse about how could we compare the size of some cars. We found it very tedious to even find the official dimension. And we had no idea how to visualize the differences. This is absolutely fabulous!
Every month, I comb through previous month Downbeat, JazzTimes, and Jazzwise magazines putting together a list of albums. The trick? I do this with past years magazine though.
I recently discovered the MusicBox app; sort of a listen later. My current playlist has 62 albums, as in December, these magazines are publishing their best of lists.
As someone close said a couple of days: "I didn't realize how much time goes into this music I might not always like to listen every day".
Whatever system I have (tried to) used over time, I've run into the following challenges:
1. how to deal with old tasks (are they relevant anymore? should they be removed?).
2. connecting tasks to their related source and needed information to act
For the former, the accumulation of old stuff has consistently led to less and less usage of the system and as a result to a continuously decreasing trust in that system. Adopting a new solution has given the feeling of a better system with better chances to success; but it has mainly been about having a (temporarily) new clean inbox.
Having a data model/system to implement regular reflection/cleanup/alignment on goals I find helps with cruft build up. August Bradley’s PPV has review cycles weekly/monthly/quarterly/yearly which cover higher levels of abstraction as the time period gets larger. I’m building an implementation of it in obsidian, august does his in Notion (which I started with but started to see a cap on extensibility), it’s a WIP but I’d love other to make it less work for me :P
https://github.com/tot0/ObsidianPPV
@luxpir mentioned Obsidian in another comment [1] and it might be what you are looking for, in particular with a community plugin called Obsidian Dataview [2]. Dataview uses JavaScript as a query language and can query the Obsidian "vault" and create different views.
Another tool to look at is Logseq [3], which is essentially an outliner (supports both MarkDown and Org syntax), but supports a rather simplistic TODO management system. The benefit here is exactly what you describe—as you work in Logseq, you can create Todos, thereby connecting the task to the related source and any context that surrounds the todo. Furthermore, Logseq also allows for queries [4], allowing you to query your "knowledge graph", which you can embed in other pages.
Both Obsidian and Logseq store your files locally, so they can be easily version-controlled (In fact, Logseq routines commits your files for you).
I'll just add that the tasks plugin in obsidian has its own scripting syntax, much simpler/plain English, and is lighter weight than the entire dataview alternative. I actually set my system up to replicate logseq and taskwarrior within the more mature and faster running obsidian project. Ran them in parallel for a while on the same files.
Main difference for me was that Obsidian can be an outliner or general markdown editor. Logseq very focused on the former, and atomising your notes, but in reality this is rarely useful. In my case at least, especially when writing long form content. Search is fast and complete in obsidian, so there's very little benefit to recalling and embedding single lines from entire vault, it's just a resource sink in my case.
in emacs org-mode you can archive some tasks, text - it will move it to another text file ex. archive.txt with the timestamp or archiving it. Beside this keep your file in git. so you delete text & make explicit commit message that something was removed.
Some people that were interested in their productivity that I read seemed to have systems that regularly cleaned their todo lists for old tasks. Stephen King [1] advises aspiring writers not to note their writing prompts, as the best ideas should pop into your head regularly, or nullprogram.com [2] programming in /tmp/.
So maybe the way to go is to have a logrotate-like on your input file.
[1] On writing -- Stephen King, although I read it a very long time ago and would not be able to point to a specific page.
[2] I searched the web but can't find the exact citation, and there is no search feature on the website.
Most things accumulate and need pruning. Some people would like to do manual pruning but I favour a time-based approach of keeping everything in monthly folders.
Monthly folders so basically with every new month, some things are not carried-over but are still there and can be referenced if necessary.
So basically, a new month helps with reducing the accumulation of old stuff which bogs down a system.
Yeah, I've been thinking about how to tackle this and I am convinced any personal note taking app should have an archive all and start over button.
A clean sheet is intimidating when you don't know where to start but is a hard requirement downstream once your chosen abstraction starts to break under the weight.
Synchronous vs asynchronous is a choice for the author of the my_operatornotify file. This module just hands the subject + body to your code.
I did some experimenting with async sending and even batching in mine, but decided to remove that and stick with synchronous. The SMTP connection is really fast and most programs send the email at the end of runtime, so it doesn't matter anyway. I prefer the simplicity. I certainly did not want to get into managing an outbound spool, waiting for the server to come back, running a separate daemon for this...
In my_operatornotify I use tenacity to do a couple of retries, then write the message and the fatal exception to a txt file on my desktop or ~/ if there is an error sending the email. I'll notice it eventually. The stuff I'm doing is not important enough to demand more retrying.
YAC Reader [1] has great panel recognition. My other favorite comic reader has attempted but never got something that I could use.
[1]: https://www.yacreader.com/