Hacker Newsnew | past | comments | ask | show | jobs | submit | more golanggeek's commentslogin

Is there any implementation yet on how this could be done?


Do you mean that I’m too exhausted before I even start watching TV and then I do watch TV. If so, very interesting. Do you know of some studies which you can point here.


Yes, that's what I mean. No, I don't have any studies at my fingertips. I just recall reading it at some point and it works well as a rule of thumb for me, though I don't even own a TV. Still, if I am playing video games and surfing twitter instead of working, I'm usually too tired to actually work.

Passive consumption of media does not take as much concentration as being productive.


Nice.. Thanks.. I will try better diet and working out..


That would be a good start. Let me try that.


:) I did try to pull the plug off. Somehow my addiction makes me then watch some video over the phone. I mean I know it sounds stupid that I do this. But I’m doing it day-in day-out. Hence asking here!


Ditch the smartphone then, or lock out youtube, and uninstall the video streaming platforms.


cwinter does Locust also support scalability across machines.. what is the timeline for it to be production ready..


Could you let me know the kids app that you are speaking about.


Kindle free time is what we use on our kids. It's built into the Kindle and you can upgrade it to a 3$ per month Kindle unlimited for kids books.


Kindle Freetime


Thats awesome, to use it with emacs


Very nice article. Also about the Bombay Blood Type


What you found are just bugs. But their main point is indeed security - compared to say simplenote. Here everything is indeed encrypted and they have no way of reading our data


Are they just bugs?

    encryptText(text, key) {
        var keyData = CryptoJS.enc.Hex.parse(key);
        var ivData  = CryptoJS.enc.Hex.parse("");
        var encrypted = CryptoJS.AES.encrypt(text, keyData, { iv: ivData,  mode: CryptoJS.mode.CBC [...]
The basic encryption operation seems to be AES CBC with a constant, reused IV.


Items are encrypted with random keys. No two items are ever encrypted with same key. Thus no need for IV, and makes implementations across platforms simpler.


Is there actually any description of how you're encrypting, how you manage and distribute keys, why you believe this is secure, why you're not using an authenticated mode, etc? "Thus no need for IV" when your desktop client just pulls a minified blob from somewhere is not particularly reassuring.



> What you found are just bugs.

Most security issues are.

Unless you have an extensive background in application security, especially on the stack that you are using (Electron, etc), then don't advertise security as a feature. Let someone else who knows how to crack 'secure' apps decide if your app is secure or not.

As Bruce Schneier famously quipped, anyone can invent a security system that he himself cannot break.


I'm not sure if it is already possible? Is it.


Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: