[BUILD] private libraries error

[witchfindertr]

Git error. Command: git clone --mirror https://github.com/MSOB7YY/flutter_scrollbar_modified C:\Users\rssmo\AppData\Local\Pub\Cache\git\cache\flutter_scrollbar_modified-12875d6fecb8ca42576de23fe99c70fab4fd3a98
stdout:
stderr: Cloning into bare repository 'C:\Users\rssmo\AppData\Local\Pub\Cache\git\cache\flutter_scrollbar_modified-12875d6fecb8ca42576de23fe99c70fab4fd3a98'...
remote: Repository not found.
fatal: repository 'https://github.com/MSOB7YY/flutter_scrollbar_modified/' not found
exit code: 128
Process finished with exit c

[Red6785]

What are you attempting to do that is causing this error?

[MSOB7YY]

hellow witch, currently there are number of libraries still private, playlist_manager, queue_manager, history_manager, basic_audio_handler, etc

nothing much but the project is big & new and i just don't want people stealing it claiming ownership to third parties, however, im considering making it public if it ever got recognition, hope u understand and sorry for that 🌺

[ahdyt]

yo MSOB7YY/dart_extensions also private

[hbatalhaStch]

hellow witch, currently there are number of libraries still private, playlist_manager, queue_manager, history_manager, basic_audio_handler, etc

nothing much but the project is big & new and i just don't want people stealing it claiming ownership to third parties, however, im considering making it public if it ever got recognition, hope u understand and sorry for that 🌺

what if you obfuscate the code from those private libraries and release them as a package? This way you can protect your code and still let people build the app,

[MSOB7YY]

@hbatalhaStch and how can one obfuscate code so that it's build-able but non-readable ☠️

[hbatalhaStch]

@hbatalhaStch and how can one obfuscate code so that it's build-able but non-readable ☠️

https://github.com/BankingofThings/dart-obfuscator
Didn't test it though

But tbh I just didn't think this idea through, I also assumed there would be a (official) way to obfuscate a flutter/dart packages the same way we do in JS (e.g. JQuery)

[MSOB7YY]

@hbatalhaStch obfuscation means making the code unreadable only in case of reverse engineering an apk file, it just changes how one could read and understand a function/etc, making it harder. in our case it wouldn't matter much since the real issue comes as soon as u have the code and are able to build
i would have considered close sourcing and use only play store but

1. YouTube client won't be possible on play store
2. i don't really mind ppl seeing/copying some code, it's how we learn

my real issue is with copying whole namida and building under different name or sussy code, which i cant really find good solution for without affecting nice ppl who just want to build and learn/contribute
sorry again

[hbatalhaStch]

@MSOB7YY I installed the app today and it is an amazing app, I would sure learn a lot from it and hopefully contribute it to it.

my real issue is with copying whole namida and building under different name or sussy code

This will always be an issue even after you get recognition. Every open-source project face this.

I want to ask you: how do you measure the recognition you receive (number of repo stars, number of installs, sponsorship) ? When will it be big enough to make those projects public?

[MSOB7YY]

@hbatalhaStch thank u so muchhhh <3 hope u learn as much.

ikr, but getting recognition makes it almost impossible for someone to do it, its like forking firefox and selling it as "your" browser ☠️

probably number of repo stars, its just a direct way to measure how many ppl know about namida, i don't have specific number tho, just the amount that shows it's now well-known

[John-Gee]

Without being on a store I fear it's quite hard to become well known on Android.

[MSOB7YY]

@John-Gee not quite easy

1. Google play:
   • YouTube client with download support
   • manage all files permission
   • possible donations
2. FDroid:
   • code is not currently fully open sourced

[John-Gee]

Yeah I get that, it's a tricky situation.
For Google play you could offer a stripped version and maybe a paid version (which could be the same as with ppspp or enhanced as with fairemail).

I also wonder how this semi proprietary thing affects users. Most users on play store obviously wouldn't care, but this is GH where people would expect some form of FOSS (that's what I expected when I followed your link in reddit, but having seem many for profits clones of FOSS projects I get you. Yet my whole point was to replace AIMP with a FOSS player so not sure what's next...). Would a disclaimer towards the top of the readme help prevent some from feeling baited?

[MSOB7YY]

there is a whole section with the info of building, i understand that some people expect fully open source but can't help it, its a site to share code/smth u made, not a "free code to use" site.

as for google play, i thought about a stripped version but it just aint useful, now namida would be just a normal music player (which is not even the main selling point) so idk not interested to deal with gp shit now.

as a user u don't really care wether it's foss or not, as a dev u also shouldn't, since bothways the license is not for complete ownership usage. the part of code that is privated is to only prevent unauthorized builds which is smth i don't wanna bother myself with. sorry for that i just wanna share my app