Chaphasilor

cross-posted from: https://feddit.nl/post/30905225

TL;DR:

Digital Hackathon for Finamp, an open source Jellyfin music client.
Saturday, 2025-03-29 to Sunday, 2025-04-06, so two weekends and the week in-between. Looking for designers and developers, as well as anyone else interested in contributing! Checkout the GitHub repository and our Discord server for more info when the time comes!

---

Hey everyone!
I'm thrilled to announce that Finamp, an open source Jellyfin music player, will have its first Hackathon starting next week, starting on Saturday, March 29th and continuing until Sunday, April 6th!
Get ready for over a week of improvements to your favorite open source music client for Jellyfin :D

This is a digital event happening on Finamp's GitHub repository and our beta Discord server.

Why Should I Care?

In case you don't know, Finamp is a music client for Jellyfin, that has been around for a few years at this point.
It is meant to be an app that is tailor-made for Jellyfin (and all its quirks), and elevates the listening experience beyond what the official Jellyfin apps can offer.
While Finamp is used and loved by many Jellyfin users, it's far from perfect. Companies like Plex or Spotify are able to create more polished and feature-rich applications because they have more money and developers to throw at the problem.
But we, as Jellyfin users and members of the open source and self-hosted communities, believe that this shouldn't stop us from trying to build the best free & open source apps we can, together with other members of the community!

That's why we need your help to improve the quality and capabilities of Finamp, to be one day on-par or even better than the likes of Plexamp or Spotify!

What Is the Goal of this Hackathon?

As part of our efforts to modernize Finamp and make it more pleasant to use, we started redesigning and re-implementing Finamp in back 2023, and started releasing beta versions of the redesigned version early last year.
Many important elements of the app have already been overhauled, most noticeably the player screen & queue, and the download system. The redesign didn't just change the looks of these elements, but also improved their features and usability over the old version.

But there's still a lot to do!
We planned this Hackathon to give our redesign efforts a much-needed boost, so that we can finally redesign the remaining parts of the app and then release the redesign as part of the stable version.
So that's the focus - re-designing & re-implementing existing parts of the app, as well as implementing new features to go along with it.

How Can I Contribute?

Glad you asked :P
Since there's a lot to do, there are many possibilities to help out!
Here's a list of things we would appreciate your help with:

• Are you a designer? We need people creating mockups of the new design, based on existing functionality and feature request!
• Are you a developer? We need people implementing the mockups, enhancing existing functionality, or adding new features!
• Are you good at organizing things? We could use some help with keeping on top of things during the hackathon and beyond!
• Are you a user? While we don't exactly need more bug reports, you could help by going through existing bugs to see if you can figure out how to reliably reproduce them.

For the designers, we have a Figma file consisting of more-or-less up-to-date mockups of implemented and planned screens. But since we essentially just need mockups in the form of static images, you can work with any design too you want!

For the developers, while Finamp uses the Flutter framework (which is based on the Dart programming language), any frontend experience should be enough to contribute, since the syntax is very straight-forward and the style system is pretty self-explanatory.
Even backend devs can help out here, since there are some features that are mostly independent of the UI, like our playback, queueing, and download system.

What's the Timeline?

The Hackathon will consist of three sections: The two power phases during the weekends, and an iteration phase during the week in-between.

First Power Phase:

This kicks of initial contributions, and should see the first finished implementations.

Start: Saturday, March 29th, around 10.30am UTC
End: Monday, March 31st, during the early morning hours :P

Iteration Phase:

During this phase, more complex implementations can be worked on, PRs can be reviewed, and designs can be discussed.

Start: Monday, March 31st, around 10.30am UTC
End: Saturday, April 5th, during the early morning hours

Second Power Phase:

This final phase is meant to finish up any remaining implementations and tie up any loose ends.

Start: Saturday, April 5th, around 10.30am UTC
End: Sunday, April 6th, during the early morning hours

"Frequently Asked" Questions

Why 9 days?

We know not everyone can dedicate an entire weekend to an online hackathon, so we decided to spread things out instead!
This also allows us to properly discuss any changes instead of rushing anything.

Where is this happening?

This is an online-only, digital Hackathon. Contributions and formal discussion will happen on Finamp's GitHub repository, while community chat, tech support, and informal discussion will happen on our beta Discord server.

How can I attend?

Just show up on Finamp's GitHub repository and/or our beta Discord server sometime during the hackathon!
The only thing we require is for you to have fun, engage with the community, and hopefully contribute something to Finamp!

What are the rewards?

Yes! We're giving out free Finamp stickers to everyone who contributes during the hackathon time frame. What constitutes a contribution can't be defined explicitly, and we can't give out stickers for just fixing a typo or adding a translation. But if you redesign a screen (design or implementation), add a new feature, or fix a bug, we'll be happy to send some stickers your way!

