danielparks
Also, what’s his problem with the “Witch Priestess from the North?”
EDIT: Oh, the blue backgrounds are links. https://jacobfilipp.com/new-lord/
I have no personal experience with Mira; I’ve been looking for a respirator myself because I live in Portland.
I actually know a number of people with CIs, but everyone else is at ASL club, so we’re not doing a lot of speaking. I’ll have to ask folks what they’ve tried, if only for my own curiosity.
I know somebody who really dislikes the over-the-ear type devices and swears by the all-in-one kind.
She seems to get a full day of battery out of hers, but I don’t know what kind they are and I imagine usage patterns make a big difference.
I keep expecting to have to explain, but the vast majority of the time people don’t ask.
I still try to be somewhat efficient about loading the dishwasher, but… if I notice myself stressing I just say “screw it”, run it, and wash the rest by hand.
The other thing I’ve realized is that sometimes things don’t get clean if you load them properly. For example, tall glasses that had smoothies in them. It’s a little gross if you don’t notice it until you’re about to use it, but… you can just look at them and wash them by hand when you unload the dishwasher.
I guess this is all to say that sometimes the best optimization is to not think about it too much.
If the operator were explicit (let’s call it ~), the example would look like this:
$ echo 'cat' | trre 'c:d~a:o~t:g'
dog
$ echo 'cat' | trre '(c:d)~(a:o)~(t:g)'
dogI found the operator precedence unnatural, and it looks like a lot of other folks in this thread did too. I would naturally assume `cat:dog` would be equivalent to `(cat):(dog)` rather than `ca(t:d)og`.
Yes, this still an issue if you manually download an attachment, but that’s a lot better than automatically when you open a conversation.
I understand that Signal does not consider this
https://gist.github.com/hackermondev/45a3cdfa52246f1d1201c1e8cdef6117 to be
a valid security bug, but it would be helpful to at least be able to
mitigate it.
Please add an option in settings to disable automatically downloading
attachments.
That should be enough to change the attack from 0-click (just opening the
conversation) to 1-click (click the attachment). Most people won’t care
about this, but for some every little bit of privacy is important.
> I decided it was finally time to build a file server to centralize my files and guard them against bit-rot. Although I would have preferred to use OpenBSD due to its straightforward configuration and sane defaults, I was surprised to find that none of the typical NAS filesystems were supported.
OpenBSD does not support ZFS.
https://youtube.com/c/FallofCivilizationsPodcast
(This particular episode is not out with images yet.)
It’s been a long time since I did any work on a real authentication system — since before TOTP was common, anyway. I appreciated the post and found it interesting.
The author posted the link in the comments of the original post.
I’ve seen the “clean up errors yourself” argument before, but, like the author, I don’t think it holds water. Often the correct response to errors is to panic() or pass it up the stack so the caller can deal with it or—more likely—panic() itself.
Seriously, I would love to have a quicker way to cook onions.
https://forums.flyingmeat.com/t/memory-consumption-when-open...
Gus Mueller (the author of the linked tweet) is the author of the Acorn image editor.
It would be fun to see this, but I get the impression that it would involve a visit to the Library of Congress. Or maybe Cuba?
Is there more information on the Library web site that I’m missing?
Use an entirely different user for file ownership.
Whether or not people actually install them is a good question, though.
It’s certainly not my experience with lamotrigine.
So, mail, DNS, and a few web sites. I’ve been running something like this for more than 15 years now.
The standard on most UNIX-like OSes is that long options, e.g. --long, have two dashes, and short options, e.g. -l, have one.
It allows you to combine multiple options into one. For example, the following two commands are equivalent:
$ ls -laF
$ ls -l -a -FFor example: https://github.com/DavidGamba/go-getoptions
I don’t have any problems with FaceID — it’s more reliable and easier than TouchID for me. I live in a rainy place, though. Obviously a YMMV situation.
With TouchID do you just put your finger on the home button and hold it by the reader?
If you’ve built once using the standard go module functionality then you will be able to rebuild as long as you don’t pull in more dependencies. Naturally you can move the cache around.
I don’t follow. Why is the code change important?
Why not just use the go module cache? Seems like a much cleaner solution with very little overhead.
This has been an increasingly difficult problem as more and more pipelines move to containers for testing and building. What other solutions have folks come up with?
Seems like an unnecessarily hard way to exfiltrate data.