[1] https://open.spotify.com/album/2gC3Ecmd6SuSSvdtpa30zP

[2] https://web.archive.org/web/20221225103900/https://www.pcgam...

Thank you contributors!

[0] https://employees.theworknumber.com/employee-data-freeze

[1] https://krebsonsecurity.com/2017/11/how-to-opt-out-of-equifa...

> Kaplinksy’s claim to fame is that he’s the lawyer who figured out you could get rid of the ability of a consumer to go to court by using what’s called a pre-dispute arbitration provision in a contract.

I'm no expert but Kaplinsky sure sounds like a modern day super-villain.

[0] https://www.thebignewsletter.com/p/ending-junk-fees-the-most...

[1] https://www.ballardspahr.com/People/Attorneys/K/Kaplinsky-Al...

What magical event happens to people at age 30 that led the legislators to ban catastrophic? Would love to see the actuarial data on that. I have no knowledge/evidence of the reasoning but to me it definitely smells like lobbying.

[0] https://www.healthcare.gov/choose-a-plan/catastrophic-health...

This is a great line, thanks! Going to share this with my distributed database reading group

EDIT: "this" meaning posting

As far as I know login.gov is a viable solution, already in use at the SSA, that is government-run aka doesn't require users to kowtow to an EULA, capricious arbitration, etc. The problem is there was apparently interagency squabbling that messed up the original deployment schedule. So it's not available. I do hope that changes because the current situation, of mandatory id.me seems pretty terrible.

[0] https://news.ycombinator.com/item?id=35519938

Compared to other vendors, it seems like Apple has an aggressive obsolescence position. This app offers a significant countervailing force to eWaste, and IMO deserves broader recognition. Authors: great job, thank you.

[0] https://github.com/dortania/OpenCore-Legacy-Patcher

The macOS appocalypse was a really shocking moment -- it was so disappointing to learn that despite the privacy marketing shtick, macOS engineers chose to have Macs phone home sensitive data in an seemingly aggressive way, with no opt out. Now in 2023 the fact that "a preference for users to opt out of these security protections" never materialized, and the copy just disappeared from the website, is quite disappointing. Great write up here [0] - thanks @lapcat!

Anecdata: Ever since that day I've blackholed ocsp.apple.com/ocsp2.apple.com at the DNS level, and all my Mac apps have launched just fine since.

If anyone at Apple reads this, I want to be given the choice. Warn me, stuff the setting into whatever plist -- whatever, but give me the choice.

Frankly for a company with Apple's resources, it's hard to believe the OCSP test suite somehow didn't consider half-open TCP connections. If a global catastrophe like that can happen once, it can happen again - which is why, in addition to the clearly negative privacy implications, Apple should give users who care a clear opt-out.

[0] https://lapcatsoftware.com/articles/ocsp.html

https://www.theregister.com/2020/08/12/splunk_sales_discrimi...

I'm trying to understand why a counterparty would enter into an arrangement where a stock price change obligates them to financial liability like this. Presumably there's some upside if the stock price goes the other way, but it's unclear who the $ would come from in that case.

Also: Who originates options? When someone buys an option, is it the brokerage who collects the fees? Is the counterparty already involved at that point?

What makes LittleSnitch/Lulu/similar nice is they listen for "all" outgoing traffic types TCP/UDP/ICMP/etc, and show UI immediately, including for non-browser apps, e.g. games, VoIP, P2P apps, whatever -- it tends to be covered. Unless I'm mistaken I don't believe a captive portal can be triggered when "just any" process originates traffic.

That's the strength of LittleSnitch/similar, but the major weakness with host-level filtering they rely on, is you're 100% at the mercy of Apple's networking stack, and this Sonoma issue isn't the first time Apple moved the goalposts. Not too long ago Apple exempted their own services from whatever LittleSnitch hooks [1] and it could of course happen again with any macOS update.

In my view this is precisely why a separate box is appealing. Ideally it'd have as tight of a UI as the incumbent apps, including the same metadata (process name + app icon, protocol, port #, most recent previous attempt, etc).

[1] https://news.ycombinator.com/item?id=24838816

Do things e.g. pfSense support that already? "Hold" an outgoing connection from the moment the SYN is observed, notify whatever client, and only allow if the user clicks?

[0] Seafowl is an early stage open source database written in Rust. https://seafowl.io/

[1] https://github.com/splitgraph/seafowl-gcsfuse

    Post https://www.splitgraph.com/blog/deploying-serverless-seafowl