641 karma · joined July 15, 2019
#> ln -s projects/'write monthly invoice' areas/$regular_gig/tex
#> ln -s projects/'write article on $foo' areas/$website/posts/foo
It just doesn't quite fit, because my short term tasks share repos (and note files) with long-term projects that I'm responsible for-- even regular invoices are long term repos. I suppose I could move it to Archive/Projects when complete, and have a script that moves it back every month.
https://github.com/Ikcelaks/keyboard_layouts/blob/main/magic...
Because as with traditional HTTPS caching schemes like Squid, it first requires you to first install a Certificate Authority's public key into your application, browser, or OS's Certificate Store, which (barring an already compromised system) an attacker presumably can't just.. do.
FWIW, I learned that first-hand configuring Squid when I used to run my own BSD routers and have seen the situation talked to death online in any thread that mentions OpnSense or a PiHole; no degree is necessary for exposure. We all have our blind-spots, and what matters is a willingness to be in over your head while you do the hard work of learning your way around.
This includes stumbling in the dark until you learn how you learn in the first place.
> Not all mathematical authors were satisfied with such workarounds.
Conversations has great support for OpenKeychain on Android, and I'd love to see that come to competing protocol Deltachat but the devs are focusing on cross-platform behaviors atm. Android-specific fork Deltalabs might be willing to be upstream for it if anyone knows where to start with that.
1: https://gitweb.gentoo.org/repo/gentoo.git/tree/app-editors/e...
I wouldn't know, I'm still using my second N7 with Lineage OS.
I presume that nothing has come of this for those involved (or GPL'ing the mobile app?), but didn't finish the thread or otherwise dig further.
https://www.humprog.org/~stephen/research/papers/kell17some-...
To be clear, these limitations in reasonable package scope come with positive trade-offs in the broader ecosystem such as promoting stability, inter-operability within emacs, and the insulatory disuse of FFI. I just feel like Emacs promised me I could do anything with elisp, and then denied me the low-level control that a lisp like Guile or Common Lisp is capable of. Helix does this better by not h̶a̶v̶i̶n̶g̶ ̶e̶x̶t̶e̶n̶s̶i̶o̶n̶s̶ making any promises.
1: One needs downtime, and can't expect perfect utilization even after planning for rest.
Cheers to consumer choice!