sinak

ahris's response to another comment applies here as well:

"While confidence isn't an issue restricted to just women, it is a more prominent issue for them on average."

This is generally an important thing to consider. Just because a particular issue applies to you or you've seen a similar pattern amongst male colleagues doesn't mean that it isn't a more acute issue for women.

> I'm not convinced that there is widespread sexism in the computer industry, because I've worked alongside and been managed by many fantastic women, and witnessed them advance as quickly as me.

Relying on just the evidence you have directly around you is the same as relying on anecdotes. It's possible you've been lucky and work at a particularly un-sexist companies, but that perhaps the industry as a whole has an issue with sexism.

While this case might have ended, but the battle isn't over yet. Via Matthew Keys on Twitter:

"There are 6 other cases where Apple is still fighting the DOJ re: unlocking phones"

https://twitter.com/matthewkeyslive/status/71458323211775590...

^ Link includes an image with 7 other cases where Apple has either objected to warrants, 2 that are still in process.

The most interesting one is the last, which involves an iPhone 6+ running iOS 9.1. It's not yet clear whether the zero day that allowed the government to access the San Bernardino phone also works on the iPhone 6, which has a secure enclave (unlike the San Bernardino phone). There are some other iPhone 6 and iPhone 5S devices in the list too running older versions of iOS.

I wish I had time myself, but it would be really helpful if someone tabulated the results from this thread.

Good call - thanks dang!

Looks really great - love the web view of WiFi density, and great to see more efforts in this space.

We've built something similar at OpenSignal. Our WifiMapper [1] app on iOS and Android has a database of over 2 million networks, and we're also crowdsourcing a database of passwords and connection speeds.

[1] https://www.wifimapper.com/

The FCC's OET website is down at the moment, I'm guessing probably because of HN traffic. You can find the document cached here though:

https://fccid.io/2ABCB-RPI32

EFF's post on the beta, including details on the roadmap: https://www.eff.org/deeplinks/2015/12/lets-encrypt-enters-pu...

The hardest part is coming up with a thoughtful rubric.

I agree that we need some sort of "internet voters guide" or rating system for existing legislators. If the two of you (or others) would like to work on it, shoot me an email (in profile). This is the sort of thing Taskforce.is would love to work on I think.

Would love to see some sources referenced here. The claim that he "planned to help the murderer cut the body up and dissolve it in acid" is, as far as I know, based purely on Sneed's testimony and has been denied by Glossip.

Glossip definitely made mistakes the day after the murder. But there's no physical evidence connecting him to the crime scene. To say that he admitted to being "involved in the crime" seems like a stretch. He's maintained his innoncence since the start.

A better story with details on the case is here: https://theintercept.com/2015/07/09/oklahoma-prepares-resume...

Hey tabbott, I'd love to chat about this more if you're interested, it's something we've been particularly looking for. My email is sina@eff.org.

White-label builds of Zulip apps would work, but at least in our case wouldn't be ideal. Having a central community-hosted service would be much better.

My one big question is: does Zulip support push notifications to the next version of the mobile app if you self-host the server?

I'm not exactly sure how that'd be possible, but I wonder if they've managed to figure it out somehow. It's the one big problem with self-hosted chat apps like Rocket.chat and others - APNS and GCM are both centralized, and it's hard to federate them to provide push services for self-hosted instances of open source projects.

I'm tactically resubmitting this, as the previous post [1] set off the flame-war detector (# comments > # upvotes). But I think this is an excellently written and thoughtful article, and deserves more visibility than it previously received. Please weigh commenting carefully with your contribution to setting up the flame-war detector.

[1] https://news.ycombinator.com/item?id=9959217

If you're commenting, please make sure to upvote.

This post has more comments than it does upvotes, which means it flags the "flame-war detector" and will receive less visibility than it would otherwise.

I'm tactically resubmitting this, as the previous post [1] set off the flame-war detector (# comments > # upvotes). But this is an excellently-written and thoughtful article, and deserves more visibility than it previously received. Please weigh commenting carefully with your contribution to setting off the flame-war detector.

[1] https://news.ycombinator.com/item?id=9959217

I'm getting a 403 forbidden trying to access the page, here's a google cached version: http://webcache.googleusercontent.com/search?q=cache:w7iPIv2...

