HNHacker News
TopNewBestAskShowJobs

spoondan

1,301 karma · joined November 17, 2008

submissionscomments
spoondan··on Phone Numbers Were Never Meant as ID. Now We’re All at Risk
That’s also just information you know about many of your acquaintances, and that people often publish online. Join a dating site, and you have the password to the PDFs.

Of course, you still need to obtain the PDFs. And there is that wall in the way...

spoondan··on Tattoo Ink Nanoparticles Persist in Lymph Nodes (2017)
And we will seem happier, fitter, more attractive, better traveled, more socially connected, and more politically engaged than we ever were.
spoondan··on Why Has Science Only Cured One Person of HIV?
I believe the point was that HIV alone does not motivate a bone marrow transplant. There are people with more urgent need for transplants and not enough donations to serve that need.

It goes without saying that it's unethical to motivate a bone marrow transplant for a person with HIV by giving them leukemia. I assume then that it was said either as a joke or just for the sake of completeness.

spoondan··on Firefox is on a slippery slope
Respectfully, I don’t think this answers my question.

My question is not about what Looking Glass itself does. I can see that in its source. My question is whether Firefox or SHIELD collected additional data because the addon was enabled, even when the pref (and therefore) extension wasn’t. That’d require going through the source for the browser, SHIELD, and Normandy, which is quite a bit more challenging.

I’m hoping for a more authoritative answer with some evidence and preferably from a Mozilla representative.

spoondan··on Firefox is on a slippery slope
Thank you for the missing context.

Would you (or someone else in the know) please clarify what additional user data (if any) the default-enabled bootstrap add-on caused to be collected when the extensions.pug.lookingglass preference was disabled? I did some searching, but it's unclear to me whether SHIELD studies automatically cause any additional data to be collected and to whom that might go. I think the support site[1] could do a lot better addressing that topic. For example, it mentions (but does not link to) the default data collection policy.

Does the fact that this study didn't pop an opt-in UI definitively mean that whatever additional user data might be collected was all within Mozilla's privacy policy? The support site says that opt-in step, "will happen when a particular study needs to collect data that is not covered by default data collection policy." Does this apply when the study is just a bootstrap, and the actual extension is pref-enabled?

Lastly, I appreciate that you've being candid in sharing your personal feelings about the inappropriateness of pushing this extension. I'd like Mozilla to go one step further and comment on whether an extension of this nature is even appropriate to consider for a SHIELD study. Based on my reading of the feature's design and history (starting at the wiki[2] and branching out from there), as well as the aforementioned user-facing documentation, I believe SHIELD is intended for user research into features/ideas intended to be shipped to all Firefox users. I didn't find definitive guidelines on what constitutes an appropriate study for this program (if aren't publicly available, that's something Mozilla might want to address in the wake of this controversy), but I would disqualify Looking Glass in at least four different ways:

* Fleeting - whatever appeal it has to its target audience has a short shelf-life * Frivolous - it has no utility and doesn't substantially improve any aspect of the user experience * Hyper-targeted - it's only for Mr Robot fans * Advertising-related - this adds an extra level of privacy concern for users

User research is a delicate matter requiring a lot of care to balance collection with privacy. To enroll (or stay enrolled) in these programs, users must be confident that they aren't trading too much privacy and are getting tangible benefits in return. Looking Glass fails the privacy confidence test for being advertising. It fails the tangible benefit test for being fleeting, frivolous, and hyper-targeted.

SHIELD isn't some convenient way to push features. It's a user research tool. Studies ought to have the gravity that the term implies. Mozilla hasn't just failed to respect user's concern over their privacy, it has also undercut its own user research efforts.

[1] https://support.mozilla.org/en-US/kb/shield [2] https://wiki.mozilla.org/Firefox/Shield [3] https://support.mozilla.org/en-US/kb/lookingglass

spoondan··on macOS High Sierra: Anyone can login as “root” with empty password
You can also get the password last set time with:

    sudo dscl . -readpl "/Users/dan.koepke" accountPolicyData passwordLastSetTime
spoondan··on The Uber Conflation
One very serious shortcoming of this article is the claim that the theoretical spirit of taxi regulation is exclusively (or even primarily) rider safety. Regardless of how we believe it has all worked out in practice, taxi regulation has long been earnestly pushed for a multitude of reasons: traffic congestion, driver pay and rights, consumer protection (from fare abuse), road safety (independent from rider safety), and, yes, the kind of rider safety that Uber is far better at through GPS tracking and driver reputation.

