#faircamp musing on reducing server cost and resource usage: 1) Faircamp generates the site without any download files/archives at all (only streaming assets are written to the build directory). 2) Instead it generates an additional local/client-side directory - not to be deployed - that contains all releases for download with torrent files. 3) Visitors on the faircamp site can exclusively download releases via torrent/magnet links, and the artists seed the downloads from their own machine (whenever they're online).
Nothing about this is new (on the contrary - file sharing renaissance galore :)), but I really like the idea of mashing up a (cheaper and less resource-demanding) always-on streaming server with a P2P download delivery mechanism (which is entirely re-using existing computers and infrastructure, i.e. avoiding data center proliferation and idle infrastructure). Also fans are downloading music directly from the artist then - literally from their computer. ^^
(Thoughts anyone? Note that this would of course be an additional option, not a replacement of how faircamp handles downloads so far)
Ahoy friends. Another week another 12 existential crises...
With regards to safe, simple, clean and honest place to offer tunes in a non social platform, non shop, we are about to make public our RFF community #faircamp where you can have your own space as an artist for preview, share, embed, download, and requesting sales/donations.
If that suits you, we have a very simple onboarding process tested where you just offer well tagged flac files, possibly even a zip from BC, and that's it.
Had a go at a Faircamp style aggregator - made with a python script that downloads the feed.rss file from sites that have it, then uses faircamp to generate a label mode Faircamp site from them. All links from the directory page are replaced so they go to the respective artist release page or home page. The result is one page that has links out to everyone's own pages and has the faircamp look.
Who's got music they want me to check out? Send me your links!
Up to 15 mins worth of music, hosted on a service that allows payments and/or messages directly to the artists (self hosted, #Bandcamp, #Faircamp, @mirlo, jam.coop, SoundCloud, YouTube, etc but NOT Spotify, Tidal etc).
Oh and you have to follow me in some respect (I'll follow back! Looking for community, not "fans" or whatever).
People who are smart and know how to setup #Faircamp, does anyone of you want to help me figure out if I can deploy that to my current web hosting, and if so perhaps help with the how?
I currently have housing with Dreamhost. My site runs off WordPress. I can access ftp and all that if necessary. I don't want to take down my WordPress site tho. Can they run under the same domain/side by side?
I'll try to figure out a solution with our diligent brew packaging hero @themissingcow, but expect at least 2-3 days for this to succeed as whatever we come up with still needs to be manually reviewed and greenlit by the homebrew team.
Special thanks to @lislegaard for reporting and digging into the issue and @kel for additional support in the process!
[*] The issue seems to be caused by a software or system update in our code forge, which through an earlier git upstream change, interfered with the checksum stability of faircamp's release tarballs. Which is to say, tough luck, but no one's fault really, tech is just messy sometimes. :)
Today we have a shameless plug for #BonkKnobRecords and our brand new #Faircamp site, where you can grab all previous releases including the equally brand new #BonkWaveAllstars single for nowt!
With all that saved money you could consider making an independent artist happy by supporting them, buying one of their releases, or if you're strapped for cash, praising or sharing their work.💕
Bon ben #BandCamp c'était fait pour que même les batteurs puissent s'en servir, par contre #FairCamp c'est pas la même salade.
ÉVIDEMMENT ON EST SUR MASTO ET TOUT CELA N'EST RIEN.
Mais bon...
Any #BonkWave musicians or aficionados that aren't already in the Matrix chat?
Let me know, and I can invite you or keep you posted about major updates. We are currently discussing next steps. This includes future compilations and hosting of existing ones.
There are ~50 hours left to vote in the Bandcamp/Faircamp poll.
The upcoming #faircamp release will feature "unlisted releases", that is, you can add the flag "unlisted" to the release manifest/section to hide it from all publicly accessible pages, while still being able to visit the page if you know the permalink.
There are some minor implications for label mode though, which I'd be happy to have double-checked - if you're a (current or potential) faircamp site operator, do you have any thoughts on this?
"An unlisted release is never visible on the home/index page.
In label mode there are some additional intricacies: An artist that has only unlisted releases is not visible on the home/index page, but in turn, all of these unlisted releases are visible on the artist page, as the artist page itself is implicitly unlisted then. If however, an artist has even just a single listed release, it becomes visible on the home/index page, and on the artist page itself all unlisted releases are not visible anymore."
The FSA #Faircamp site is online! There's a couple tweaks to be made, for example, I seem to have gotten at least one release date wrong (copy/paste strikes again), but nothing I'm worried about fixing right away.
Support is always appreciated, but feel free to just listen or take advantage of the "soft" paywall too.
Setting up your own #Faircamp site, just in case #Bandcamp goes to total shite?
If you're a self-hosting beginner, or just a bit rusty, this new-fangled "static site generator" thing can seem a bit arcane. A lot of manuals assume you know stuff you don't know.
Good news, a new #faircamp release is available as of tonight.
First, you can now include extra material in your releases (booklet, etc.). Drop files in your release directory and they're bundled automatically (can be disabled).
Second, by default a built site will now only include full release downloads, which I'd estimate lowers build size by about 30-60%, meaning also faster deployment. Single file downloads can be enabled too though, even exclusively, if you'd rather offer only that.
Third, a very critical addition: faircamp now adds track number tags in its default "rewrite_tags" mode. Realizing the absence of this functionality prompted me to dedicate all of today to wrapping up the release asap, this cannot be missing! x)
Also included: Florian Antoine corrected my wild french translations (merci beaucoup!), aif/aifc extension support for input files, alphabetical sort of tracks when track numbers are missing, clearer "0$ or more" placeholder, and, unaccompanied by a native speaker I added dutch translations - I hope the results are not too angstaanjagend. :)
getting an error trying to generate a #faircamp page.
Hint: In order to resolve the conflict, explicitly specify non-conflicting permalinks for all involved artists/releases through metadata (see faircamp's README.md)"
I'm reading the Manual but I don't think I'm finding the correct info I'm needing to understand. Is this a metatag prblem?
Messing with Faircamp in a Docker image on Windows, and I'm actually managing to get a site built. This might be an easy way to get it running on Windows too.