Iceggiren i Dictionariez: Your Dictionary, Your Language
Dictionariez: Your Dictionary, Your Language sɣur River Young
Tiririt sɣur River Young
Tiririt n ineflayen
yeffeɣ-d deg prije 14 satiAha, the good old days! I remember ~10 years ago when I just started this project, the internet was like the wild west. Cookies hadn't eaten the world yet, and I just checked every permission that I thought would be useful for this tool. Neither Firefox nor Chrome couldn't care less, my extension just lived its best life, silently running on every website it visited.
Then, maybe about four years ago, Firefox gave me a reality check. They told me, "Hey, you need to explain these permissions and get actual consent from user, or we will pull the plug." I was spooked! I told them, "But I don't collect anything!" and Firefox basically replied, "Naj, you’re handling a ton of data. You just don't realize it."
So their solution is that instead of making developers write long essays, browsers now show those "scary" popups warning you that I have access to all data on all website etc. It sounds intense, but it’s all in the name of transparency. And on my side I’ve had to write a proper privacy policy to explain every bit of data I handled.
I’m not complaining, though. I’ve learned that privacy is a core value, and data is just as valuable as money, and losing it usually means losing freedom. I’m still a minimalist at heart: I don’t collect anything unless it’s 100% necessary. I don't even use web analytics like most other devs do. If I absolutely have to handle data for a feature to work, I make sure it’s declared in the app, documented in the policy file, and write about it on my site or in my blog post.
To address your concerns (which are totally legit):
1. The app is open-source.
2. The privacy policy is transparently hosted on GitHub and Firefox.
3. Most of the app works right out of the box, no login or registration required.
4. For free features, zero data is sent anywhere. Only some Pro features require a server to function, which is why those need a login to handle things like the specific word or sentence you’re translating.
Thanks for the feedback! It’s great to see people actually care about their privacy. It keeps me on my toes and makes me a better developer.
Then, maybe about four years ago, Firefox gave me a reality check. They told me, "Hey, you need to explain these permissions and get actual consent from user, or we will pull the plug." I was spooked! I told them, "But I don't collect anything!" and Firefox basically replied, "Naj, you’re handling a ton of data. You just don't realize it."
So their solution is that instead of making developers write long essays, browsers now show those "scary" popups warning you that I have access to all data on all website etc. It sounds intense, but it’s all in the name of transparency. And on my side I’ve had to write a proper privacy policy to explain every bit of data I handled.
I’m not complaining, though. I’ve learned that privacy is a core value, and data is just as valuable as money, and losing it usually means losing freedom. I’m still a minimalist at heart: I don’t collect anything unless it’s 100% necessary. I don't even use web analytics like most other devs do. If I absolutely have to handle data for a feature to work, I make sure it’s declared in the app, documented in the policy file, and write about it on my site or in my blog post.
To address your concerns (which are totally legit):
1. The app is open-source.
2. The privacy policy is transparently hosted on GitHub and Firefox.
3. Most of the app works right out of the box, no login or registration required.
4. For free features, zero data is sent anywhere. Only some Pro features require a server to function, which is why those need a login to handle things like the specific word or sentence you’re translating.
Thanks for the feedback! It’s great to see people actually care about their privacy. It keeps me on my toes and makes me a better developer.