Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Why not use ReplayGain tags to capture the normalisation information and let your player adjust non-destructively? Of course I don't care if you do it by actually re-normalising – they're your files. Just curious!
Depending on what device/software/etc. you use, your player might not be able to read that normalization info. For that reason alone, I still use mp3gain to actually modify my files, I don't have to worry about whether or not the player will use the replaygain info, or not.
That feature didn't exist when I started and I haven't bothered to change it yet. Since this also needs support on all clients, it's somewhat less portable than my solution.
Edit: Reason 2 I'm not sure how different clients handle the dynamic adjustments