Cool! I'm glad more people are picking up Darktable! Ever since I switched the 'image processing workflow' to 'scene-referred (sigmoid)' my editing productivity skyrocketed. It's way more intuitive than the filmic RGB module IMHO. How are you finding Darktable?
Glitterkoe
joined 2 years ago
Good shower thought
Pretty sight for sure, but the editing is overdone IMHO
I guess if the need for more badges arrives you could always change the design or offer an option then.
Semantically it makes sense to put it after the community (ie crossposted from somewhere else) or after user who did it. I'd rather have this information in some shape or form in that location than that it's shaped like a badge.
The one that lives within or is in the living. It's alive in all of us (the community) and the other way around: our contributions live within the app and OSM. Also, its supposed to be the fork that lives on. I think this would be a subtle nudge without carrying a scarred name like phoenix/revival with the project forever.
In Vivo Maps
Naturally we need to know which suggestions "won" ASAP
With Railway it's the typical anticipation of strategy games that gets you. Just one more expansion of your network, one more resource to connect to a town, one more logistical puzzle to solve. It's way more intricate (in a good way) than just managing the budget and I've sunk hours and hours into some of those missions to figure them out.
Railway Empire 2 hard to put down once you get going.
Wasteland 3 is awesome and akin to DOS2 and BG3!
Hmmm, never had to sudo ... or work with SELinux I see. I highly prefer that to other policy/admin rights solutions, though, but still.
view more: next ›
Well, from what I understand for admins you have some config keys being
PF_OPTIMIZE_IMAGESto toggle the entire optimization pipeline (or accept supported formats as is) and theIMAGE_QUALITYpercentage as an integer to tweak the lossy compression for formats that support it.The image resize to 1080 is even hardcoded in the optimizrtion pipeline. I think I saw a toggle for it on the PHP side, but it seems they only expose the toggling of storage optimization as a whole for admins. The 1080 is currently not exposed as a parameter to set, sadly.
As a creator, I was interested in the maximum possible quality to retain. As PNG is often supported and by design only features lossless compression at best while remaining well under 15MB for a file with common image aspect ratio's, that was the winner in that regard. My uncropped 24MP images then become 3MB-ish.
Other formats tend to be way smaller in filesize due to lossy compression being so effective and most images I checked on Pixelfed are resized&optimized JPEGs well under 1MB (around 600-800KB). That is probably the file format and size you'll encounter most.
My own filesize comparisons were for RAW exports using Darktable for different file formats, qualities and resolutions. The PHP image pipeline used by Pixelfed will probably yield comparable results for the same image.
If I were to advocate new settings, that would be cranking up the resolution to more modern standards (like fitting a 4k monitor) and converting to WebP at some 85% (or sticking with 80%).
It's difficult, though, as that may introduce double-lossy pipelines when converting other lossy formats. That's why I looked into resolution settings first. If you upload an image that is too large, it currently decodes your (maybe lossy) image, resizes that (lossy, probably?) and re-encodes that using the set lossy quality if applicable.
Thus, first order of business: at least publish ideal image sizes.
Second, better quality control. Might involve settings per file format or setting a unified output file format.