CVS and E*Trade both refused to accept my fairly standard user@mydomain.info address during initial registration, but had no issue changing to that address once the account was created. It would be nice if their internal teams communicated a bit better.
The full email address syntax described in the RFC cannot be precisely matched with a mere regular expression due to the support for nested comments. The need to track arbitrarily deep nesting state makes it a non-regular language.
If you remove the comments first the remainder can be parsed with a very complex regex, but it will be about a kilobyte long.
They ruled that people acting together have all the same rights that they would have acting individually, and that preventing someone from spending money on producing and promoting their speech effectively prevents them from being heard. Which are both perfectly true, common-sense statements.
If you can read emails sent to a given address, and send replies from that address, it basically is your email address for all practical purposes no matter who was meant to be using the account. This is not necessarily a good thing and better end-to-end security would be nice but it is what it is. Odds are the app itself would let anyone change the password and log in provided they can read the emails, unless it’s using some form of 2FA.
I’m fairly certain that last one is UB in C. The result of an assignment operator is not an lvalue, and even if it were it’s UB (at least in C99) to modify the stored value of an object more than once between two adjacent sequence points. It might work in C++, though.
They should still be using the CPU’s built-in AES hardware acceleration, yes? It seems they have good reason not to trust the SSD to handle the encryption but that doesn’t mean it has to be entirely implemented in software. CPU-accelerated AES shouldn’t be that much slower.
Examples of local commands I might run in tmux could include anything long-running which is started from the command line. A virtual machine (qemu), perhaps, or a video encode (ffmpeg). Then if I need to log out or restart my GUI session for any reason—or something goes wrong with the session manager—it won’t take the long-running process with it. While the same could be done with nohup or systemd-run, using tmux allows me to interact with the process after it’s started.
I also have systems which are accessed both locally and remotely, so sometimes (not often) I’ll start a program on a local terminal through tmux so I can later interact with it through SSH without resorting to x11vnc.
Not the GP but I also use tmux (or screen in a pinch) for almost any SSH session, if only as insurance against dropped connections. I occasionally use it for local terminals if there is a chance I might want a command to outlive the current graphical session or migrate to SSH later.
Occasionally it’s nice to be able to control the session from the command line, e.g. splitting a window from a script. I’ve also noticed that wrapping a program in tmux can avoid slowdowns when a command generates a lot of output, depending on the terminal emulator. Some emulators will try to render every update even if it means blocking the output from the program for the GUI to catch up, rather than just updating the state of the terminal in memory and rendering the latest version.
The morals of your actions are for you to decide. It’s your conscience. However, if you punched someone over what they said they would be perfectly justified both in defending themselves against your aggression and in punching you right back. At that point you would have no objective rational argument that their defense or retribution was wrong which would not similarly condemn your own actions. You’re the one who chose to escalate to violence, not them.
Individuals do have more freedom to discriminate and show “social intolerance”, but that obviously doesn’t extend to punching people they disagree with. Or violent responses in general.
Freedom of Speech primarily exists to protect thw press
Freedom of Press is a whole separate thing. Freedom of Speech is about public discourse in general, not just speech by members of the press.
Apart from that, however, you’re on the right track.
The social contract concept is over-used by people who try to make it cover too much. It becomes a one-sided contract of adhesion which you’re assumed to have agreed to simply by existing. This, however, is simple reciprocation—it’s more like a truce than a contract. It would be unreasonable to expect tolerance from others while refusing to grant the same tolerance to them.
Of course there is no obligation to be intolerant just because the other person is; you are free to make a better choice.
A person can see a dog whistle and know it for what it is without being able to hear it. Also it’s not only dogs who can hear dog whistles; some people just have exceptionally good hearing.
Citizens have their own limitations when their response strays outside the realm of speech. Boycotts are fine—you have no obligation to buy what they’re selling. However, harassment is not okay, and bullying is not okay. These things are wrong (and coincidentally illegal) on their own merits, and not a justified response to someone else’s speech.
In what sense do you think this isn’t following the email standard? The plus sign is a valid character in the local part, and the standard doesn’t say how it should be interpreted (it could be a significant part of the name; it’s not proper to strip it out) or preclude multiple addresses from delivering to the same mailbox.
Unfortunately the feature is too well-known, and the mapping from the tagged address to the plain address is too transparent. Spammers will just remove the label. You need either a custom domain so you can use a different separator (‘+’ is the default but you can generally choose something else for your own server) or a way to generate random, opaque temporary addresses.
If you want to talk about non-compliant address handing, aside from not accepting valid addresses, the one that always bothers me is sites that capitalize or lowercase the local part of the address. Domain names are not case-sensitive, but the local part is. Changing the case could result in non-delivery or delivery to the wrong mailbox. Most servers are case-insensitive but senders shouldn’t assume that is always true.