Of course, you still need to obtain the PDFs. And there is that wall in the way...
1,301 karma · joined November 17, 2008
Of course, you still need to obtain the PDFs. And there is that wall in the way...
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.
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.
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
sudo dscl . -readpl "/Users/dan.koepke" accountPolicyData passwordLastSetTimeThere 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.
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.
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.
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.)
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.
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.
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.
Also, it's really easy to disagree with what I wrote without suggesting I am naive.
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.
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.
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.
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.
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.
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.
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.