For example in a multi-tenant application 90% of tables will link to the tenant table, but those links add little value to the viewer, so hiding these would be nice.

> your_command | grep -o -i "b" | wc -l

* If you allow the user to grant those privileges to third-party applications, they can grant it to applications that abuse it, resulting in security and privacy risks. You might even be blamed for allowing them access (e.g. the famous Cambridge Analytica scandal).

* If you don't allow the user to do that, third-party tools won't be able to serve those needs, which can be considered anti-competitive preferential treatment of your own tools.

(And I don't think it applies to US merchants like you anyways)

https://ec.europa.eu/commission/presscorner/detail/en/ip_15_...

Why is there no way to legally fight this? Is polymarket too de-centralized? Or incorporated in a jurisdiction where that's not feasible? Or are "you can't sue us" ToS actually enforceable here?

Or run the installer in Wine/Proton.

Online payments (e.g. e-commerce) usually send such data directly to the PSP, or encrypt it with a PSP controlled key.

And in person payments (e.g. stores and restaurants) use a payment terminal/device, which is presumably PCI DSS compliant and doesn't store such information.

Doesn't that just trade password resets for passkey resets? Or do they permanently lock out users who lose their passkey?

In a well designed scheduler, a task that has been granted an allotment of at least n cores, should never get throttled to less than n cores at any time. It can be limited to less than n cores if CPU utilization is at 100% and another task gets scheduled at the time, since that's unavoidable when you oversubscribe the available resources.