There are many attitudes to have about taxi regulation. Some would argue that the market will eventually provide better solutions; even for issues like traffic congestion. Others might contend that the regulation is necessary because the market will either not find solutions or the cost of finding those solutions via the market is prohibitive. Some might take a less principled approach and consider whether the current regulations are better at solving problems or creating them. Regardless, we have to honestly consider the whole story. It's easiest to argue for Uber's approaches when you consider only the small part of the argument where Uber and its ilk clearly best the entrenched taxi system.

spoondan··on C++11 FAQ
This is perhaps one of the more unexpected opinions on C++ I've encountered. When I picked up C++ with Turbo C++ 3.0 in the early '90s, it was already widely regarded as an over-complex behemoth. Donald Knuth said of it in 1993, "Whenever the C++ language designers had two competing ideas as to how they should solve some problem, they said 'OK, we'll do them both'. So the language is too baroque for my taste." The last twenty years, there's no C++ that I would call lean, expressive, and elegant. You give the example of template meta-programming as something added more recently, but Erwin Unruh was printing the primes in compiler error messages not long after Knuth was knocking C++ as baroque. It makes me wonder if perhaps the issue isn't simply that over time you've become more aware of how complex the language has always been?

The language has continued to grow, but it's growing in a rather different direction (or rather in a clear direction): towards a modern, preferred subset that _is_ lean, expressive, and elegant. While C++ is still far from my favorite language, I find C++ today to be far simpler, more expressive, and more elegant than at any other point in the past.

spoondan··on Hellwig Will Appeal VMware Ruling After Evidentiary Set Back in Lower Court
This page https://sfconservancy.org/copyleft-compliance/vmware-code-si... attempts to back up Hellwig's claims using analysis from CCFinderX. However, it seems to make an error in establishing baselines when it states that, "Next, we compared the source code of the Linux Kernel 4.5.2 to the LLVM+Clang system, version 3.8.0. These two projects are each a large program written in the C programming language, but they are not known to actively share code."

LLVM+Clang are written in modern C++, not C. It's unclear to me if a mechanical translation from modern C++ to C will rank as similar, despite it clearly being copying. I suspect it would, but I think the cross-language comparison is a weakness in this demonstration. Combined with the reported failure to meet evidentiary standards, it suggests some real room for improvement in pursuing these cases.

spoondan··on The Apple Goes Mushy Part I: OS X's Interface Decline
Floppy disks have entirely disappeared from our daily lives except as an icon (and then largely only on Windows). A computer-savvy 18 year old that grew up on Macs could have entirely grown up without ever using a floppy disk and rarely if ever seeing the icon. I know adolescents that have never seen a floppy disk. Being unfamiliar with an obsolete media format doesn't make them stupid.

As for the rest of your comment, I'm not sure what you think I was trying to make sound difficult. I was arguing that it's entirely possible to replace the floppy disk with an arbitrary symbol, and it's just inertia (user training and a strange sacredness afforded this one random icon) that really keeps it around. I think assosciating a distinct symbol with an action is pretty damned easy, actually. (Designing a good symbol can be hard, though.)

spoondan··on The Apple Goes Mushy Part I: OS X's Interface Decline
To be honest, I don't know what point you're trying to make. It is as if you think I was claiming arbitrary symbols cannot work well as icons. But I actually said the opposite of that: the floppy disk is basically an arbitrary symbol at this point. It works because we train people what it means.
spoondan··on Java REST framework Dropwizard 1.0 released
There's quite a bit of magic under the hood of DropWizard (or, rather, the components that make it up). My experience has been that a developer using DropWizard will rarely, if ever, encounter this magic: they don't need to be aware of it. But if the veil ever slips, the sheer amount of ugly machinery will shock and horrify.
spoondan··on The Apple Goes Mushy Part I: OS X's Interface Decline
The icon is recognizable because younger people learn the weird boxy icon means save. Even with an explanation of the icon's origins, for the younger generation, the icon is recognizable but not meaningful. Can we devise a more meaningful icon? Can we break with convention and just choose a different icon that's recognizable but more aesthetically pleasing or consistent with our style guides, even if it's still meaningless?

This isn't an argument against vestigial iconography. It's not even an argument against skeuomorphism. It's a recognition that skeuomorphism increasingly fails to serve its intended purpose of conveying a meaning. Once we recognize that the old icons are dead metaphors, that we often times keep them only because of inertia and not because they have any intrinsic value, we can build momentum on the necessary work of establishing the visual language of the digital age on its own terms.

