Hacker Newsnew | past | comments | ask | show | jobs | submit | more wlonkly's commentslogin

I wonder if it's buyers (which I would find mildly surprising) or potential buyers (which wouldn't surprise me at all)?


I recently discovered that iOS supports both: you can have it detect driving by Bluetooth pairing or by motion (or disable it).


That bought nginx, but yes!


I'm in a Zoom shop now, but when I was in a Meet/Hangouts shop, I used Chrome for that, and Firefox for everything else. If you're on a Mac, the utility Choosy can send links to appropriate browsers based on patterns.


It means the opposite of that.


Agreed, I would have appreciated this more as a peer-reviewed meta-analysis than a blog post.


Archive Team is carrying books in a bucket brigade out of the burning library. Archive.org is giving them a place to put the books they saved.


The long-standing requirement that you must use subnetting to isolate public from internal, and operational from management, workloads has been a thorn in the side of cloud-based FedRAMP-authorized companies for ages, and now they're finally updating it as part of the "FedRAMP 20x" program aimed at reducing red tape.

From the linked doc:

Current FedRAMP Guidance:

SC-7 (b) Additional FedRAMP Requirements and Guidance: SC-7 (b) should be met by subnet isolation. A subnetwork (subnet) is a physically or logically segmented section of a larger network defined at TCP/IP Layer 3, to both minimize traffic and, important for a FedRAMP Authorization, add a crucial layer of network isolation. Subnets are distinct from VLANs (Layer 2), security groups, and VPCs and are specifically required to satisfy SC-7 part b and other controls. See the FedRAMP Subnets White Paper (fedramp.gov/assets/resources/documents/FedRAMP_subnets_whitepaper.pdf) for additional information.

Updated FedRAMP Guidance:

SC-7 (b) Additional FedRAMP Requirements and Guidance: SC-7 (b) may be met by using any technical capability that ensures logical separation between publicly accessible components and internal networks by preventing traversal without inspection and authorization; traffic may not flow unrestricted from publicly accessible components to internal networks.


Jeez, I moved from Instapaper _to_ Pocket many years ago.


Based on the thread and the replies to the thread, it sounds like this is a particular (franchised) hotel, and there are other (franchised) hotels in other brands that are using the same revenue stream. So boycotting Hyatt will not let you avoid ending up at a hotel with these things.


Yes, I feel like it's important to clarify that this is one specific hotel which happens to be associated with Hyatt, not a general program instituted by Hyatt or any specific chain.

If Hyatt refuses to address this scam after being made aware of it, that's a different story, but for now this is a story about specific hotel properties' wrongdoing.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: