We use the podcasters access which you get as the podcast host after claiming your podcast on apple or spotify. Using your host credentials, raw data is fetched from google/apple and stored in a local MySQL database. Subsequently, you can run custom queries on it and even derive additonal information which is not presented on apple's and spotify's podcaters dashboards (e.g. correlating data, using historical data, etc.).
Hey, we are Wolfgang and Matthias who build codeprints.dev and we would love to get your feedback on it.
We created codeprints because we both were looking for geeky art for our home-office. We found some older services which offered similar prints but they were all down and we couldn't order anymore. So we decided to build our own service to convert all the pain of our contributions into nice wallart ;)
What do you think about it? We would also be very interested in other ideas or designs how to convert data into geeky art.
I really like the idea. I have been looking for such a platform for a long time but couldn't find one. Therefore, I developed a quick solution for myself some years ago: https://constructeev.com/
I used it for many use cases (for my students, team, workshops). People were happy about it but some didn't trust it in terms of anonymity. Even computer science student who should know better. So maybe you can also address this issue.
Due to my experience you are in a very lucky position if there are too many good ideas popping up in your team. Of course, you also have to manage them and do some prioritization, in the best case together we the team to get the buy in and to find the most promising projects you want to work on. Maybe you also have to align them with company goals but so far, I haven't encountered a situation when ideas were impeding the business.
Usually, your runtime deps are still in your minified version and used during runtime. But in general, it might be a good idea to offer this as an option to the user how the money should be distributed.
Thanks a lot for all the helpful links and relevant questions. I agree, there is still a lot to clarify. I also see Recursive as a platform which could work together with other platforms. Recursive can't solve tax issues for the project owners but can be an additional source for donations which can then be received by any legal entity.
I really like the idea. Push to talk is a proven concept when a lot of people work together and should stay informed (e.g. fire fighters). I see a huge potential for it...
I know several people and also companies who would like to support Open Source financially, but don’t know how to do it in a fair way. Usually, there is just one approach, pick the most important library/project you depend on and donate some money to them. I asked myself if there is a simple method to support more maintainers with one donation, especially those who are further down the dependency chain and, thus, lack visibility. If you want to donate, for example, 100$ to 100 libraries, it is almost impossible to do it easily. You have to investigate for every single project if they accept donations, what platform they use for it, split the money, pay in the worst case 100 times transaction fees (credit card, bank transfer fees), and finally initiate the transactions.
I envision that you can donate on one platform and the donation is transparently and automatically distributed to all maintainers your project depends on. On the contributors’ side, this means that even if you are a small library down the dependency chain and don’t usually get a lot of visibility, you receive a small amount of the donation. I built a small mock up to demonstrate how it could work ... https://recursive.gives
As there are a lot of Open Source enthusiasts here, I would like to know if you think that it can work or if you have any other suggestion to tackle the problem.
We use the podcasters access which you get as the podcast host after claiming your podcast on apple or spotify. Using your host credentials, raw data is fetched from google/apple and stored in a local MySQL database. Subsequently, you can run custom queries on it and even derive additonal information which is not presented on apple's and spotify's podcaters dashboards (e.g. correlating data, using historical data, etc.).