638 karma · joined July 16, 2012
In the linked post, they mention both Django for the backend and Redis as a cache. Django has caching built-in though, so until you need more complex caching logic, you probably don't need to reach for Redis.
I think the big difference is the adaptivity of the phone. Books don't figure out what personally engrosses you and tweak the rest of the book so you can't put it down. That feels too powerful IMO.
The most prominent example is ISPs inject ads or messages. Search for "comcast injecting ads" to see some examples.
It's easy to see codes of conduct as draconian or unnecessary if you can't empathize with the people they're designed to protect. I'm not saying the CoC system is perfect or that there aren't false positives, but your statement here is _dramatically_ privileged.
> PD has certain charging ‘profiles’.
> For example Apples 30W USB-C charger can work at:
> 15 watts (5 volts @ 3 amps), 27 watts (9 volts @ 3 amps), 30 watts (15 volts @ 2 amps), and 30 watts (20 volts @ 1.5 amps)
> The MagSafe puck supports none of those for some reason. So it drops down to ~5W which is a safe backup amount for most devices.
> The new 20W charger appears to have a new profile it supports for the full 20W, which so far seems to be unique to that charger + MagSafe combo. It’s... messy.
[1]: https://appleinsider.com/articles/20/10/27/magsafe-15w-fast-...
I've been trying to move friend groups more towards Slack and it's been a huge improvement over group texts / Facebook chat / etc.
(of course, for our gaming group, discord voice chat is still superb. But, we only use it once a week and all the rest of our chatter/discussion happens in our new Slack team)
From the perspective of their business, it's advantageous to have the consistency of $X / month forever instead of "hopefully a huge yearly sales month, followed by mostly nothing until next year". Businesses like predictable revenue.
It would be great if we could see more software sold as-is, without updates. But, especially in the world of online-capable tools (which not everything is, but most apps can access the internet), ongoing security maintenance is important. I'm not sure we can have it both ways.
It's an open standard, so you can read all about it: https://webauthn.guide/
Unless it doesn't auto-fill, but it looks right, so you paste it anyway.
If I'm fishing you and get you to type your password into fakegoogle.com, I'll try to use it with real google immediately. If they send me a 2FA error (and I've got a semi-sophisticated phishing operation) fakegoogle will show you a an input field for that 6 digit code (just like real google). Then I've got a few seconds to send that to $site as well. It's a tighter timing window, but it's likely at this point that I'm into your account.
This sort of attack isn't possible with a hardware key, since it only works on the original domain (which presumably I don't control).
Does that make sense?
Doesn't seem like change for change's sake at all.
I just wish the need for constant growth wasn't the reality of tech companies in 2020.