Nothing that you said is wrong but it doesn't make the situation better.
1) As many people pointed out, this doesn't prevent OCR, it just prevents copying strings (e.g. with crawlers).
2) Majority of OCR doesn't deal with PDFs produced from a text source but either from a) jpg-scans of documents b) pdfs produced from those jpg-scans.
3) The first thing I tried, was OCR with my iPhone and it obviously worked. As someone else said, there're solutions that let you batch process many documents.
Don't get me wrong, your stuff works for what you designed it to.
However, it provides <false sense of security> by <falsely> claiming that it prevents OCR; which in turn, can lead to more harm[1].
[1] - e.g., it may convince people to share stuff that they wouldn't otherwise.
I agree that using booleans like this can be confusing. But, imo, it's more confusing to have a bunch of wrapper functions that create abstraction madness.
I mostly write computation/math-related code and I find using named arguments to be a good practice. This is also quite similar to OP's enum approach, e.g. sth like `calc_formula(a, b, is_gain=True)`.
To be fair, the older I get, the more I like explicit arguments for everything like in Swift (and smalltalk iirc).
I fully subscribe to this point. It comes up, then it either gets voted out or doesn't even come that far.
What baffles me though is that such blatant power-grabs are being introduced, and that anyone thinks that anything would be better off afterwards. Surveillance is going to get more difficult, not easier unless you want to spy on middle-aged people talking about fishing or sour dough recipes.
While the assumption that you can make changes to swift’s stl is not that far-fetched, doing so to cpp’s is completely mental.
I’ve got a feeling that swift is becoming a very polluted mashup of features that come from parties with conflicting interests. AFAIK, internally at Apple, teams pull in different directions (e.g. to get SwiftUI), at the same time there’s this half-baked differentiable programming / swift4tf manifesto, then there’s the backend swift initiative with vapour.
This reminds of a hotch-potch that Scala’s framework and feature landscape is. The overhead of getting into it is quite substantial and for some, definitely not worth the investment if not just downright scary.
This is the key point here. Google (Chrome), Apple (Safari) and MIcrosoft (Edge) funnel money from other ventures to their browser dev teams.
For Apple and Microsoft it’s just a staple tool that each operating system needs but for Google it’s a platform that guides users towards their other services and ties them in, YouTube, Gmail, Drive, to name but a few.
In the current business model, there’s absolutely no competing with them long term. You’d have to either break them up or create some weird funding schemes driven by govs and users that don’t care (public good or some other utilitarian argument).
No, if you work in a software house; or I'd say, you have extremely low chance there and anyone who made it, was an outlier.
Yes, if you work in a company that does some RnD and you have actual domain knowledge and expertise as opposed to being a generic, even if experienced, but nevertheless generic developer. I have many colleagues well into their 50s and some even 60s that work at Intel, NVIDIA, Ericsson etc.. They are not a rare sight over there.
On one hand side, provided rationale is right and I agree. If Twitter wants to play the policing game, they'd better bring out big guns and introduce a mechanism to police and fact-check entire platform.
On the other hand, and maybe its due to my lack of knowledge on the 230, how's report-and-remove of posts different? Twitter already has mechanisms to remove flagged content so how's this incident different (apart from being blatantly political).
Lastly, does anyone know if Facebook and YouTube are also protected under 230? I imagine that GOP wants to make an example of Twitter but for the sake of consistency Facebook and Youtube should get the same treatment.
Could someone ELI5, why it is so difficult to make it right? And I do not mean exclusively to Linux, because Windows has been horrible for years now too.
If the issue is hardware, then we'd blame OEMs.
If it's software, then we'd blame, say, Microsoft.
If it was a combination of these two, then we could say that Apple is the only one that controls both... if it wasn't for the Surface series which still has atrocious touchpad experience.