factorialboy

Who has audited these claims by Apple? Is there a governmental authority that does so?

> that cannot be accessed by the operating system or by Apple

Does any third party periodically verify and audit this claim?

— or —

Do we blindly "just trust Apple, bro"?

* Tasks / TODOs

* Podcast subscriptions and syncs (queue, playtime)

* Ditto for YouTube

* Self-made and self-played online web game

Insurance for transiting oil is primary culprit, along with supply shocks when pipelines or refineries get hit.

736mb on macOS

/facepalm

Apple claims to be the privacy king. They deserve scrutiny.

I am outside the US.

Agree on fake enthusiam.

How about genuine emotions?

I suspect you might be interested in this crowdfunded project - https://smallandroidphone.com/

Yeah, but I'm not really sure.

There's a perfectly good use case of using this device unfolded with their kickstand powered folio case and a portable keyboard — While getting some zoom calls and productivity / work done.

That may be right, I was referring to list price, which is identical between Apple and Samsung. (I'm located in EU)

With Samsung, they're going to heavily discount it over the holiday season.

With Apple, the device is actually going to retain its value in the second hand market.

So there's this value argument that can swing both ways.

Ty, phew!

I'm okay with the lack of face ID. Fingerprint unlock power button works perfectly well for me.

Did they mention MagSafe?

I'm not sure if they mentioned MagSafe for the iPhone Duo.

That could be a deal breaker.

It's priced identical to the Samsung Fold 8.

The dimensions are also close.

From a visual aesthetics perspective, I prefer the square edges of the Samsung Fold 8.

Eager to check out the reviews of the software capabilities of the iPhone Duo.

And I'm not sure about the inner screen's selfie camera. The under-screen camera has failed in previous devices, especially for zoom calls, it was abysmal.

Excited for the nano texture displays though. For far too long, Samsung had beaten Apple with non-reflective displays.

Why do they all sound robotic and sterile? :-/

Let's feel some excitement in your voices!

The largeCorp developer and their PM are many orgs and layers away from where these decisions are mandated.

I'd pick major Linux Desktop Environments (KDE or GNOME for instance) over macOS and Windows any day of the week. I feel 3-4x more productive on Linux.

With LLMs, I've been creating little desktop apps to fill the odd gaps. For example, yesterday, I made a little offline dictation app for KDE.

Is it true that the person who authored the "Grug-brained developer" essay also created HTMX?

Cool project. I've built my own Django "harness" so I can't use it right now, but will consider for future projects.

For one sec, I got excited for a new font!

Leading be example is not.

Look up Vatican land holdings across Europe, Africa and Asia.

But then, the opposition to my comment is based on religious ideology and not merit.

The pie (market) has also vastly expanded since 1998. Need to factor that, and not just inflation.

Tusk — an open-source Postgres desktop app for macOS and GNOME — https://shapemachine.xyz/tusk

Tusk - An open-source Postgres desktop app for macOS and GNOME - https://shapemachine.xyz/tusk

Pretty much, yes.

Silently replacing Git with `but`.

All I did was install GitButler via my OS's package manager, and open a local repo via the GUI.

And I saw these malicious (pre-commit) git hooks installed by GitButler, without any confirmation, or prompt seeking my approval.

I'm sure you folks will come up with a "technical explanation" or some "legal-marketing language" to cover up for this — but in my book — redirect `git commit` to `but commit` is dishonest and unethical.

Installed GitButler to try it out — and realized it installs malicious Git hooks to take over the git commit workflow:

* pre-commit — The malicious one. It intercepted every git commit attempt and aborted it with that error message, forcing you to use but commit instead. Effectively a commit hijack — no way to commit to your own repo without their tool.

* post-checkout — Fired whenever you switched branches. GitButler used it to track your branch state and sync its virtual branch model. It cleaned this one up itself when we checked out.

* There's also typically a prepare-commit-msg hook that GitButler installs to inject its metadata into commit messages, though we didn't hit that one.

* The pre-commit hook is the aggressive one — it's a standard git hook location, so git runs it unconditionally before every commit. GitButler installs it silently as part of "setting up" a repo, with no opt-in. The only escape (without their CLI) is exactly what we did: delete it manually.