Notices by Simon Repp (freebliss@post.lurk.org), page 2

Faircamp 0.22.0 has been released today! ヽ(⌒▽⌒)ﾉ

Did you know that faircamp sites can be used without javascript? That even unlock codes still work without javascript? ^^ Much has been added and changed in the last months, but during initial planning for the Faircamp 1.0 grant work both me and the @nlnet team were fully on board with the idea of dedicating a work package to making sure that during all the new developments, faircamp stays as usable as it can be without javascript, and this release now includes all the changes to make it happen!

And we have two important fixes included as well: "More" sections now make use of the full site width on smaller screens (thank you @lminiero for bringing this up!) and a piece of logic was added to ensure that support artists are registered for releases that have their main artists set either manually through the manifest or through the "Album Artist" tag on files (thank you @keefmarshall for digging up and reporting this long-undiscovered issue).

Many thanks again to @nlnet and the @EC_NGI for funding this important work. Keeping things working without js is not a glorious or particularly fun task, but important nontheless!

New to #faircamp? Check out https://simonrepp.com/faircamp/

Good news everyone – Faircamp 0.20.0 is out, introducing
a major new feature: Browse/Search! °˖✧◝(⁰▿⁰)◜✧˖°

Many, many other things happened as well: Direct external download links, M3U playlist opt-out option, "More" section redesign and conditional rendering, lithuanian and serbian (cyrillic+latin) translations, simplified payment configuration, fixes for RTL layouting/downloads/rounded corners mode, and well over 20 (!) major and minor accessibility improvements throughout all pages - in detail: https://codeberg.org/simonrepp/faircamp/src/branch/main/CHANGELOG.md

There's a great many people and institutions to thank this time around again: @nlnet and the @EC_NGI for making this work possible through the Faircamp 1.0 NGI0 grant / The diligent auditors at HAN Accessibility Lab and Radically Open Security for providing numerous excellent accessibility and security recommendations / @Vac and DURAD for the new lithuanian and serbian translations / @atomkarinca, @toctoc and @sknob for their continuous work on turkish, italian and french translations / And: Turnus for their amazing Valedictions EP featured in the release screenshots.

Faircamp 1.0 is now just weeks away and I'm super excited to see what else will still make it into the release! Maybe a new language? Check out https://simonrepp.com/faircamp/translate/ for that! :)

New to #faircamp? Visit https://simonrepp.com/faircamp/

Tada, it's #faircamp release day again! ✺◟( ᐛ )◞✺

Today's edition - 0.17.0 - introduces configurable support for writing embedded cover images to download files (flac/mp3 [¹]), three first iterative refinements to the new layout that were high in demand - reduced spacing to bring release and track lists back up above the fold, demystification of the "..." navigation link and a simplified breadcrumb implementation right where it is required for navigation, plus a handful of fixes!

Special shout-out to @sknob for diligently keeping me up to date with all the latest ways in which Safari breaks my frontend implementations ^^ and everyone who provided great critical insights on the (re-)design process, that's @keefmarshall,
@xenogon, @axwax, @ethicalrevolution and @branpos - thank you so much!

This release too is part of 2024's Faircamp 1.0 project grant, financed and supported by @nlnet and @EC_NGI. <3

P.S.: Those who update, make sure to check out "synopsis" in the manual (catalog/release pages) and give it a try! :)

https://simonrepp.com/faircamp/

[¹] I've done a good bit of research for all formats that faircamp outputs and found these two are the only ones for which this is supported through the format and through ffmpeg's featureset right now, but if you have insights to extend this to further formats, let me know!

@thanius Hey there! Sorry for the late reply - right now there's no such functionality but it's an interesting point! I've made a note of it in my feedback document, I'll give it some thought if and how this could be integrated. (It will take a while though, just so you know).