Yeah you're right. I switched it to AGPL.
Thanks, haha. I'd love develop a Native App for it too but this is a zero-budget Project (aside from the Domain). PlayStore has a one-time fee so that's 25€ for Android + 8€/Month for the IOS AppStore just to have the App on there.
In theory, I could just have a downloadable .apk for Android to circumvent the fee but most people don't want to install a random .apk from the internet. And I'm not developing a Native App for like 3 people excluding myself (I'm an iPhone user).
Soo, yeah that'll probably not happen :(.
it’s implied it’s licensed under "all rights reserved", so not open source!
Oh, I actually did not know that. I'll try to remember adding a License right from the get-go from now on, thanks :)
It's GPLv3 now.
Thanks for the suggestion, I’ll definitely try to make the app as language inclusive as possible!
Also, sorry if I might’ve been too vague with the post title. The app is just similar to Duolingo in terms of structure and the idea, however it’s not specific to language learning but supposed to cater to any subject, really.
For example, I personally use it to study for my university subjects.
Well it's open source, so whenever there's demand someone will fork and maintain it, if the original team ever leaves.
This should be the community icon.
You already have 13 on your comment. You're like a lemmy celebrity now.
What is it like being famous?
takes notes for my own App 👀
Very good point! I think @TheButtonJustSpins@infosec.pub has a good idea on how to circumvent that.
I could make my own database with hashed passwords using postgreqsl and RLS, which is pretty secure. The User then decrypts the hashed passwords once on login and is simultaneously logged into multiple instances of Lemmy to get the JWT of each instance, which is then stored in SessionStorage or even in a Cookie if the User wants to which would make this a one-time process.
On signup the User could just register to one instance and then I just generate random 32 Character passwords and hash them with the Users' password, then get the JWTs and if cookies are enabled the that would only have to be done every year or so (or when the User deletes the Cookies).
This whole process is seems pretty easy, especially if you've done something like this before and I'm betting some other App Dev is already taking notes lmao.
Edit: Let's also do a thought experiment on what data will be leaked if I did this 1:1 and the database gets somehow hacked:
For each User:
- Username (=> Gives away that you use Nemmy)
- Hashed Passwords (=> Hashed passwords cannot be read if you don't have the original Users' password until we have access to quantum computers which can literally crack the encryption algorithm)
I'm making an App for Lemmy and I'm planning on adding that feature. I also want to make it so you only have to register once and the App can register you to all the instances you choose automatically.
Edit: The Webapp is Nemmy, also the Community !nemmy@lemmy.world
Edit2: Please note that Nemmy is early Alpha, so not really useable as a daily driver yet.
Edit3: Changed Community link to proper format
Never heard of that actually. Main difference would be my web-based approach with a cloud, which works on any device. You also don't have to run the LLM on the same device (which seems to be a must with SillyTavern?).
The Character Cards database looks very interesting though! I will definitely look into writing an importer/connecting service.