mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

344K
active users

A late :

This week, let’s share services that helps you give back to the OSS community at large:

- @stackaid - like Flattr it works with a fixed monthly fee of your choice which it then splits between all first and second level dependencies of your projects
- @opencollective - a site through which you can donate to projects, but more importantly, a structure that can host the money of OSS projects
- @tidelift@floss.social - like @stackaid but adds legal protection and is geared at enterprises

@voxpelli Ok, so the remuneration goes to projects that registered specifically for @stackaid and the payment method is to go via github?

@clacke They divide it across the dependencies of all the projects you register in it and if I remember correctly it adds your new GitHub projects automatically.

You can remove projects and filter out receivers.

Then it looks at the subdependencies and forwards part of the money to them.

And lastly it pays out to registered projects through Stripe or they try to find the projects on GitHub Sponsors or OpenCollective and forward the money there.

If they can’t, that money gets redistributed.

@clacke You donate through Stripe, this enables a site like StackAid to not have to deal with much of the money as it never leaves Stripe, they handle the forwarding from giver to receiver

@clacke The laws around money transfers are such a pain, it was one of the biggest challenges we had when we built Flattr back in the day, so it’s great that Stripe has enabled innovation there now through stripe.com/connect

stripe.comStripe Connect | Platform and Marketplace Payment SolutionsStripe Connect is the fastest and easiest way to integrate payments and financial services into your software platform or marketplace.
@voxpelli I'm looking at www.stackaid.us/#payments and it doesn't mention them proactively trying to find recipients:

> Owners of open source projects can claim their repositories by installing the StackAid GitHub app. As part of the claiming process, owners can associate one or more Stripe accounts with each repository they own to receive payments.
www.stackaid.usStackAid - Fund all your open source dependencies
www.stackaid.us/#reallocation

> A project's allocations accumulate for 2 months. If the project is not claimed by then, an automatic reallocation happens and the amount is redistributed to the other dependencies that are claimed.

I wonder if this means that at this early stage before many people heard of this and enabled their claims, a lot of funds will end up at the transitive dependency of last resort, @stackaid themselves?
www.stackaid.usStackAid - Fund all your open source dependencies
@stackaid Maybe there's a good methodology for what happens when none of my dependencies are registered recipients, but for me as someone just discovering this, I'd really like to see documented what happens in this case before I sign up.
StackAid

@voxpelli @clacke @opencollective

Sorry for the late follow up here. A couple of thoughts to address your questions:
- While we are in the beta period, we are not re-allocating funds for unclaimed projects.
- We do crawl all your dependencies looking if the have some other means of accepting funds, be it via GitHub, OC, Patreon, etc and use those methods for distributing funds
- We work hard to allocate as many of the funds as possible and will never be the last recipient of unclaimed funds.

@stackaid @voxpelli @clacke Happy to help you match dependencies with their Open Collective (if any). We can look at some data set and see if we can find some that you don't already have.