527 karma · joined August 7, 2018
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.
Julia has been <designed> to unsettle Python in the data space but to no avail.
¯\_(ツ)_/¯
My educated guess is that <at best> UN is using homomorphic encryption for basic analysis...
or they have achieved a breakthrough and have FHE /s.
Likewise, how’s it different from backlink-based apps like Obsidian, Roam and Craft?
Is OSS the only selling feature?
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).
Scraping may not be a crime but unintended privilege escalation is a whole different story.
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.
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).
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 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.
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.
Unless they are deliberately avoiding comparison to Mathpix, they are quite unaware of the competition out there :|
The only time I use paper is when I don't have the iPad on me and for personal journaling (for which I have a dedicated notebook anyway).
While I wouldn't use that material directly ever again, I noticed that I would often paraphrase a paraphrase, so to speak, because I would remember some of the material.
Tangentially, this thread shows that people prefer different ways of taking (or not taking notes) usually due to a habit itselfc as opposed to superiority of one method over the other. It reminds me of Dvorak vs qwerty, while technically superior for typing in English, the cost of switching is not worth it for most people out there.
It seems that the only way to deal with this, would be to have a hardware switch that disables the camera, e.g. like iPhone's mute toggle.
I say this in jest but at the same time I'm concerned this might be true.
Let's run through the options (accumulated over months or years of discussions): 1) Split FB into the FB-Instagram-WhatsApp trio that we used to have in the past. Neat but the main culprit remains the same. 2) Remove Zuck or at least reduce his voting power s.t. the board has more. This would work if we assume that Zuck is the main issue with FB, which I doubt he is. Investors would always push for more money and if it means more of the same privacy-violating, advertising-driven social media, I doubt they would change it - money hardly ever has a moral compass of any kind. 3) Kind of like 2 but on top of this, you fix some members of the board with community/government selected representatives which would be supposed to balance out things and/or at least raise concerns. 4) Introduce point 3 as a general rule - if a company reaches X% of the given industry's estimated total market value, it has to give up some board seats. In theory, forces companies to stay focused instead of spreading into every single adjacent industry.
Now, all of these have problems of their own (corruption in case of 3-4, anyone?) but the sooner the discussion starts the better. Google/Amazon/Microsoft/Apple/chip makers are next in line but also, as another commenter pointed out - we do want to see people build strong and prosperous companies that truly innovate.
Damn, it's a non-trivial topic, just writing this down brings more questions than answers
Swapping Introduction to Statistical Learning for Elements of Statistical Learning is a good step-up if you don't need as much hand-holding (it's essentially the same book, by the same author just more thorough). Then, adding Bishop's ML book is a good idea. Although also introductory, it covers a lot more topics (some kernel methods and probabilistic stuff) and in a more disciplined way.
Also, while not that popular in the deep learning hype era, Vapnik's Nature of Statistical Learning is a great read.
However, take it as an educated guess rather than a fact since I have never been a mobile dev apart from hobby apps.
EDIT: typos.
Nowadays, it's difficult enough to convince people to drop e.g. MATLAB for R or Python for Julia (let's assume that there's some merit to it), despite them having excellent counterparts for almost everything. Swift's success in this domain depends solely on the adoption by developers/researchers/engineers. Unless they're just going to mostly use it internally (as Google is known to).
Which brings me to the last point - why on Earth would they pick Swift (apart from Christ Lattner being involved) when Julia was on the table? It ticks all their boxes and has more mature ecosystem for all things "data". Provided rationale is hardly convincing.