Here:
"(a) Taken "->" to mean "it is inevitable that" rather than "it is likely that". Almost any discussion about social/economic issues involves likelihood rather than deterministic cause and effect."
Yes, because your initial argument relied on assuming one very specific meaning of '->' in formal math/logic while ignoring other possible meanings that were actually more plausible in context (and the original poster has long since confirmed that they were talking about likelihood, not absolutes). You hadn't even stated your assumption of formal logic notation at that point.
...and you're
still compounding your appeal-to-the-dictionary fallacy - I referred to the OP's use of '->' -
you choose to interpret that as "implies" and then look up "implies" in the dictionary... The
whole point of my argument is that you weren't justified in interpreting the original post as formal propositional logic.
...and you still haven't explained what you meant by:
The formal meaning of "->" was (and still is) "then", "hence", "therefore", or any other words in the same spirit.
What you are describing is the "fat arrow" (=>) which does indeed mean "implies" which was used in none of the statements. MacBH928 used the wrong arrow (->) in the statements if that is what they ment.
...which appears nonsensical since we've established that 'A => B', 'A -> B', 'A implies B', 'if A then B" are -
in the context of formal logic notation - synonymous. MacBH928's post was sloppily argued - that is not in dispute - but it certainly wouldn't have been 'fixed' by changing '->' to '=>'.
Mathematical Sciences, Northern Illinois University this would fall under Equivocation Fallacy (Use of expressions of double meaning in order to mislead) is it was intentional which it likely wasn't.
...but if it
wasn't intentional, and you base your rebuttal on one specific meaning without permitting the alternatives, you're committing an Appeal to the Dictionary fallacy, which is what I'm claiming here.
I would like to point out that JMacHack in post
#157 also pointed out the excluded middle aspect of the examples.
...but that post still hinges on the presumption that the OP intended a specific meaning of '->' and disregarding that sometimes an arrow is just an arrow (Pro tip: never go to a seminar on social sciences if you are inclined to think of boxes connected by arrows as representing nodes and edges on a graph with some formal significance - you'll go mad

)
Also - careful with that "excluded middle" stuff - "excluded middle fallacy" is
misuse of the "law of excluded middle" which is about true/false propositions. If an argument is
not a true/false proposition then the fallacy is attacking it "because excluded middle". Again, it all hinges on your assumption that the OP intended '->' in the propositional logic sense, and they have already clarified that they didn't - the elephant is
not pink.
at least Apple told people what it was going to do
Absolutely - and the positive side of that is that a lot of independent experts are now scrutinising what they've claimed... Unlike a random person's posts on web forums, Apple's releases
should be assumed to have been carefully written and thoroughly reviewed before released, and should be held to a very high standard of technical accuracy and
The most detailed papers are too technical for anybody but crypto/image recognition experts, so I'm not even going to try, but you might want to attack this one with a dictionary:
https://www.apple.com/child-safety/pdf/CSAM_Detection_Technical_Summary.pdf - e.g. the way they start with "unique number specific to that image" on page 4, and work through "nearly identical" (a bit like "only slightly pregnant") until by page 5 it's "identical and visually similar images result in the same hash". ("similar" has a strict true/false geometrical meaning - e.g. 'similar triangles' - but 'visually similar' introduces an unknown degree of uncertainty to that).
Certainly if you look at these threads you'll see lots of people who have read Apple's press releases have come away with the message "it's not scanning my photos because it just compares hashes" which is a great example of an equivocation fallacy (conflating "NeuralHash perceptual hashes" - an image recognition technique - with cryptographic hashes, a security technique - both "hashes" in the broadest sense but hugely different in the details and implications{colloquial meaning} ).