That seems like a pretty naive and biased approach to software to me honestly.
Ease of use, community support, feature set, CI/CD etc..all should come into play when deciding what to use.
Freedom at all costs is great until you limit the community development and potential user base by 90% by using a completely open repo service that 5% of the population uses or some small discord alternative.
So then the option is to host on multiple platforms/communities and the management and time investment goes up keeping them in sync and active.
As with most things in life, it's best to look at things with nuance rather than a hard stance imo.
I may stand it up on another service at some point, but also anyone else is totally free to do that as well. There are no restrictions.
Unfortunately currently there isn't a true RAG implementation largely due to the fact that this site/app is fully self contained with no additional servers or database etc..which is typically required for RAG.
For now file uploads are stored in the browser's own local database and the content can be extracted and added to the current conversation context easily.
I definitely want to add a more full RAG system but it's a process to say the least, and if I implement it I want it to be quite effective. My experience with RAG generally has left me quite unimpressed with a few quite decent implementations being the exception.
I used Apple for the last few years until recently and I can't say I've ever really noticed stuff like apps faking being another app. That's not to say it doesn't happen of course.
I do know the Apple app approval process is definitely more strict than what is required for the Play Store.
I'm not very experienced with Apple or Android development so I'd be curious to hear from devs that use both platforms as well.
They’re just going to source the allowed parts from Red Bull basically exactly like they used to do with Toro Rosso.
To think that will equate to a RB19 is a bit insane in my opinion. They will likely improve, but still be a mid midfield team like they used to be with Toro Rosso.
That seems like a pretty naive and biased approach to software to me honestly.
Ease of use, community support, feature set, CI/CD etc..all should come into play when deciding what to use.
Freedom at all costs is great until you limit the community development and potential user base by 90% by using a completely open repo service that 5% of the population uses or some small discord alternative.
So then the option is to host on multiple platforms/communities and the management and time investment goes up keeping them in sync and active.
As with most things in life, it's best to look at things with nuance rather than a hard stance imo.
I may stand it up on another service at some point, but also anyone else is totally free to do that as well. There are no restrictions.