3 ms·
I'm sorry, but the idea of a product designed specifically to facilitate the mass redistribution of communications normally assumed to be private by default is
by yellowapple 8y ago
I'm sorry, but the idea of a product designed specifically to facilitate the mass redistribution of communications normally assumed to be private by default is deeply disturbing. Do I need to start including EULAs in every email I send? In what multiverse is this sort of thing okay?
Unless permission requests are mandatory and forever will be (regardless of anonymization), I will automatically refuse to communicate via email (and possibly any other implied-private medium, including one-to-one chats, mail, and SMS) with anyone I know to be using this service; instead, the only communications from me with these people will be through systems/services in which communications are already assumed to be public or shared (e.g. forums, mailing lists, public social media posts, blog posts / webpages, etc.). Likewise, I will never use this service myself; there are plenty of services out there that facilitate public-record written electronic communication while being upfront about it.
To reiterate: my emails to others should be considered private between myself and the recipient unless both of us explicitly consent to their publication, anonymized or otherwise. That's basic fucking courtesy - courtesy which FWD:Everyone seems to be explicitly designed to violate.
- beager 8y agoThe thing is, they could easily extract participants and require opt-in from all parties.
- LeifCarrotson 8y agoIt requires opt-in from all participants in the conversation, as Alex posted down this thread last week: https://news.ycombinator.com/item?id=17401425 https://news.ycombinator.com/item?id=17401425 > We actually currently require double opt-in permission for each message contributor in a thread to share stuff publicly. That might change in the future, we're still playing around with the model. And yes, it does violate basic expectations - that's on purpose.
- yellowapple 8y agoPer Alex's comment on this post (and, in fact, the current top comment): "Permission requests are becoming optional, at least for now. Previously we required permission for all non-anonymized message contributors, now there will be an option to publish stuff immediately and let people anonymize themselves later if they want. If this is excessively abused we'll re-evaluate this, but we've tried to build things to incentivize good judgment." It requires opt-in from all parties now, but there's already a publicized plan to change that. "And yes, it does violate basic expectations - that's on purpose." I'm not sure how "don't worry guys, we're intentionally building a product to facilitate the wholesale violation of decades-old email etiquette and common courtesy" is supposed to make this idea sound any less horrific.
- Alex3917 8y agoSo just to clarify, we're changing the product to make it possible to upload stuff without permission, but we're not trying to induce bad behavior. E.g. Gmail has a reply all button and a forward button, but they don't encourage users to abuse them. They're just there for situations where it's (hopefully) appropriate, and they trust users to exercise good judgment. And for the most part it works, since there are only so many times you can abuse those features before people stop sending you emails. There are many times when it's easy to get verbal permission from someone, but difficult or impossible to get email permission, e.g. if their email address has changed.
- yellowapple 8y ago"Gmail has a reply all button and a forward button" Last I checked, neither of those buttons are designed to publish the whole conversation to the whole world via the World Wide Web. Your product is. Therefore: "we're changing the product to make it possible to upload stuff without permission" Then you're changing the product in a way that is absolutely unacceptable for privacy reasons. "we're not trying to induce bad behavior" I'm not trying to induce meth addiction; I'm just selling it and hoping it won't be abused. "And for the most part it works, since there are only so many times you can abuse those features before people stop sending you emails." Then you're missing the point: I want to minimize the potential for abuse to ever happen in the first place. Hence the ultimatum in my top-level comment: if I know someone is using this service, then I'm going to refuse to communicate with that person via implicitly/semantically-private channels (in fact, it'd be nice if there were some way to programmatically get a list of email addresses registered with this service so I can maintain a blacklist on my SMTP servers and prevent myself from sending anything to them by accident). I might waver from that if FWD:Everyone offers the ability to preemptively register my email address(es) in an "automatically deny permission" list. "There are many times when it's easy to get verbal permission from someone, but difficult or impossible to get email permission, e.g. if their email address has changed." Then that request for verbal permission should be along the lines of "hey, I want to post our conversation from a while back to FWD:Everyone; do you mind logging in real quick and approving it since the request probably went to your old email?". Even better if FWD:Everyone would keep track of who owns what emails and send requests to alternate emails if not approved in a certain amount of time. Otherwise, tough beans. Just because Disney didn't respond to my email asking for permission to sell bootleg copies of Frozen on the black market (e.g. because I sent it to the wrong address or because it's obviously going to be a "no") doesn't mean I'm automatically allowed to do so. In other words: if I'm unable to provide consent, then assume that I do not consent. Inconvenient, sure, but that ain't my problem.