A significant effect is through opioid receptor activation, as demonstrated by Williams et al. <https://doi.org/10.1038/s41380-019-0503-4> by blocking the receptor with naltrexone, which attenuated the antisuicidality effects.
Hi, I'm Kevin. I'm a generalist senior software engineer and consultant with over a decade of experience with a broad range of technologies, roles, and industries. I graduated magna cum laude with a B.S. in C.S. from Cornell, co-founded Digital Engine Software in 2009, joined early-stage fintech startup Quantpost in 2013, and have been developing and consulting independently since 2016 for a variety of clients, particularly in home health care and construction. Recently I've worked on many backend web sites and services (ASP.NET+MSSQL and MEAN Stack), automation, integration, and synchronization (Selenium+C#, Python, PowerShell), and Linux DevOps (Docker, Ansible, Bash) projects, but I particularly enjoy lower-level embedded and systems programming. I'm a free and open-source software proponent and contributor. I'm looking forward to joining a team doing meaningful work, particularly toward a social good, contributing my expertise, and learning and collaborating with other professionals.
It sounds like you may be remembering VBE display modes.[1] I think you can still play with these modes by adding `nomodeset vga=ask` to the kernel parameters[2] if you are booting with BIOS (or UEFI with CSM).
According to the comment, the rest of the script "uses IFEO to attach to Virtual Disk Service Loader process running during setup, then erases appraiserres.dll [...] it must also do some ping-pong renaming of vdsldr in system32\11" Could anyone explain this in more detail?
To clarify, gcc -Wall only produces the warning with -std=c89/gnu89 (or GCC < 5 without -std=c99/gnu99). As with clang, it implements the implicit `return 0;` for C99 and later. Example: https://godbolt.org/z/Y7Wx5Y89q
Agreed. I should have made my post clearer. OpenWrt does not suppport SHA-2 signature hashing or any of the newer key algorithms I mentioned, so you are stuck with RSA+SHA1.
I've been running with ssh-rsa disabled for a while (with a config based on https://infosec.mozilla.org/guidelines/openssh#modern-openss... ) and it's been pretty smooth. Support for better algorithms is widespread, with a few exceptions (like bazaar.launchpad.net).
One gotcha: OpenWrt does not enable ECDSA by default[1] and only recently enabled support for ed25519 by default.[2][3] It's available in release candidates for 21.02, but not in current stable releases. So if you're running a stable release you'll need to either add `PubkeyAcceptedKeyTypes +ssh-rsa` to your client ssh_config or use a custom build of OpenWrt with DROPBEAR_ECC or DROPBEAR_ECC_FULL enabled.
Great suggestions! One caveat: -fsanitize=pointer-compare and -fsanitize=pointer-subtract have some sharp edges and (last I knew) are not considered production ready by the sanitizers team. For example: https://github.com/google/sanitizers/issues/1324
It's neat, but I don't believe it is a compliant implementation of HTTP/1.1 (or 1.0). For example, it does not handle percent-encoded characters in the request URI.[1][2]
I agree. As with many things, it's only simple as long as you ignore the complexities. As they say, the devil's in the details.
> this "server" only responds to a simple well formed GET request.
And not even that. The Request-URI in a Simple-Request line (inherited from HTTP/0.9) may contain escape characters. (e.g. `GET /my%20file.txt` to get `my file.txt`) HTTP/1.0 states "The origin server must decode the Request-URI in order to properly interpret the request."[1] This server does not.
Which is not to say that this server isn't interesting. Just that it's not a demonstration of how easy HTTP/1 is to parse.
I still use both, with a shared vimrc. The biggest advantage of neovim for me is support for the clipboard in Wayland.[1] There are workarounds for vim (vim-fakeclip[2] is the best I found) but they have many limitations which can be frustrating.
It needs both hardware and driver support. You can check supported formats using vdpauinfo. Nouveau maintains a list of supported formats for different hardware at https://nouveau.freedesktop.org/VideoAcceleration.html (I don't think HEVC is supported by nouveau on any hardware.)
The Huberman Lab episode Ketamine: Benefits and Risks for Depression, PTSD & Neuroplasticity <https://www.hubermanlab.com/episode/ketamine-benefits-and-ri...> and the referenced journal articles (including the above) have a lot of detail on it.