I've often wondered about this, and PG's related essay. Should you really be trying to optimize for minimizing the number of regrets you have on your deathbed?

It seems like optimizing for a happy, fulfilling life is right for a lot of people. But that isn't necessarily the same as minimizing deathbed-regret. I have a feeling that the two might actually be quite different.

> So my point is: why bother with increasing their volume. It's a bit like shipping gasoline to a forest fire.

Isn't this exactly what you did at BSD? Enabled advocacy organizations to send millions of form-letter to Congress, making real constituent contact get lost in the flood?

I've already addressed how we plan on incentivizing members of Congress to write better responses, but again: we're looking at an open dataset of comments, and reports on timeliness and content of responses.

Clay, I have read those Congress Foundation reports. And we regularly visit congressional staffers in DC. I'll also try not to resort to all caps in responding :).

Obviously your product, ScreenDoor, addresses some of the concerns you're raising around better data collection. Glad to hear you're so enthusiastic about that approach.

The EFF isn't planning on selling software to members of Congress. However, we are considering offering users the ability to make their comments public, which'd create a large public dataset about messages sent to Congress. If we decide to go ahead with that, the open dataset would then be available for anyone to run analytics on and create reports for members of Congress.

Improving the ways people contact Congress is one piece of the puzzle. The other part is making sure that people get better responses, and we hope to work on that too.

You have no idea how complicated sending message to Members of Congress is.

There's no way to email legislators directly. The only way is to fill out their forms. Each form is unique, and many have CAPTCHAs.

To do that, we first had to develop an open source dataset that describes to a computer the steps necessary to submit messages via each contact form for 538 representatives. That was quite a lift, but was made possible by about 100 volunteers who chipped in. The dataset is called contact-congress, and is online here: https://github.com/unitedstates/contact-congress

Then we had to create a system to fill in the forms based on the dataset. The system we designed is called phantom-of-the-capitol and it does that by firing up 3 browser windows on an AWS instance each time a user submits a message. If the legislator has a CAPTCHA, we take a screenshot and return that to the user. The code for that system is here: https://github.com/EFForg/phantom-of-the-capitol

Hey there, I worked on this.

BSD, BlackBaud, and Salsa all deliver messages to congress, but only for advocacy organizations who are willing to pay. Beyond OpenCongress, I don't think there are any tools that make it easier for constituents to write their own non-cookie-cutter messages to Congress. Change.org, for example, doesn't deliver emails.

The reason why Congress receives millions of messages is because advocacy organizations send millions of form letters. Congressional staff already have plenty of tools for separating those form letters from real, constituent-written letters. I can dig up their names, but they're built by high-level contractors.

Finally, one of our plans for Democracy.io is to measure response rates from representatives, and to use that to release a public report on how well MoC respond to real constituent messages. Both in terms of timeliness, and the relevance of their response.

Abgoosht/Dizi is my favorite Iranian dish - but unfortunately the only place in SF that serves it is Flytrap, in SoMa. I tried it recently and it's not quite the traditional Dizi that one might hope for (Flytrap is kind of fusion-Persian food).

Alborz in Berkeley also serves Abgoosht, but I haven't tried it there. If anyone has I'd love to know it is. If you're just generally looking for Persian cuisine in SF, Lavash is great.

