Streams is basically an acknowledgement that my work has no value to anybody but me.
I can't speak for anyone else but I appreciate all that you do.
There are no targets. Streams is not a product or fediverse project. I don't care if 10 people use it or 10 million. Doesn't matter to me at all. It is a repository of code. Nothing more.
"Zap died because it was dead. Five years of hard work and it failed to interest more than a dozen folks across the entire planet."
"Streams is not a product or fediverse project. I don't care if 10 people use it or 10 million. Doesn't matter to me at all."
"Success has little to do with performance, winners & losers are chosen by society."
We just must not repeat the mistake of only trying to talk to potential devs or potential instance admins. We have to reach out to aspiring end users first and foremost. Devs and admins will come in their wake. FLOSS people aren't keen on developing something they've never even tried using.
UI/UX has to find ways to present things that easy that such understand it in 10 minutes.
I think Friendica would be the easiest case.
[Streams is] only a code repository which you can yoink and make something nice out of. Streams says, "Fork me!"
what Streams needs more than Hubzilla is reference implementations that show in practice rather than in theory what can be done with it.
Because modern Friendica uses AGPL, you cannot use any of modern Friendica's code in Streams or Hubzilla, because it would change the license. Streams and Hubzilla stuff can go into Friendica, but not the other way around.
One of the key differences between GPL and AGPL is that software-as-a service or cloud hosting providers and developers must release their modified code under the AGPL if they use AGPL code. You don't have the same issue with GPL code.
Does AGPL and GPL make a difference here - don't think so.
GPL: if you use any GPL code on your front-end, or any other code that is being “distributed” to users, your entire codebase needs to be open sourced. You are free to use GPL on the server side without having to open source your code.AGPL: AGPL takes the above and applies it to the backend. So if you use any code licensed under AGPL anywhere in your application, you need to release the source code for your entire application.
AGPL: AGPL takes the above and applies it to the backend. So if you use any code licensed under AGPL anywhere in your application, you need to release the source code for your entire application.
Why not give Hubzilla and Streams a better UI?Building a theme is actually easier than writing the back-end stuff.