Hey #Fediverse #Musicians - I'm once again trying to figure out premium pricing for #Bandwagon
-
replied to Ben Pate π€π» last edited by
@benpate for copyright, you'd have to deal with clearing licenses more wouldn't you?
I'd probably suggest things like more features + seller tools
-
-
replied to Ben Pate π€π» last edited by
@benpate The first two make sense to me because of licensing and payment processor fees you might have to cover. The third one could, because of storage costs, but the first two should be enough to cover that cost?
Also if you were to do the third, how would you count that to prevent abuse? If someone stored a huge 100GB album, that's gonna cost a lot more than someone hosting 12 albums at like 30MB each or whatever it is. And if you were to set a storage limit instead, that might end up cutting off some albums in odd places. It might be better to skip over that one unless you need it, just because of how difficult it would be to measure and get right.
(and just in case the options are in a weird order, I see it as publish copyrighted music, sell music online, host large libraries, and need extra features) -
replied to Ben Pate π€π» last edited by
@benpate First I've heard of this...I'll do a deep dive and read up. I might have some thoughts to share.
-
replied to Monarkie last edited by
Thank you.. Iβd love to hear your thoughts!
I know how to make software, and how to price things, but I'm a little out of my element with music and IP licensing. So I'm leaning on the Fediverse community for everyone's advice. You guys always have the best ideas.
-
replied to Ben Pate π€π» last edited by
@benpate take a (reasonable) cut on sales. Make commercial entities pay. Donβt charge/penalize indie artists. No artists, no bandwagonβ¦
-
replied to Blake Leonard last edited by
Thank you! And yes, I think we could probably cover costs just by charging for any one of these.
I want to make it fair for small guys just starting out. I learned long ago to go out of my way for the "small customers" because when you do, they often grow into big ones. The best outcome for this would be for bands to get started on Bandwagon, then stick with it once they get a break
-
replied to Emelia πΈπ» last edited by
Yes, I likely have to do more to protect copyrights. Right now, it's just a checkbox when people sign up, declaring that they will only upload music that they have the rights to.
From there, they can choose their licensing terms on an album-by-album basis.
-
replied to sknob β last edited by
Yeah, that seems to be the consensus so far⦠so that's probably my answer.
And absolutely - "not penalizing indie artists" is certainly the goal.
And, can I just say how awesome the Fediverse is, as a platform for validating product designs? If I'd had this in 2005, I couldβve done so much moreβ¦
-
replied to Ben Pate π€π» last edited by
@benpate @sknob I agree with this absolutely in principle but you have to get a reasonable number of sales on the platform for that to cover costs.
While I hate the idea of charging artists, someone has to pay the hosting fees at the end of the day, just as with a Mastodon server instance.
Have you chatted to the @mirlo folks? They take a cut of sales but are still asking for donations as well, so I suspect that cut doesn't cover their costs (yet).
-
replied to keef last edited by
@keefmarshall @benpate @sknob @mirlo
Possibly controversial opinion: Do the cut per sale, but also charge on large libraries, as that presumably directly influences costs. As opposed to elsewhere in the thread I would determine library size by total length (rather than file size of the uploaded file, or the number of releases or tracks).
Edit: the total length should probably be based on the actual track length, rather than what we put into the length field in the form
-
replied to keef last edited by
@keefmarshall @benpate the eternal chicken and egg problem (the egg came first, but thatβs a question for another time ).
The question is does BW want to make a decent living off of BW or just cover costs? I have doubts the former is possible since 99.9% of musicians can no longer make a decent living off of making music.
I would also ask listeners for donations. And maybe charge for help installing/configuring independant BW instances.
-
replied to sknob β last edited by
@keefmarshall @benpate sorry if that sounded too glib.
There is a scenario where BW becomes a goto site for artists and listeners, but that wonβt happen overnight, and charging artists from the get-go would probably delay such a scenario.
-
replied to AxWax last edited by
@axwax @keefmarshall @benpate @sknob I agree that charging should be related to sharing the benefits (sales) and costs (hosting, development, admin...) About hosting, the collection size isn't as expensive as the traffic generated, right? Something to consider. Maybe you have 12 albums nobody listens (generating little cost). Then again if someone generates a lot of traffic, they are also contributing to the awareness and use of the platform (more listeners) so taxing that is tricky.
-
replied to keef last edited by
For what it's worth, we just voted to make our platform fees a an artist's choice based on what they can afford. We'll roll that out in the next month or so with a more formal announcement than this
We originally based our take rate decision on this math: https://mirlo.space/team/posts/16/
We've now had a year worth of data to reflect on. We're able to cover costs of running the server through our own monthly patronage, but the transaction fee comes no where near.
-
replied to mirlo.space last edited by
One of the things we want to be clear about in our messaging is that it is a collective effort to keep these kinds of platforms running. We can't rely on the "heroic labor" of individuals.
-
replied to Ben Pate π€π» last edited by
@benpate Have been thinking about this same thing for TIBR. Just some spitballing here:
One way (which could be combined with others) is the patronage + rewards model. Offer monthly patron tiers. Give certain tiers (higher $) "rewards" that provide access to certain tools. It's sort of a "softer" subscription model.
Someone mentioned sponsorship (by a trusted entity) to me today. This is probably more of a fit with TIBR, but there could be a way to make it work for BW maybe?
-
replied to Ben Pate π€π» last edited by
@benpate OK! So, I registered on the platform and uploaded some music and I like it! I would have some ideas on minor tweaks, but I love how this is working and it being federated is fantastic!
I voted for paying for "Need Extra Features"
Personally, I would love for people not to feel like they have yet another barrier to putting out what they have and I think with Bandcamp offering a free model (with "pay for extra" functionality), it's something that might convince folks to be here...
-
replied to keef last edited by
@keefmarshall @benpate @sknob The server costs question is also related to how the decentralized Bandwagon will actually work. If everyone piles up in the first instance Γ la mastodon.social, then yes, that will be expensive. If it's easy to set up specialized instances and federate content / searches, then the costs are more spread and affordable for different types of hosts. I wonder whether it is too early to imagine how that federated future will look like.
-
replied to Ben Pate π€π» last edited by
@benpate the βcc is freeβ model seems very fitting for the fediverse, and iβm not sure why people think it would complicate things.
as keef pointed out, cc is a license; it does not βundoβ copyright. itβs already an βhonor systemβ of sorts where anyone uploading now needs to be honest about either being the rights-holder or that the piece in question is permissively licensed such that they can upload it. βall rights reservedβ doesnβt fundamentally change this.
-
replied to bri last edited by
Yes. Thanks for the clarification. I need to find better language to differentiate the regular βall rights reservedβ license vs the various CC licenses.
Perhaps thatβs it.. since theyβre all copyrighted, itβs the LICENSE that matters.
For now, please hand wave over that detail in my character-limited poll questions, and know that weβll do the right thing when we figure out the actual policy. π₯Έ