If you're ever down in Southern California, there are a few places that serve Dizi. I particularly like Hen House Grill in Irvine - the setting isn't quite right for a Dizi (it's almost fast-foody), but the food itself is excellent.

More details here on Cloudflare's status page here: http://www.cloudflarestatus.com/incidents/m8hf8q8vs81d

Github pages is a great way to go, you basically push to a branch called "gh-pages" and a file in the root called CNAME with the domain and you're done.

https://pages.github.com/

From https://news.ycombinator.com/newsguidelines.html:

Please don't submit comments complaining that a submission is inappropriate for the site. If you think a story is spam or off-topic, flag it by clicking on its "flag" link. (Not all users will see this; there is a karma threshold.) If you think a comment is egregious, click on its timestamp to go to its page, then click "flag" at the top.

If you flag something, please don't also comment that you did.

I do think more examples of when flagging isn't appropriate would actually be helpful. And finding the instructions above isn't very easy, I wish they appeared elsewhere in HN's UI.

You can watch a livestream of the filibuster here: http://floor.senate.gov/MediaPlayer.php?view_id=2&event_id=3...

dragonwriter nails it on the first point.

On your points about free speech: there are legal carve-outs from free speech in the US. You can read more about them here - https://en.wikipedia.org/wiki/United_States_free_speech_exce...

And regarding silencing, sure, things are much better than they were 20 years ago. But that doesn't mean we should push for them to be better.

Also: please note that you're misinterpreting my words. I never said that anyone is a "horrible, shitty person." You can be a little racist and be a wonderful person. Those two things aren't mutually exclusive. Racism, is not an on-off switch, it's a spectrum.

> Are you trying to somehow imply everyone is racist? Are you further implying that everyone is sexist?

Yes and yes. Much of our context for judging people comes from society, and society is both sexist and racist. Numerous studies have shown that even people who identify as being non-racist will shoot a black person more quickly, dismiss a resume if it contains a black-sounding name, etc:

More here: http://www.nytimes.com/2014/08/28/opinion/nicholas-kristof-i...

The same applies to sexism. You can Google your way to plenty of similar studies.

> I'm curious, who (in the US anyways) doesn't have that right. At this point I feel like I can get sued for calling a stop sign red. It's getting a little absurd.

It's true that people (mostly) have the right to free speech in the US. But there are two ways to prevent people from expressing their views: you can literally disallow them from saying something, or you can "silence" them by making them feel uncomfortable for having spoken at all. I'm talking about the latter.

As with many articles about sexism, it's easy to read this and have an immediate, emotional reaction. If you "cringed" like one of the other commenters (and as I did reading some of the points listed), its worth taking a moment to think more carefully about why that emotional response was triggered.

Few HN users self-identify as "sexist." Yet reading this post, many of us will have done things that the author identifies as subtly sexist micro-aggressions. If you think that that makes you a sexist, well, you're right. All of us are. Sexism, like racism, is a societal problem, engrained in all of us. To try and shift away from our current sexist norms we need to redefine them, and that means recasting behaviors that many of us currently view as completely unoffensive.

Another common reaction is something like "these things aren't important, will never change, and feminists should pick their battles." But that's misguided - you're silencing and dismissing viewpoints that deserve to be heard. Just because a subtle but widespread societal norm isn't likely be fixed in the short term doesn't mean it shouldn't be discussed. We certainly have the ability to change own behaviors, and nudge those around us to do the same.

The general EFF phone number is (415) 436-9333.

But if you need legal help you can email info@eff.org.

And if you'd like to work on EFF's tech operations team, email techjobs@eff.org.

Electronic Frontier Foundation - https://eff.org - San Francisco, CA - Frontend/Backend Developers, Technoactivist

The EFF fights for an Internet free of surveillance and censorship.

We're currently hiring frontend and backend web developers: https://www.eff.org/opportunities/jobs/web-developer

We're also hiring a Technoactivist who'll bridge the technology and activism teams: https://www.eff.org/opportunities/jobs/eff-seeks-techno-acti...

If you think you might be a fit for either role, take a moment and get in touch.

A small sample of projects our technology and activism teams have worked on in the last year:

- Launched numerous projects including LetsEncrypt.org, Privacy Badger, Surveillance Self-Defense, DearFCC.org, The Day We Fight Back, Trolling Effects, Tor Challenge and others.

- Worked with over 100 volunteer developers to crowdsource and populate contact-congress, an open dataset describing the contact forms of members of congress.

- Created and open-sourced congress-forms: a delivery mechanism for sending emails to congress based on the open data we crowdsourced.

- Created a new (and soon-to-be open source) activism platform that’s currently live at act.eff.org.

- Launched a preview version of our OpenWireless open source router firmware.

It's a real long-shot that this is going to get enough upvotes to appear on the homepage, but it's really interesting stuff.

After the mess of the last triennial §1201 DMCA exemption (unlocking exemption was removed, causing a kerfuffle), a coalition of organizations rallied around this year and petitioned for a whole host of important exemptions.

These are the opposition comments - its fascinating to see content creators and equipment manufacturers come out and argue for why people shouldn't be able to use and modify the devices/content they've purchased.

The original petitions for exemptions can be found here: http://copyright.gov/1201/2014/petitions/