sssilverman

Seriously. You want to ask the CTO to make artifacts public because you don't want devs to set or clear an attribute bit? Talk about entirely the wrong priorities.

Where did this coddled sense of entitlement come from? Are they creating their own SSH keys? Do they know the basics of the git cli? Or are these "magic commands" too? Do they know how to do their job?

I sympathise that Apple's tooling could be better, but the conclusion and tone is ridiculous given what could charitably be described as 'unique' requirements.

Our internal CLI tools have all largely been hassle free regardless of devs OS. We do use GoReleaser which abstracts away the multi arch builds, signing, and publishing to GitHub and Homebrew, which can be criticised sometimes as a bit of a crutch. But it's also been zero hassle for all of our Mac devs (the most junior of which are still expected to be able to download and execute a binary from a terminal.) and lets us get on with our day without prioritising 'requirements' that aren't even worth spending any time on.

Why would you even ship a command-line tool if your apparent need is to avoid the command line?

WB Discovery has been pretty clear it intends on launching Max in Australia as early as 2025, not coincidentally when Foxtel/Binge's HBO rights are up for renewal.

Also try telling that to poor Stan, now in 5th place having lost much of its licensed content to Amazon, Disney+ and Paramount+ entering the market.

I tried using the official client for a while but just couldn't stand it and switched back to Apollo about a month ago.

Sideloadly + ApolloPatcher was surprisingly easy to set up. Who knows how long it'll last, but it's basically set and forget once you create the Reddit+imgur API keys and enable wifi sync/auto refresh.

Regardless of his reporting at the time, Krebs has known since December when Sharp was arrested that:

- the supposed hacker was the goddamn Unifi Head of Cloud, using the access keys needed to do their job

- the initial internal investigation into the hack and ransom was being conducted by the attacker

- that the whistleblower account is a complete fabrication by the internal attacker and his reporting on a coverup are false

Ubiquiti aren't suing him for reporting on it, they're suing him for not retracting it properly once it was revealed how false it was. As per the filing:

70. Ubiquiti brings this litigation because of Krebs’s refusal to do the right thing and retract the March 30 article or the December 2, 2021 update, which continue to malign Ubiquiti’s reputation, damage its relationships with its stockholders, and disrupt its business operations.

Krebs and Corey are _way_ wrong on this.

There is plenty to be said and very valid criticisms about how Ubiquiti dropped the ball and handled the situation. The attack being an insider does not excuse them. But it invalidates much of the reporting.

Krebs was specifically and personally targetted by the attacker as a method of spreading false statements to damage the company and, by keeping the articles up, remains complicit and liable.