ace

joined 1 year ago
[–] ace@lemmy.ananace.dev 3 points 10 months ago

The built-in Firefox support is only activated for unstable builds, so you can't enable it on stable unless you manually enable it during compile-time.

[–] ace@lemmy.ananace.dev 15 points 10 months ago (6 children)

Why is it .jpg and not .jxl? That's the registered extension for JPEG-XL.

[–] ace@lemmy.ananace.dev 42 points 10 months ago (1 children)
[–] ace@lemmy.ananace.dev 0 points 10 months ago (1 children)

People really have no love for JPEG-XL - though to be fair that's mainly Google's fault at the moment.

[–] ace@lemmy.ananace.dev 1 points 10 months ago

Haven't really used any proper JMAP clients - since the setup is broken anyway, so mainly just curl.

[–] ace@lemmy.ananace.dev 1 points 10 months ago (2 children)

You could also just run IMAP/JMAP/SMTP as separate components, I can't see any place in the Stalwart documentation - or in the Docker image itself - where monolith is the only option.

I haven't tested the setup myself yet, but me and another root are planning on testing a setup of Stalwart to replace a semi-broken IMAP/JMAP setup for a computer club, keeping the SMTP as is.

[–] ace@lemmy.ananace.dev 1 points 10 months ago

I personally use ~/.bin for my own symlinks, though I also use the user-specific installation instead of the system-wide one.
I wouldn't guarantee that any automation handles ~/.local/bin or ~/.bin either, that would depend entirely on the distribution. In my case I've added both to PATH manually.

[–] ace@lemmy.ananace.dev 36 points 10 months ago* (last edited 10 months ago) (2 children)

Flatpak already creates executable wrappers for all applications as part of regular installs, though they're by default named as the full package name.

For when inkscape has been installed into the system-wide Flatpak installation, you could simply symlink it like; ln -s /var/lib/flatpak/exports/bin/org.inkscape.Inkscape /usr/local/bin/inkscape

For the user-local installation, the exported runnable is in ~/.local/share/flatpak/exports/bin instead.

[–] ace@lemmy.ananace.dev 3 points 10 months ago

The official binhost project has been an experimental thing until now, I've personally been using it for the year on multiple machines, but it's not been something that you can just enable. And it's definitely not been something that's come pre-prepared in the stage 3.

[–] ace@lemmy.ananace.dev 2 points 10 months ago

Reading the Dockerfile in their repo, it's simply a clean debian:slim with four compiled rust binaries placed into it. There's no services, no supervisord, nothing except the mail server binaries themselves.

[–] ace@lemmy.ananace.dev 3 points 11 months ago
[–] ace@lemmy.ananace.dev 2 points 11 months ago

I can already imagine so many fun ways this could be used.

view more: ‹ prev next ›