Fujitsu has never been served justice for Horizon.

This is a joy.

Berkeley, for disambiguation.

Oops, too late to edit my comment!

Google incentivizes takedown vote abuse. 1. 3 Strikes rules for channels 2. Automatic takedown systems based on votes 3. Incentivizing competing channels with ads 4. No verification/limits/punishment of bogus takedown voters and vote bots 5. Lack of democritized, universal takedowns of equivalent content

Does Microsoft unfairly benefit from Google's takedown tirefire? I do not know.

But if I were designing a voting system for takedowns it would be: 1. 1 non-DMCA takedown vote per user per year 2. No takedown votes for accounts less than 1 year old 3. Takedown all equivalent content when a video is voted down. 4. Verification of DMCA ownership before taking down DMCA-protected content.

It is not a mandatory feature.

Yes, it is mandatory for OEMs.

Microsoft denied a bug for a decade that harmed 100% of users every month in an obvious way.

It is the denial that is so very Microsoft.

Finite, but sufficiently abundant for any human to be clothed, housed, fed, taught, married, and succeeded by offspring as well-protected as they.

It is hard to see it as anything else.

I wish them success. I would like more of my vendors to operate their pricing this clearly.

Are there any workarounds?

In my ghostty config I use:

  scrollback-limit = 512000000
  keybind = super+f=write_scrollback_file:open

It writes it to a temporary file and then opens the file in the default text editor when I hit Cmd+F.

tmux

But there's a whole thread on other workarounds etc. Apparently it's on the roadmap.

https://github.com/ghostty-org/ghostty/issues/189