No, not a mix of both. Either exclusively wins only, or losses only. Only way to tell these two apart is to see if this information is being celebrated or not…

Do you have Bluehost web hosting plan? In that case, Bluehost would do the most heavy lifting regarding the derliverability. Email deliverability with big hosts like that shouldn’t be a problem.

Owning a domain for yourself and having a provider send/receive email on your behalf is a common choice, and it has its own benefits such as being able to migrate to other providers easily. As long as you renew your domain properly, it should be fine. Though do note that only you would use that domain, so anyone would know it was you who sent that email.

Owning a domain for yourself AND handling email sending/receiving can be challenging because there’s a chance your email gets filtered as spam, and the receiver doesn’t get what you sent. It’s also possible that your server goes down, and the email sent to you doesn’t arrive properly, though the email server usually try to send again a number of times before giving up.

If you are confident about setting a server, I can personally recommend Mailcow. As long as you set up SPF, DKIM, DMARC, it should pass most spam filter including Gmail. If you don’t want to deal with the potential headache, getting a provider to send/receive emails for you is a good choice too.

연패

Can mean “to lose multiple times in a row” (連敗) or “to win multiple times in a row” (連霸).

I dump my encrypted data to someone who probably practices 3-2-1 rule (which is Backblaze for me). I mean, these guys back up data for a living.

Grub entry missing and Nvidia driver installation not going smoothly did happen to me, though the former is somewhat independent of the distro.

Not even close. Too many things to learn, too many things you can get good at, not enough time to do them all.

Worse: Debugging regex that needs to be passed as a string\.

show me the money
black sheep wall
power overwhelming
operation cwal
food for thought

How I played Starcraft as a child

.ch

• Renewal is cheap, even if the domain is short
• No particular requirements for registering
• Automatic WHOIS lookup is disabled
• Easy domain hacks
• Decent reputation, ranks low in mail spam rate

Same here. I spent last month transitioning all my servers to NixOS and it feels so comfy! I do a small test on my desktop when I do something that might break stuff first, and then add it to server’s config later.

--target-host and --use-remote-sudo makes it even better too.

If you’re considering (something) + Syncthing, try Orgmode. It looks like Markdown but has a lot of features for note management and navigation.

Did mandatory service, and no, it shouldn’t be a thing. It’s not that you would be fighting in the frontline that it sucks (it is a possibility, but doubt it would happen any time soon), it’s that you can’t do much during that period that makes it annoying, and you’re paid below min wage for it. It also imposes restrictions on you before you complete your service in case you try to avoid it. You also do it during the 20s, and that’s just a waste of time.

They are always well versed in colour theory, or at least it feels like that. Really jealous that they can get any colour working, but I can’t even with the help of those online palette generators.

THANK YOU! Just got my frontend back up and running. Turns out it was Gluetun that needed to be in the same network as my reverse proxy container, not the application that is behind Gluetun.

Have you by any chance managed to set it up with a reverse proxy? I can’t get communication between two containers working if one’s using Gluetun.

Not sure about other bugs but definitely for network-related bugs. Knowing how to tell if it’s happening on my side or not is also a plus.

Nice argument. However:

ME IS FLOAT

TEXT IS NOT PUSH

The hardest part would be how to trigger the kill-switch periodically without showing it to your adversary whilst keeping it easy. Having your device queried directly would be a dead giveaway. My idea without involving people would be as follows:

1. Set up a program that syncs files to a remote third-party cloud
2. Sync it to a directory that frequently changes when you use your device (your docs, for example)
3. Have a server that queries the third-party drive for that synchronised directory
4. If there are no changes, trigget the alarm

But since this plan relies on the secrecy, it’s kind of ruined now. That, and I think your threat model is a bit too extreme.

A dead man’s switch doesn’t quite protect you from garden hose cryptanalysis though. Nothing stops them from asking you to tell them if he got a dead man’s switch.