936 karma · joined September 7, 2017
Please do not be disrespectful toward others.
Separate the commenter from the comment.
Smart commenters still make dumb comments now and then. And vice versa.
Consequently, the "identity" of the commenter is not a reliable predictor of the quality of the comment.
Shared accounts such as this one can address this problem.
Each comment must stand on its own, apart from identity and historical karma.
sed '/^#\{3\}/!d' x=$(command -v $0 2>/dev/null)
sed -rn 's/^### ?//;T;p' $x
Personally I would not use the author's chosen sed commands. exec sed -n '/^###/p' $x
would work fine.Semantics. Familiarirty with a piece of equipment versus familiarity proper technique when using it.
"I still don't know how he did it."
Practice. Learning through mistakes. Tips from others.
What are the reasons users do not read the /legal/data page on the Julia website? What are the reasons users do not read 200+ posts from developers debating the use of opt-out telemetry? To ignore such reasons, assuming they exist, would also be disingenuous.
If you put the choice clearly before users and they knowingly, affirmatively choose to submit usage data, then no 200+ post thread is necessary. Instead, the choice is not left to users. It is made by developers, and the fact of the use of opt-out telemetry is found on a webpage that developers know users do not read.
This way, we are not restricted to the ciphers supported by the "Crypto-JS" NodeJS package. Not meaning to take anything away from the venerable Crypto-JS library of "standards" including RC4 and TripleDES.
I am a human and I don't love mobs. This article is all about incorrect assumptions. If I am not mistaken, the parent comment just made another one.
The part about the media amplifying what is on social media I absolutely agree with. I have always thought there is some strange irony in news outlets writing about something that is, at least in the case of newspapers, killing their own business.
https://www.cbsnews.com/news/columbus-statue-in-baltimore-to...
Moreover, at present, we have no idea how many people use each solver (and on which platform!). Knowing how many people installed which solver
would allow us to prioritize support from our finite developer time.
Why not just let users vote on that? The support is for the users, no? Instead the developers want to minimise the amount of time they spend on maintenance based on the number of users who could potentially complain. The reason for this is (as we are about to be told) so they can spend more time working on platforms where they believe commercial solver developers could provide for-profit support services "(or $$)". This would also allow us to lobby the commercial solver developers to provide official support (or $$). To quote one company "We'll want to
provide official support at some point, but it looks like the scales haven't tilted quite yet." It'd be nice to know whether 100, 1000, 10000, or
100000 people per month use their software; that might change their mind.
The truth comes out. Collecting data via "frictionless" telemetry allows someone else, e.g., commercial solver developers, to make money. Nothing wrong with that if we let users know about these intentions, however when devlopers try to operate under the guise of "free", "non-profit", "open source", etc. while, truthfully, they have commercial motives, then it seems to me they are doing everything they can to avoid tipping users off that this aims to be a commercially-oriented project. Instead of just being transparent about their motives and letting users decide, they want to sneak something by (most) users. The issue raised here is not the collecting statistics (nothing wrong with that), it is the less transparent, opt-out nature of it: telemetry. Deceptiveness, stealth. The message coming from this discussion is "Don't tip (majority of) users off that we are collecting data." And why is that? Because the developers know this is something most users do not want. Finally, if it is opt-in, the vast majority of users will not opt-in. This leaves us no better off than we were before. Opt-out is a good
compromise.
The discussion should have ended right here. If providing usage statistics is something that the Julia developers already know the vast majority of users do not want to do, then sneaking it by them via opt-out telemetry is wrong, and it tells us much about the people behind Julia. If users do not want it, and you know that, then why the heck are you doing it anyway? Anyone reading this will know why, but most users will probably never read what we are reading here.The rest of this discussion devolves into "Everyone else is doing it". The lone dissenter finally gives in to peer pressure.
I remember when using download statistics was enough. Developers still maintained software. No "trade-offs" were needed.
Big Browser is the cause of so many problems that people on HN complain about. Without the control over Big Browser that certain offending corporations have, their empires are considerably weaker.
Mom-and-Pop Browser is probably not an accurate caricature. Maybe something like End User Browser is more apropos.
If most HTTP is being sent over TLS these days, and Gemini is also over TLS, one could argue there is no "incompatibility". Gemini just doesn't need to all the extra ad-hoc functionality that has been built on top of HTTP. It is intended for data retrieval, not something that relies on help from the 20+ million lines of code in Big Browser to achieve.
def divisors(n):
for d in range(1, n):
if n % d == 0:
yield d
n = 1
while True:
if n == sum(divisors(n)):
break
n += 2
print(n)
I don’t know if this program halts. But I’m pretty sure it won’t steal my data and send it to third parties. Why? Because at no point does it read my data or communicate with third parties in any way: it would have to have those things programmed into it for that to be a possibility. At no point I had to solve the halting problem to know this.Also, if I execute a program and it does exhibit that behaviour, that’s a proof right there.
The same kind of analysis can be applied to Google’s scripts: look what data it collects and where it pushes data to the outside world. If there are any undecidable problems along the way, then Google has no plausible deniability that some nefarious behaviour is possible. Now, whether that is a practical thing to do is another matter; but the halting problem is just a distraction.
https://m.youtube.com/watch?v=gqGEMQveoqg
(Google Tech Talk from Van Jacobsen on CCN many years ago)
Facebook is doing the wiretapping, not the site owner.
Perhaps you are suggesting that the plaintiffs could allege a conspiracy to commit wiretapping?
These cases never succeed because the damages are too speculative. What injury/harm have the plaintiffs suffered as a result of the wiretapping? How can that be quantified?
Never trust tech companies about anything. Wise words.
What would happen if advertisers pulled out and Facebook fell on hard times? Would someone else acquire every detail of your life that you shared with Facebook? What happens if Facebook fails? Do they send your data back to you with a note saying "Thanks for the loan"?
I would not call haproxy "referer masking software". In any event, a proxy is not even needed.
Modern browsers are open source, right? Users can edit the source and remove the code that sends Referer header.
Even easier, I wrote my own http client. I can send any header I want, or none at all. According to DDG's privacy policy this is a good thing.
curl -Huser-agent= https://duckduckgo.com/lite/?q=xyz|grep result-link
curl -Huser-agent= -dq=xyz https://duckduckgo.com/lite/|grep result-link