Funkwhale @funkwhale@mastodon.eliotberriot.com

@ScriptFanix tu peux éventuellement réduire la conso de ram de funkwhale en suivant les instructions ici: https://docs.funkwhale.audio/installation/optimization.html
mais c'est pas sur que ça suffise :/

@ScriptFanix qu'est-ce qui s'est passé ?

@pupy Thank you <3

We have reimplemented big sections of the Subsonic API (Subsonic being another audio server with a rich ecosystem), meaning we have at least 2 android apps that you can already use to access music from one or multiple funkwhale instances.

https://docs.funkwhale.audio/users/apps.html

Support on IOS apps is still unclear because we miss some bits of the API, but it will definitely come at some point!

@skotperez @zatnosk in this scenario, you start a mopidy server with our plugin installed on the device you want to control.

Your Funkwhale library will be available for music streaming, and you'll be able to control the queue remotely using any Mopidy compatible app from the ecosystem.

@skotperez @zatnosk depending on what you mean by "control the server" you may or may not find differences in Funkwhale.

The main one is that streaming sessions are not shared accross devices : you can open the app in two different computers and stream different things in parallel. This also means you cannot control the session of one device on another.

However, we have an experimental Mopidy plugin (https://code.eliotberriot.com/funkwhale/mopidy) you can use to support this use case as well.

@zatnosk yes, this is one of the use cases we support! You can host your own, private music library on it and use a subsonic-compatible app (https://docs.funkwhale.audio/users/apps.html) to access it on mobile devices :)

@dansup there is also a strong incentive for doing so, as music is a scary place in terms of copyright infringement laws / regulations :D

@cirku17 you're completely right, there is a strong necessity to have track licence stored in the DB and displayed obviously in the app.

We have an open issue for that, and the implementation is planned for the next release, but I'll add a reference in the moderation issue as well :)

Ok, it's time shape Funkwhale's future, in terms of moderation and anti-abuse tools!

We can and will reuse tools from existing projects, but there are also things we'll have to work out ourselves.

If you want to be a part of that, the whole discussion will take place here: https://code.eliotberriot.com/funkwhale/funkwhale/issues/580
(you can answer this post as well but please read the issue before!)

Take the time you need to read / contribute. the issue will remain for at least a few weeks before any implementation happens.

@pybyte you can use it as a medium to distribute your own music, but there is no builtin way to monetize your content. Open.audio is a good example of an instance for creators :)

Support for tips is planned on the long term.

@d7dd0d awesome, thanks :ok_hand:

@d7dd0d oh, nice catch ! Do you mind filing a bug about that on our issue tracker ? https://code.eliotberriot.com/funkwhale/funkwhale/issues

@d7dd0d depending on your browser, this is indeed possible since files are not (yet) transcoded by the server :)

@neon yes, this use case is completely supported since version 0.17 (it was one of the reasons of the big overhaul)!

1. Create a private library
2. Import your tracks in this one
3. Share the library link with your friends (or the people who should have access)
4. Accept their follow requests on the library
5. Enjoy!

It's not done at the track level though, so users following a library will have access to all the tracks in this library (including tracks you add in the future).

@octalish @funkwhale Come to the dark side, we have coo... music!