Do you believe that a blackhat presentation taints the code quality of WireGuard? Do you believe that Donnefeld's desire to maintain tight control over kernel implementations suggests he has ulterior motives?
807 karma · joined January 10, 2015
Do you believe that a blackhat presentation taints the code quality of WireGuard? Do you believe that Donnefeld's desire to maintain tight control over kernel implementations suggests he has ulterior motives?
I've watched it before and it is compelling; however, at the end of the day, an OS that tries to take security seriously is probably better than one that doesn't. The OpenBSD code is small and I suspect that the defects/KLOC is far less than other projects capable of routing. I'd love to hear more critiques for using it as a home router though.
If I had to pick between USB-C charging and MagSafe, I'd pick MagSafe for accident prevention. The option to use USB-C or MagSafe charging would be a win for everyone.
[1] https://www.ea.com/service-updates
Games impacted by the above policy:
https://www.ea.com/service-updates/a-h
I'm hoping KoReader can salvage what the reMarkable team has ignored.
https://webonanza.com/2015/10/02/did-satoshi-predict-pooled-...
If you want to skip the video, the design document gives a nice overview of the protocol: https://github.com/jsherer/ft8call
This is the only other method I've found: https://github.com/nick8325/remarkable-fs
You'd think scp would work also but I haven't found info on the subject and I don't own the RM1 to try.
edit: found someone's scp script: https://github.com/reHackable/scripts/blob/master/host/repus...
The changelog is public so you can see the rate of development if you're interested: https://support.remarkable.com/hc/en-us/articles/11500546010...
Full review: https://www.youtube.com/playlist?list=PLsSI9-gaSSmiXwb7Vjk5V...
I ultimately passed on the device for a few reasons:
1. The RM1 and 2 both don't allow file transfers as a mass storage device. If you want local, non cloud based transfer, you need to use a flaky local web UI that hasn't been improved in years
2. The internal storage still hasn't been updated from 8 (6 usable) GB. This is an obvious attempt to sell cloud storage in the future
3. While the hardware is amazing the software moves at a snail's pace. This is either management holding development back by trying to simplify the device out of existence or the team simply lacks the resources or ability to improve it
4. There has been almost no attempt to improve reader functionality in years. Things as simple as font resizing are 30x slower than on a Kindle
5. It seems obvious to me that management doesn't understand the target audience for the device
"Nicotine could maintain or restore the function of the cholinergic anti-inflammatory system and thus control the release and activity of pro-inflammatory cytokines. This could prevent or suppress the cytokine storm. This hypothesis needs to be examined in the laboratory and the clinical setting."
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7192087/#!po=22...