You're right - but, as Cory Doctorow points out, Apple owe their success to reverse engineering, the very thing they're busy blocking now.
Deebster
joined 1 year ago
It's not the same expression. I mean "a bug" as in a software error and "on my side" as in it's not Lemmy's fault.
Now I see that OP is the creator of the tumblr clone Wafrn I'm sure it's just a typo and that this is the intended meaning.
Or "a bug on my side", depending on what they mean. Prepositions are hard.
It's been downvoted because it was posted multiple times (misunderstanding/technical error) but I agree. Each of the posts have different replies so it's a shame we can't merge them into one excellent thread.
Large parts of the rewrite came from contributors who had never worked on fish before.
That's pretty useful alone.
And there's this:
Thread Safety
Allowing background functions and concurrent functions has been a goal for many years. I have been nursing a long-lived branch which allows full threaded execution. But though the changes are small, I have been reluctant to propose them, because they will make reasoning about the shell internals too complex: it is difficult in C++ to check and enforce what crosses thread boundaries.
This is Rust's bread and butter: we will encode thread requirements into our types, making it explicit and compiler-checked, via Send and Sync. Rust will allow turning on concurrent mode in a safe way, with a manageable increase in complexity, finally enabling this feature.
Oh yeah, that looks much better than any of the included themes. Nice work!
Could you share a screenshot of your final result?
Hmm, getting origin servers to expose themselves this way is a clever hack. As noted, any bad actors probably already know this trick to bypass Cloudflare/whatever anti-DDOS layer.
As a fix, I guess you can either send your server's outgoing connections through a proxy/VPN or use your hosting company's firewall to block all non-Cloudflare inbound traffic.
I think "partnering" is a bit strong - Kagi uses Brave as one of their various sources for search. I agree that Kagi's response was poor, though.
Not even htop? That is old school.
Good to hear something about Solid again. I was aware of it already (having Sir Tim Berners-Lee behind it makes it occasionally news-worthy) but it's really not made any ripples that I've noticed recently. It seems to be ticking slowly along, but I think until we can get a good look at ActivityPods 2.0 it's hard to get too excited.
You're being unnecessarily pedantic. Apple was blocking interoperability and reverse engineering found a solution—and Apple is blocking that solution.