If you knowingly sell users a service with vulnerabilities that isn’t a good ethical practise to be honest (not saying it does, just saying you implied it does).
The point of (F)(L)OSS is that users can enjoy using a service with freedom and lack of bugs or vulnerabilities whether or not it is paid. The people who fix these bugs are the developers themselves by users who report it or more importantly, the users themselves. It is completely up to you on how you plan to release your service(s), but certain decisions may benefit both you and your customers
On another note I think a lot of people would actually appreciate StreamX as something you can host yourself (c: @FxllenCode ) and it doesn’t have to be free. The reassurance that you have control is enough and it eliminates developer’s reliability or burden on them, because they don’t have to worry about server issues or anything.
I completely agree. If I made an product that had a few vulnerabilities here and there I would probably only release the product as an beta for beta testers. Nevertheless StreamX is still a very good product it reminds me of PartCache and StreamingEnabled except they are combined into 1 product.
Ooo… Nice! I have an question does StreamX support NonPart Instances such as: SurfaceGuis, ViewportFrames, etc. Since these can use on resources a bit.
I hate to be that guy, but you’ll lose a lot of money. Like, a lot. That much Robux isn’t going to pay for (I assume) the immense amount of infrastructure and storage StreamX needs.