Keep in mind that Finamp is an open source project, and is a free app. Finamp itself doesn't make any money, so we're funding the stickers ourself, using mostly GitHub donations :)

---

Let me know if you have any further questions!
We will make another post with more details on how you can get involved on the first day of the Hackathon, so stay tuned for that!

- Chaphasilor

TL;DR:

Digital Hackathon for Finamp, an open source Jellyfin music client.
Saturday, 2025-03-29 to Sunday, 2025-04-06, so two weekends and the week in-between. Looking for designers and developers, as well as anyone else interested in contributing! Checkout the GitHub repository and our Discord server for more info when the time comes!

---

Hey everyone!
I'm thrilled to announce that Finamp, an open source Jellyfin music player, will have its first Hackathon starting next week, starting on Saturday, March 29th and continuing until Sunday, April 6th!
Get ready for over a week of improvements to your favorite open source music client for Jellyfin :D

This is a digital event happening on Finamp's GitHub repository and our beta Discord server.

Why Should I Care?

In case you don't know, Finamp is a music client for Jellyfin, that has been around for a few years at this point.
It is meant to be an app that is tailor-made for Jellyfin (and all its quirks), and elevates the listening experience beyond what the official Jellyfin apps can offer.
While Finamp is used and loved by many Jellyfin users, it's far from perfect. Companies like Plex or Spotify are able to create more polished and feature-rich applications because they have more money and developers to throw at the problem.
But we, as Jellyfin users and members of the open source and self-hosted communities, believe that this shouldn't stop us from trying to build the best free & open source apps we can, together with other members of the community!

That's why we need your help to improve the quality and capabilities of Finamp, to be one day on-par or even better than the likes of Plexamp or Spotify!

What Is the Goal of this Hackathon?

As part of our efforts to modernize Finamp and make it more pleasant to use, we started redesigning and re-implementing Finamp in back 2023, and started releasing beta versions of the redesigned version early last year.
Many important elements of the app have already been overhauled, most noticeably the player screen & queue, and the download system. The redesign didn't just change the looks of these elements, but also improved their features and usability over the old version.

But there's still a lot to do!
We planned this Hackathon to give our redesign efforts a much-needed boost, so that we can finally redesign the remaining parts of the app and then release the redesign as part of the stable version.
So that's the focus - re-designing & re-implementing existing parts of the app, as well as implementing new features to go along with it.

How Can I Contribute?

Glad you asked :P
Since there's a lot to do, there are many possibilities to help out!
Here's a list of things we would appreciate your help with:

• Are you a designer? We need people creating mockups of the new design, based on existing functionality and feature request!
• Are you a developer? We need people implementing the mockups, enhancing existing functionality, or adding new features!
• Are you good at organizing things? We could use some help with keeping on top of things during the hackathon and beyond!
• Are you a user? While we don't exactly need more bug reports, you could help by going through existing bugs to see if you can figure out how to reliably reproduce them.

For the designers, we have a Figma file consisting of more-or-less up-to-date mockups of implemented and planned screens. But since we essentially just need mockups in the form of static images, you can work with any design too you want!

For the developers, while Finamp uses the Flutter framework (which is based on the Dart programming language), any frontend experience should be enough to contribute, since the syntax is very straight-forward and the style system is pretty self-explanatory.
Even backend devs can help out here, since there are some features that are mostly independent of the UI, like our playback, queueing, and download system.

What's the Timeline?

The Hackathon will consist of three sections: The two power phases during the weekends, and an iteration phase during the week in-between.

First Power Phase:

This kicks of initial contributions, and should see the first finished implementations.

Start: Saturday, March 29th, around 10.30am UTC
End: Monday, March 31st, during the early morning hours :P

Iteration Phase:

During this phase, more complex implementations can be worked on, PRs can be reviewed, and designs can be discussed.

Start: Monday, March 31st, around 10.30am UTC
End: Saturday, April 5th, during the early morning hours

Second Power Phase:

This final phase is meant to finish up any remaining implementations and tie up any loose ends.

Start: Saturday, April 5th, around 10.30am UTC
End: Sunday, April 6th, during the early morning hours

"Frequently Asked" Questions

Why 9 days?

We know not everyone can dedicate an entire weekend to an online hackathon, so we decided to spread things out instead!
This also allows us to properly discuss any changes instead of rushing anything.

Where is this happening?

This is an online-only, digital Hackathon. Contributions and formal discussion will happen on Finamp's GitHub repository, while community chat, tech support, and informal discussion will happen on our beta Discord server.

How can I attend?

Just show up on Finamp's GitHub repository and/or our beta Discord server sometime during the hackathon!
The only thing we require is for you to have fun, engage with the community, and hopefully contribute something to Finamp!

What are the rewards?

Yes! We're giving out free Finamp stickers to everyone who contributes during the hackathon time frame. What constitutes a contribution can't be defined explicitly, and we can't give out stickers for just fixing a typo or adding a translation. But if you redesign a screen (design or implementation), add a new feature, or fix a bug, we'll be happy to send some stickers your way!

