Today I continued working on my File Encryption Frontend, nothing functional, yet!

The icons are selfmade, I think at least the folder icon is pretty.

Our programm will have something like a Zip-Explorer feeling too it, but our aim is still encrypting files to the unbreakable point.

Looking good! Will it be open source? :)

@Alice sadly, it's not a real video file. I tried clicking on it but I knew it wouldn't work.

@ScriptCoded I won't think it will be that open. We may release the source but won't let anyone publish their own version.

It's not really decided yet, I'll keep you up to date ^^

@SteffTek Ah, I'm crossing my fingers. Would be fun to add theming support :)

@ScriptCoded That's a feature I would consider ^^

@SteffTek Just tell me ;)

I still get distracted by the orange titlebar. Feels like an error to me.

@JFK422 just imagine its blue, better now? ^^ JK - maybe i'll add theme support

@SteffTek Depending on the target group, some might not use your software if it isn't open source.
Especially in cryptography, there had been a few scammers around - promising secure encryption but giving away nothing.
You certainly know what you are doing and are delivering good software, but not anybody knows that.

@sbiewald just because we may not allow code modifications doesn't mean our code for won't be visible ^^

@SteffTek What do you mean by no modification?
'You may not share your modification' or 'you may not do a private modification'? I guess you mean the the second one.

.

@sbiewald probably share. I think I cannot forbid private mods ^^ and I am just talking about the backend. Frontend is done in Electron so it's pretty customizable. ^^ we'll see, it's a long way to go

Please share BiggerTits.mp4 for reviews.

@ScriptCoded I thought about the Creative Commons Attribution Non-commercial license. Your opinion?

@SteffTek It's a good licence. It allows people to modify, but still ensures that you hold the rights to earn money of it. I'd go with the ShareAlike version of it, to be sure that others share on the same premises. Not much more difference, but it covers the possibility of someone else making it closed source. :) Though I'd much more prefer the normal non-commercial over proprietary ;)

@ScriptCoded I think you can share with that license ^^

@SteffTek An alternative would be to only make parts of your code base open source. For example, if you split your front-end in to a separate repo (assuming you haven't already) you can release that, but still keep your encryption and back-end to yourselves. Not only would that give you complete control over where it's used, but perhaps also cover the encryption and make it a tad more secure. Although I strongly believe that publishing as open source more quickly covers security flaws, assuming that there is a community backing the software.

@ScriptCoded I splitted my project into 2 different repos, but on my private local git.

Because our backend is written in Java everyone could decompile it unless were going for obfuscation (got a pretty good selfmade obfuscator) but we thaught the community won't like obfuscation. I don't have any problem releasing the frontend under a sharable noncommercial license, I just think about our backend...

@SteffTek Ah, I see. So what you're saying is that you're screwed anyways? 🙈

@ScriptCoded I think we'll release the frontend on a sharable non commercial license and the backend on a closed one but with accessable source code.

So everyone can see it but not use it. Also I'll definitely set up a donation page xD (even if donations aren't tax free in Germany)

@SteffTek Nice! Make some noise when it's live!Dick move to put tax on donations btw 😅

@ScriptCoded I'll keep you up to date ^^ and yes... Donations are income in Germany

@SteffTek Why couldn't I use the source code if it is accessible?

@sbiewald I didn't say you couldn't, I said you shouldn't. Imagine someone creates a different version of our encryption tool and legally uploades it. Instead of encrypting it steals your data. Wouldn't be good, would it?

@SteffTek You mean like faking your brand? It is still illegal with every license. Also data theft is already illegal :)

@sbiewald Im not talking about brand or sth like that. Im talking about "oh yeah enhanced Version" Like. Sure the theft is illegal, but not the Version. And it makes my whole app looks shady ... :/ But frontend app should be open