As a small tech tradeoff and an experiment I'm integrating a soft paycurtain: Albums can display a price tag, (including a user interaction for setting a price for "name your price" albums), payment directions are given (Liberapay, SEPA, etc. as configured), but the payment itself is not technically enforced, i.e. the listener is asked to affirm by themselves - by clicking a button - that they have paid for what they want, and only then given the download link. I'm open to experiment further with this when I've released faircamp (current codename) to the public. I could also imagine an option for integrating a hard paywall based on entering a token that could e.g. be made exclusively available to your backers on an external platform (ghost, patreon, steady, paypal, ...).
Been fleshing out the first prototype all day today, and having a blast! ✌️
Update on the announced self-hostable #bandcamp alternative: Got tons of work done on the foundation over the last days (architecture, reading, transcoding, caching, syncing, configuration, cli arguments, ...). Today was the first time I did some design exporation (first glimpses attached - these are already in-browser screenshots of the functional interface, not mockups :)). I'm developing out in the open at https://codeberg.org/simonrepp/faircamp °˖✧◝(⁰▿⁰)◜✧˖°
Been looking a bit into the topic of waveform representation in faircamp. I like the idea of integrating something that adds a varying graphical quality to all releases and tracks without forcing the artist to provide artwork, i.e. having the system generate something graphical from the audio itself, which also has functional value ... Delicate matter anyhow, not yet sure if there will be waveforms in the end. :)
Random faircamp progress excerpt: Added decoding (and thus waveform generation) for FLAC and WAV, experimented a bit with "waveform thumbnails" for the tracks of releases (might remain an experiment only), today added font customization (supplying custom files, default and custom system font stack options, etc.). I might make the system font stack the default, because environment, page load speed, non-latin scripts, etc., but let's see, in general I'm rather fond of bespoke typo choices and would rather eliminate other optional bytes on the page :)
Also there's now a --theming-widget cli option which injects a small overlay widget into all pages and with which one can interactively explore different color configurations for the visual theme - the configuration options are automatically generated as text and can be copied into the config file. (sorry for the weird video compression, wasn't meant to be an encoding glitch art video :D)
@freebliss this looks really exciting, and if you get to a point where you want beta testers i’d be game. i’m launching a new label this summer, so timing could be good.
@emenel Hey thanks, very happy to hear it! Beta testing would be fantastic - much appreciated and I just made a note to ping you when things get stable-ish. :) Also - if you then like what you see and opt to use faircamp further - I'd love to start collecting faircamp sites out in the wild (for others to get inspired and have some reference of what's possible) and would gladly add yours to the link collection then, if you're ok with that! Lastly, if you like to share that already, I'd be curious about the label's genre/very brief context! :)
@freebliss Still love this!
Actually getting ready to do something similar in a piece of software I'm working on.
Welcome to post.lurk.org, an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.