I don't know who is dumber now... the AI, or the humans who keep interacting with them thinking that they actually possess some form of intelligence and are not just stochastically regurgitating a token stream.
Yes, probably but they are “easily” replaced. More easily than Signal in any case.
Also if we go down this road, we’re all depending on our internet access provider at the very least too! At some point we gotta know when to stop trying to be fully independent from the rest of the world. He chose there.
There are obviously other CDNs (or whatever Cloudflare considers itself to be these days) and other certificate authorities. They are all interchangeable thanks to open protocols (HTTP, TLS/ACME in this case). Contrasted to Signal: there are no other implementations.
Re: Signal, it's even worse: they are openly opposed to federation and to letting alternative clients use their server. They demand control and obedience, which has always been suspicious-enough to defeat any goodwill effort on their side. Why would I have/want to trust them when XMPP is a viable federated alternative?
Signal focuses on security and privacy above all else, which they don't think a federated model can do well. Case in point, XMPP in practice is less secure than Signal but has the advantages you mentioned.
The other common anti-federation argument is spam/reputation, which is basically the reason email is becoming more centralized unfortunately, though it still survives.
?? I don't understand the conclusion to block incoming SYNs with TTL > 70... you're blocking all (even valid) connection attempts from users running other OS's that don't choose the default TTL of 64... like Windows, which I think uses 128.
When in the past you learned that the recommended value for the TTL was 64 and you didn't think any operating system would pick a value much larger than that.
> "We totally lost all of our critical thinking skills "
This nugget was buried in the article, and seems appropriate. I don't get where the author is coming from. If one doesn't take some level of responsibility and modicum of effort to preserve and safeguard something valuable to them, then yeah, it might get lost.
> To be honest, though, this seems like ideal content for an LLM to produce. It's basically fact regurgitation.
You're trolling us, right? "Basically fact regurgitation" is all that teachers do after all. Have you ever noticed the difference between an inspirational teacher and a not-so-inspiring one in terms of effectiveness of communication and the "ah ha!" or lack of moments in your own understanding? If you can honestly say "no", then I might be able to understand your statement above, but really?
> I want less code. I want to limit the amount of 3rd party code I pull in. This is mostly due to supply chain disasters over on NPM scaring me and the amount of code dependencies bringing in see rust dependencies scare me.
`anyhow` has exactly one optional dependency (backtrace).
`thiserror` has three (proc-macro2, quote, syn) which are at the base of practically the entire Rust ecosystem.
Unless the author has zero dependencies in general, I'll bet they have all of the above dependencies already.
Anyhow itself is still a dependency. This is more something I wanted to do and not something I recommend for everyone. Google took a similar approach in how they added rust for chrome. They don’t use an error handling library.
> I know it’s thermal throttling because I can see in iStat Menus that my CPU usage is 100% while the power usage in watts goes down.
When I read this I wondered "Why isn't core temperature alone not a reliable indicator of thermal throttling?". Isn't that the state variable the thermal controller is directly aiming to regulate by not letting it exceed some threshold?
My M4 Max Macbook Pro can run for a while at like 105°C and fans to the max before throttling, when it starts throttling it doesn't exceed that threshold, and then the temperature goes down for a while before throttling stops
Makes me wonder why there isn't a UI feature within easy reach to let the user drag a pin on a map and tap "I know I'm here right now"... and if that agrees with where GPS also indicates, let's it reset its notion of "I must be getting spoofed right now" thoughts in addition to calibrating other notions of current location.
reply