The methods are trivial, and we cannot centralize the keys since they will be
different for different apps. So an abstraction for this is not beneficial.
Also move the next specific dev build check to @/next
From our Discord, someone commented
> if minio's cautions about Single-Node, Single-Drive are to be taken
seriously:
>
> "SNSD deployments use a zero-parity erasure coded backend that
provides no
added reliability or availability beyond what the underlying storage
volume
implements. These deployments are best suited for local testing and
evaluation, or for small-scale data workloads that do not have
availability or
performance requirements."
MinIO was never meant as a production replacement, it was only to make
it easy
for people to get started. So add a notice in the docs re this.
From our Discord, someone commented
> if minio's cautions about Single-Node, Single-Drive are to be taken seriously:
>
> "SNSD deployments use a zero-parity erasure coded backend that provides no
added reliability or availability beyond what the underlying storage volume
implements. These deployments are best suited for local testing and
evaluation, or for small-scale data workloads that do not have availability or
performance requirements."
MinIO was never meant as a production replacement, it was only to make it easy
for people to get started. So add a notice in the docs re this.
Open the link in a new tab. This prevents the desktop app from getting
into a state where the user cannot navigate back.
Tested on the web app and desktop app.
## Description
New Oneplus devices have a "ProXDR" feature when viewing images. These
images (when in HEIC format) decode fine on devices that supports
ProXDR, but fails to decode on other devices.
So if decoding fails, we convert it to a JPEG and use that image for
viewing it.
## Tests
- [x] Tries converting to jpeg only if decoding fails
- [x] If converting also fails, the behaviour remains the same as before
when decoding fails.