352 karma · joined September 5, 2022
that is exactly the problem. You have two relationships here: author -> patreon and author -> patrons. The first one is irrelevant, the second on is the problematic one. You cannot be anonymous in one case and not in another. That is not how business, law or taxes work - anywhere. Just because patrons do not want to know the legal identity does not mean it is legal to hide it. You could get sued for tax avoidance like that.
If you are making a platform you must make it universally usable. Just because one creator does not like or is missing some thing, you just cannot bend the platform to suit his needs. It just does not work like that.
Personally, I have solved the anonymity issue. It's not hard to do but it requires legal layering, which sounds way more complex than it actually is, but i don't want to get out my solution in here.
You cannot do business and be anonymous. The tax man would eat you alive. At least outside of USA. You also need a license as sole proprietor or be incorporated as a company in order to make repetitive sales and not one-offs. So again, no anonymity whatsoever.
"by works" payment model is illegal. You can receive donations or have subscriptions or pay per view but you cannot "maybe deliver", "deliver maybe one work, maybe ten". Again, illegal as fuck.
"Non quid pro quo patronage" - again, donations solve this. They are legal and easy without any hustle, as long as the payee is aware what is the purpose of that payment.
"api / audience relation system" - well, i am trying to run a business, why in the world would i give api access to third parties without being able to monetize it? each api call costs me resources. nothing is free. not to mention that giving access to api might go against my financial business altogether by moving some financial transactions out of my business into foreign business that is monetizing my api.
Author is very naive in his complaints in general. The red tape you have to go through these days for a simple(it's not a rocket science) website is astronomical. The technological issues(like finding a bank with an actual api that works and does not charge you per payment is close to impossible) too are unending hurdles being thrown at you form left and right and the bigtech-monopolized internet does not want you in it competing with their services or NOT using their services and infrastructure to build yours. You think streaming video is free? Try finding a place to host the video and send it over the network for amount that your income can cover and allow you still to make a profit. Good luck.
Yes, i have solved all these issues. But it is so damn hard, that these complaints don't even scratch the surface of how impossible it is to start something serious in this monopolized era of the internet and red tape. You just have no idea. You don't.
I do not use docker compose because each server is in active development so I cannot compile it into an image and I have to spin them all up manually. But I will use docker compose after i am done for front-end developers so they can keep developing the UI locally.
func Clone[S ~[]E, E any](s S) S { return append(s[:0:0], s...) }
looks just like Rust, which has the fugliest syntax I have ever seen. Personally I use maybe 3 or 4 generic functions to work with arrays(oh, sorry SLICES), otherwise I do not touch them. Could not care less about them and all that noise they caused.