spoondan··on Simon Pegg Admits He Used Wikipedia to Fact-Check Script for 'Star Trek: Beyond'
Wikipedia may well be going the route of Kleenex, Xerox, Coke, and Google. When a product is so strongly identified with a brand, people just don't care to distinguish between the two.
spoondan··on Emudore: a C64 emulator written from scratch using C++11 and SDL2
This is a cool project with nice, simple code. However, the submission's title (perhaps counter to the README) makes it seem like a good example of C++11, and I would caution against using it that way. From a cursory examination, and with all due respect to the author, this code is more classical C++ with a few uses of C++11 features than it is representative of how modern C++ (at the time of C++11's publication) should be written. There are a few areas where the code could be updated: adding tests, avoiding manual memory management, making it so objects cannot be created in invalid states that would cause crashes, const correctness, etc.

By way of explanation, I'll focus on just the issue of manual memory management. Simplifying a bit, consider this part of the C64 class's implementation:

    C64::C64()
    {
      cpu_  = new Cpu();
      mem_  = new Memory();
      cia1_ = new Cia1();
      ...

      cpu_->memory(mem_);
      cpu_->reset();
      ...

      cia1_->cpu(cpu_);
      ...

      mem_->cia1(cia1_);
      ...
    }

    C64::~C64()
    {
      delete cpu_;
      delete mem_;
      delete cia1_;
      ...
    }
The contract in this code is that a C64 owns the chips, the chips are born when the C64 is instantiated, and when the C64 dies, the chips all die along with it. There are two approaches for making this contract explicit, one is to simply not use pointers and references at all:

    Cpu cpu_;
    Memory memory_;
    Cia1 cia1_;
But this does mean we can't use polymorphism within the C64 class, we don't have nullability, and we can't replace the instances. The code doesn't leverage any of these, so that may be an appropriate choice. However, if we need any of those things, we can instead use the appropriate smart pointer:

    std::unique_ptr<Cpu> cpu_;
    std::unique_ptr<Memory> memory_;
    std::unique_ptr<Cia1> cia1_;
In either case, C64's destructor is no longer necessary. The other classes still take raw pointers (e.g., `Cpu*`) because they do not own the objects they receive and do not dictate lifetimes.

It's worth mentioning that many people would use `std::shared_ptr` here instead, but I think that's abuse that leads you towards circular references (memory leaks): the Cpu doesn't own its Memory, they just have their lifetimes managed exterior to them. This would actually come up with the existing design (if shared ownership were used), since the object dependency graph (which is perhaps another issue) has several circular dependencies.

spoondan··on NPM and Left-Pad: Have We Forgotten How to Program?
I think that there's a certain wishfulness bordering on naïveté to this pursuit. We tell ourselves that we are managing complexity by having small, well-tested units that are reused by an entire community. But software complexity continues to exist. We think we are mitigating the complexity of our own software. But the complexity really just shifts to the integration of components.

Anyone that has been around long enough has war stories about getting two relatively simple pieces of software working with each other. In my experience, integration problems are often the most difficult to deal with.

spoondan··on Add Reactions to Pull Requests, Issues, and Comments
Facebook and Twitter provide strong evidence that people will use reactions. I see no reason to expect that user behavior will differ when they want to express negativity. Facebook's decision to not provide this feature has long been rooted on the pretense that people will use it. That is the basis of this thread: that people will use it instead of commenting.

Also, it's really easy to disagree with what I wrote without suggesting I am naive.

spoondan··on Add Reactions to Pull Requests, Issues, and Comments
The context of this feature is that users were using comments to react without providing substance. The primary motivation is to reduce the visual clutter of non-substantive comments.

While we can agree about what users should do, users not behaving as we think they should is the whole point here. Removing the -1 reaction won't encourage people to articulate their concerns. Nor will it discourage people from writing comments that explain why something is not a good idea. It simply provides a mechanism for people to register disagreement that is less obtrusive than the mechanism they would otherwise use. A cavalcade of -1's as comments obscures and thereby prevents substantive discussion.

spoondan··on Answers to your questions about Apple and security
Apple do not have the ability to unlock the phone. They have the ability to create a tool that could unlock any iPhone. That is not a starting point.
spoondan··on San Bernardino County tweets it reset attacker iCloud password at FBI's request
There are separate passcodes for the phone and for iCloud. An iOS device will automatically sync a backup to iCloud once a day if iCloud backups are enabled provided the phone is connected to power and a wifi network. When you first enable iCloud, the phone requests your iCloud password and stores it. If you change your iCloud password, automatic syncing is disabled until you unlock the phone and enter your new iCloud password there.

