• 1 Post
  • 31 Comments
Joined 11 months ago
cake
Cake day: January 19th, 2024

help-circle



    1. Turning into an executable is compiling as far as C goes. For Python, there probably is something somewhere to wrap a script into a .exe.

    2. For the UI: what matters is the data you generate, not the fluff around it. As the other commenter said, start with a CLI program. You can easily nest several levels of menus if that’s your thing. This allows you to have user input. Then for outputs you can do it to a .txt or .md file. Use simple text-based formats. Then once you’ve got that down you could build a GUI? But tbh I have never built a GUI and I’ve been programming for 10 years at this point so I can’t help you out. There are simple cross-platform libraries you can use out there






  • Got you. It is a shame that this part of crypto is not more widely publicized, as it is its most interesting use in my eyes.

    Still think it can’t be the only solution if we want wider reach. To avoid taxes and legal structures, I want to study whether we can interface with projects’ available donation options and automatically split a user donation into several. Skipping the “finding the donation option for each project” problem which can be tediously human-solved for a proof of concept, the issue would be whether the process could be easy for the user while not getting obliterated by transaction fees.

    There is no need to develop a crypto side since I’m sure a way to interface with Kivach could be found if the other fiat currency problems are solved beforehand.

    Thank you for your input, it means a lot.






  • The solutions you linked are interesting but ultimately neglect the most important aspect in my opinion: discussion among stakeholders. They also tend to use bitcoin, which has proven it could not gain enough traction to be mainstream yet.

    Taking the core principle of Kivach and making it viable in state-backed currency, using the platforms devs have already set up for payment would be a great leap forward. We need to get something going and build support from a critical mass.

    Why is Kivach not more widely used? We should tackle these questions and try to improve it.


  • You are indeed a good motivator! The reason I did not want to make this post at first is that I need everything: people to brainstorm with, people that can carry the project, people with the skills to create a prototype, people who can convince FOSS projects to get on board, and people willing to encourage others to donate.

    Overall too much labor, skills and connection for one person. I believe we would need a team of 10-15 volunteers, some already involved in projects, to put something up



  • That would be a nice option for web-based stuff. I guess the whole difficulty is to get a list of projects and to publicize it widely. I also believe donations should be stupid simple or they will never take off.

    The main difference between your idea and mine lies in who decides where the money goes. I do not think end users should decide 100%, because that ignores a lot of critical under-the-hood software. Users must however have a completely transparent report of who gets what. I guess at that point they should be able to adjust it to their whims, which circles back to your point 1.


  • Among distribution rules to be discussed, one of the first points would be who is eligible. I would not want corporations to be supported by these donations, but some companies actually focus on FOSS as a service and I could see them getting in on it. I would exclude devs employed at a company getting paid to contribute as well.

    I think this would not drastically change the status quo. Today, corporations contribute to FOSS, but mostly to make sure their hardware or other software is well supported. They will still have that incentive if there is a central donation system that excludes them.