Keep in mind that Finamp is an open source project, and is a free app. Finamp itself doesn't make any money, so we're funding the stickers ourself, using mostly GitHub donations :)

---

Let me know if you have any further questions!
We will make another post with more details on how you can get involved on the first day of the Hackathon, so stay tuned for that!

- Chaphasilor

Hey @everyone!

I just launched this year's Jellyfin Rewind, and I think you might be interested in it.
Jellyfin Rewind is similar to Spotify Wrapped, but made for people who use Jellyfin for their music listening. It let's you take a look at your listening habits of 2024.

If you're using Finamp's beta version, you can even import all of your offline plays to your Jellyfin server this year, since Finamp's beta automatically records all plays that couldn't be sent to your server.

To learn more, read the release announcement on GitHub: https://github.com/Chaphasilor/jellyfin-rewind/releases/tag/2024.0.0

Hey everyone!

I'm super excited to announce that Jellyfin Rewind 2023 is finally here! Another year has passed, and it's time to look back at all the music you've listened to!

In case you don't know, "Jellyfin Rewind" is an open-source version of Spotify Wrapped (& co.) made specifically for Jellyfin, that I initially created last year. This year, I've made some improvements and added a few new features, and tried to make it as enjoyable as possible.

You can find more info below, but if you just want to see your Rewind, use the links below:

Links

Local Network / Self-Hosting

If your Jellyfin server is only accessible on your local network, you will need to self-host Jellyfin Rewind so that it's also accessible on your local network. Otherwise your browser will block the connection.
To do this, check out the GitHub releases page and either download the zip-archive or use the provided Docker image here. The zip-archive will need to be extracted into a folder that is served by a web server, like Apache or Nginx. The Docker image will need a to have port 80 exposed instead.

HTTP (works for both http and https Jellyfin servers, as long as they are accessible over the internet):

Make sure your browser shows "insecure" / no lock at the top after opening the link, otherwise connecting to your HTTP-only Jellyfin server might not work!

http://jellyfin-rewind-http.chaphasilor.xyz

HTTPS (only use this if your Jellyfin server has an https connection and is accessible over the internet, this is the best experience):

https://jellyfin-rewind.chaphasilor.xyz

Download your Rewind report!

Please, please, please download your Rewind report at the end!

Jellyfin's statistics aren't very exhaustive, and any additional data could help offer you more insights during next year's Rewind! Especially if you don't have the Playback Reporting plugin installed, this year's Rewind report might come in very handy, so keep it save!

If something doesn't work and you can't download the data, I'll be happy to help you resolve the issue.

Something isn't working!

I'm sorry to hear that! I spent a lot of time trying to make everything as robust as possible, but everyone has a different server and different media, so it's no easy task.
There appear to be some issues on iOS with the browser tab crashing, probably because it's crunching too much data. If it happens to you, please try again on a desktop browser.

If you have any other issues, please comment below and include:

1. What isn't working?
2. Which device are you using to view Jellyfin Rewind?
3. How are you accessing your server? (local IP, public domain, https yes/no)
4. A screenshot could be super helpful.
5. If you are familiar with web development, some logs from your browser's dev tools probably have the highest chance of helping me debug the issue.

How does it work?

Glad you asked!
Essentially, Jellyfin Rewind loads most of the information about your music from your Jellyfin server, processes it on your device, aggregates some nice statistics, and then shows the result to you!

Your data never leaves your device; it's very similar to using the Jellyfin app on your phone.

Sadly the build in statistics of Jellyfin are pretty lackluster as of now, even with the Playback Reporting plugin, so that a lot of data has to be processed on your device. That's why it takes a few seconds to generate your Rewind report.

For next year, I might release a separate plugin that can use your Jellyfin server in order to crunch the data. This would also solve some of the connection problems that might happen this year. If you're interested in helping me with the plugin, please be sure to reach out!

Where's the source code?

You can find the source code on GitHub: https://github.com/Chaphasilor/jellyfin-rewind. There you can also find the files needed to self-host your own instance if you feel like it (under "Releases").
Self-hosting might actually enable you to use Jellyfin Rewind if nothing else works, because both Jellyfin Rewind and your Jellyfin server are running locally.

Can I help out somehow?

If you know something about web development, are a designer of some sorts, or have experience (or are curious about) developing Jellyfin plugins, I'd love to hear from you! There's so much I want to implement for next year's Jellyfin Rewind, and I need your help to bring all these ideas to life!

I had many more features planned for this year, but simply didn't have the time. I originally planned to launch back in November, and that obviously didn't work out :)

Thanks to everyone who uses Jellyfin Rewind, I sincerely hope you enjoyed it as much as I did!
See you next year!!! - Chaphasilor