The FBI cannot unlock the phone. By changing the iCloud password, they have made it so that the phone cannot even possibly sync without first being unlocked. Knowing the iCloud password is of no utility for them.

spoondan··on Mypy 0.3 Released – optional static type checker for Python
Authors of libraries, frameworks, and tools that must support Python 2.
spoondan··on David Bowie Has Died
Your sadness is completely justified. As John Donne observed nearly 400 years ago, "any man's death diminishes me, because I am involved in mankind."
spoondan··on Amazon has no idea how to run an app store
The first sentence of the article is, "Amazon is relatively new to the job of running an app store, and some of their mistakes are either hilarious or infuriating, depending on how much money you’ve lost trying to deal with them."

The decision to switch the submission title away from the article's actual title is unjustified. The decision to switch it to a selective edit of the article's first sentence is even worse.

spoondan··on YouTube change served lower-quality video to Firefox 43 for 2 weeks
YouTube's compatibility hacks are against buggy versions of browsers. Regardless of whether a bug is eventually fixed, once it is released, there is some segment of the user base that has it. If that segment is large enough, and the bug easy enough to hack around, then YouTube will provide a workaround rather than lose revenue.
spoondan··on Dell Computers Has Been Hacked
The purpose of the scam is not to gain access to computers. The purpose of the scam is to fleece unsuspecting Dell customers. The scammers gain the trust of their victim by using misappropriated Dell customer data. They charge exorbitant fees for unnecessary services to the less technically competent.

My assumption is that the scammers are based in India or somewhere else where dollars go quite a bit farther than the US. Even apart from the potential for fraudulent charges, spending a few days to earn a few hundred dollars is definitely worth it in a country where the average income for a year is around $1300.

spoondan··on SnoPy – Snobol Pattern Matching Extension for Python
Plenty of PyPI packages have external dependencies (e.g., anything that uses Cython will require a C compiler). SWIG isn't needed, since it is a source generator, and it's trivial to ship the generated source as part of the release process. GNAT is not commonly installed, but since it's part of GCC, it's packaged for every major OS and distribution. So there's one external dependency that is trivially installed, and many packages have similar requirements.
spoondan··on More Dirty Coding Tricks from Game Developers (2010)
Nicholas Vining was referring to the first ever appearance of the character, not its first mention. The Lithtech comic is the first appearance, and the one you've linked is its first mention.
spoondan··on Why Docker Is Not Yet Succeeding Widely in Production
> The same can be said for ruby, python and any number of other language environments where you have multiple services that were written at different times with differing base targets. I've seen plenty of instances where updating a host server to a new runtime breaks some service that also runs on a given server.

This is a solved problem in Python and Ruby. In Python, use virtual environments. In Ruby, use RVM. You won't have the issue of one tenant breaking another.

spoondan··on Weave is kinda slow
Nonsense. Users of free and open source software have every right to point out flaws in the design and implementation of that software. And this is an invaluable service to the authors and community. While finding and fixing an issue is nice, it's certainly not required, and not everyone capable of identifying issues has the time, ability, and inclination to fix those issues.

Furthermore, the conversation at issue was initiated by a community member asking why Weave's authors chose to implement their own security mechanism. The point of this kind of question is to assess whether the authors had good reasons, bad reasons, or no reason at all behind a questionable decision. This helps determine whether the effort to resolve the issue would be well-spent. If the authors aren't convinced that other solutions would be superior, they may be unwilling to accept a contribution, and you are potentially wasting your time producing a patch.

spoondan··on Google Is Developing Its Own Uber Competitor
I don't think Google Ventures's role is particularly relevant. Companies should be aware of what data they are providing Google when making use of Google services. Google doesn't need to have insider information to have a wealth of information about Uber trips: the number of trips, when they most frequently occur, duration and miles covered, what cities are most popular, what are the popular starting and ending points. All of these data can be mined from just watching Uber's use of the Google Maps API. It may not be contractually permitted, but the data are there for Google to use.

Through a paranoid lens, Google APIs are corporate espionage you sign up for. Since Google is a valuable and entrenched service provider, they can get away with it. What I could see companies doing in return is attempting to obscure their API usage by fabricating requests. For example, Uber could break the correspondence between API requests and trips by sending requests that look authentic but don't correspond to any actual trips. This kind of corporate information warfare sounds like something out of a William Gibson novel, but it certainly feels present and real when you look at Google's relationships.

← PreviousPage 2 of 7Next →