mschout
mschout on Hacker News
I used to fly SWA quite a bit, but the past few years they are often more expensive than American for the same routes out of my area (DFW), or, require connections when I could get a direct flight on American for the same price or less. Unless I'm flying with a lot of bags, its generally cheaper lately on another airline. I did love SWA's open seating and hope this change doesn't stick, but they no longer seem to have the cost advantage over the other carriers going for them. I fear if this change goes through, its only a matter of time before they start charging for checked bags and then they will be no different from any other airline.
If I'm accessing IMAP with an app password will I still be able to do this after the Sep 30 deadline? I've re-read this 3 times and I have no idea. It almost sounds like they are disabling anything other that XOAUTH auth method from IMAP (which, I think, they already did for non Workspace accounts).
Have you heard about our Lord and Savior pipewire?
Unless you live in Dallas/Fort Worth where American has a strangle hold on the flights out of here. You basically have very few other options.
I also am confused somewhat here. With KMS, if you need to encrypt larger payloads, KMS itself is of no help except to generate a data key to use and you are left to either use AwsCrypto, or roll your own encryption using the data key which itself is encrypted by AWS KMS. If you happen to be using a language that does not have a port of the AwsCrypto library I am unclear if say AES CBC is okay or not.
If you are able to use AwsCrypto with KMS, I am assuming that is the recommended pathway as that is the default that AWS provides and I am hoping that AWS has thought it through enough to have a sensible default.
I was gonna say cherry-pick is farily frequent for me. Also I seem to learn new variations once in a blue moon for common commands. E.g. recently I learned about the --cherry option for git-log and it changed my life.
I'm not sure I get it either. Maybe just simplicity / path of least resistance in that NiceHash provides a quick way to get up and running potentially without needing to install mining software and decide on a pool to participate in etc?
Yes, AWS MFA is very poorly implemented.
LOL. I assume you're trolling. The official ZFS implementation has been Illumos for years now.
Exactly!
Most registrars are already redacting whois output to comply with GDPR.
Registrars that aren't doing this for non-EU costomers (e.g.: godaddy) are the exception. The only reason for this is to push sales of their privacy/proxy registration service.
Essentially because ICANN says so. ICANN requires the registrars to maintain accurate contact info, and also to publish the contact info on port 43. In addition they allow registrars to offer proxy registration service, which does has additional requirements for the registrar (see the whois primer linked in this thread).
HOWEVER, due to the GDPR, ICANN's "Temporary Solution" to the GDPR changes a lot of these requirements. One of the changes is that the requirement to make the contact info publicly available via whois has been removed. Registrars now are only required to show the state+country of the registrant, as well as some anonymized way to contact the domain owner (e.g.: via an anonymous email, or, via a web form).
For transfers of domain names between registrars, this also means the gaining registrar no longer is required to email you asking for authorization to transfer the domain (because the gaining registrar does not have access to the email addresses any longer). ICANN is working on a replacement for whois called RDDS which has tiered, authenticated access, as well as an accredidation process for people that need access to the real contact info such as law enforcement. However, they haven't worked out all of the details on this yet.
ICANN has also said regsitrars are not required to distinguish between an EU customer or a non EU customer when applying this rule.
So essentially, ICANN's temporary solution to the GDPR makes a lot of the reasons for "Whois Guard" or proxy registrations less useful.
See: https://www.icann.org/resources/pages/gtld-registration-data...
I believe the main reason for this (along with the requirement that registrars "escrow" contact info for all of their domains with an approved third party such as Iron Mountain) is so that the domain ownership information can be recovered in the case of a registrar failure. E.g.: registrar closes unexpectedly, or registrar suffers some catastrophe and loses the contact info.
I am an engineer working for a registrar and we've been told by at least one TLD that there is no difference. We used to "mask" the registrant email regardless of whether or not the customer had opted-in for proxy registration, and we were told this was not allowed by the TLD operator.
Valley View Mall is one option that was proposed. There are plenty of spots.
I ran Linux on the desktop from ~1996 until about 2008 when I switched to OS X. The things that keep me from going back is a much shorter list now than it was back then, but for me it boils down to:
1: Lightroom/Photoshop. I'm a hobbyist photographer, and the tools just aren't as good in Linux. Gimp, Darktable etc are interesting, but they just aren't up to par yet with Adobe's offerings. And basically everyone in photography seems to be using Lightroom + Photoshop.
2: iMessage - being able to have my SMS and iMessage messages on the desktop (and synced back and forth from my iphone) is just way too useful every single day. Yes there are apps that provide similar functionality, but the beauty of iMessage is that nobody has to use an app. They just send texts like normal. Maybe there is a solution to this that works in Linux but I haven't seen it.
MacVim is now using Vim 8.0
If this article makes you think DNS is complex, just wait until you have to deploy DNSSEC!