Live data from Hacker News

FWD:Everyone

fwdeveryone.com

41–50 of 143 posts

Re: FWD:Everyone

#41
post #37

Earlier quoted context omitted.

It only includes the headers of the last email in the thread. But that doesn't guarantee that the person forwarding the email hasn't changed what someone else wrote in the quoted reply text. To me that's actually a serious security issue, and in the long term is more serious than the OAuth thing (which I'm confident that Google will eventually fix). If I'm wrong and it's possible to do then by all means I'll do it th…

I don't believe that is correct. If you check the email source, it includes all the emails with their headers.

What email client are you using? In Gmail the only thing I see between quoted replies are blocks like:

--000000000000061f91056a2a279c

Content-Type: text/html; charset="UTF-8"

Content-Transfer-Encoding: quoted-printable

Re: FWD:Everyone

#42
post #3

Thanks for submitting this, I was surprised to load HN and see it here. I've been meaning to do a proper update on what we've been up to for a while, but basically things that we've done since launching: - 99%+ of non-commercial email threads now parse correctly, better than Gmail in most cases. E.g. check out the inline reply parsing here: https://www.fwdeveryone.com/t/Gb8CYKvGS6uFSXdb_hwiTA/blog-po... - We now supp…

> - You can now anonymize any message contributor. [...] > - 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…

I concur! I don't understand, why was there a need of such services anyway...

Re: FWD:Everyone

#43
post #23

Earlier quoted context omitted.

> That's still the default. That's good to know. > There are lots of legitimate use cases for publishing stuff without permission though, e.g. emails from Steve Jobs or whatever. Just because he's dead, and was a public figure, is it morally acceptable to publish private email? Or even legal, without permission from his estate? A quick search gives me the following. https://blogs.findlaw.com/law_and_life/2018/04/is-i…

In terms of legality there are two separate issues, invasion of privacy and copyright. Things like privacy / libel / slander generally don't apply to the deceased, so in this case I think we can safely ignore that. With respect to copyright, when you send someone an email you're using an agreed upon protocol (RFC 5322, RFC 5598, etc.) that implicitly grants the recipient a copyright. Now you can say this is a bad arg…

IANAL, and so don't know how libel and slander apply to the deceased. I can imagine how estates might have claims. But ??? And even so, there are all the non-deceased correspondents.

I had no clue that email protocols "implicitly grants the recipient a copyright". What are cites for that? Neither https://tools.ietf.org/html/rfc5322 nor https://tools.ietf.org/html/rfc5598 includes "coptright" except in the "Copyright Notice".

But anyway, I get your point about "forc[ing] uploaders to have skin in the game." Maybe that will be enough. Because, as you say, there are many other ways to leak confidential stuff.

Re: FWD:Everyone

#46
post #33

Earlier quoted context omitted.

Well... it is weird. I kinda like that. I recall an app that (I want to say it was for Mac) that turned the trash into a recycle bin and actually "recycled" the content in the sense that files were then sent to other users to look at and if they took them out of the trash the file was gone for everyone else (as if it was a physical print out). It was kinda neat... weird... probabbly a security nightmare... but intere…

The security story will definitely be better once we have the plugin, but it's already quite good. So under the current read-only OAuth model: - Tokens can only be used from our servers, and their use is logged by both us and Google - Tokens are rate limited on Google's end, both per user and per app. Both of these combine to make any sort of large scale breach essentially impossible. We also don't access and store a…

I would like a way to proactively opt out of your application/service, so that there is no chance you ever host an email thread I'm on. Do you provide some mechanism for this? Frankly, I'll take legal action if one of my emails ever ends up on your site.

Re: FWD:Everyone

#47
post #5
post #3

Thanks for submitting this, I was surprised to load HN and see it here. I've been meaning to do a proper update on what we've been up to for a while, but basically things that we've done since launching: - 99%+ of non-commercial email threads now parse correctly, better than Gmail in most cases. E.g. check out the inline reply parsing here: https://www.fwdeveryone.com/t/Gb8CYKvGS6uFSXdb_hwiTA/blog-po... - We now supp…

I really hope this does well (because I'd like to discover more interesting and useful content). I've been on the home page a few times and haven't yet signed up. My behavior on the homepage has been to click the "more example threads" button. I'd guess that the thing that would make me more likely to sign up is to be able to see/discover more great threads before signing up. (Similar suggestions that people have giv…

> I really hope this does well (because I'd like to discover more interesting and useful content).

Thanks! Expect to see more content in the near future.

And we definitely need to redo our front page and incorporate more cool content. It's a lot better than when we launched, but I feel like we haven't quite hit a level of professionalism that's reflective of the rest of the site.

We’re trying to avoid raising capital, so what we’re really looking for right now is a larger company (1,000+ employees) to adopt us for a year so that we can keep evolving the internal tooling and make sure it’s satisfying a real need. (If anyone is interested, send me an email.)

Re: FWD:Everyone

#48
post #3

Thanks for submitting this, I was surprised to load HN and see it here. I've been meaning to do a proper update on what we've been up to for a while, but basically things that we've done since launching: - 99%+ of non-commercial email threads now parse correctly, better than Gmail in most cases. E.g. check out the inline reply parsing here: https://www.fwdeveryone.com/t/Gb8CYKvGS6uFSXdb_hwiTA/blog-po... - We now supp…

One thing you almost certainly want to change is the site's behavior with Javascript disabled - right now, it just shows a white screen with the text "Loading FWD:Everyone".

It's a bit of a pet peeve for me to see pages like this that are primarily static but are not accessible without JS, but I can understand that making a page built with a JS frontend work without it might be more work than it's worth, at least for an early stage project.

However, you really should put up some sort of notice to users - while being able to read a short blurb about what the site is nice, even just "This site requires Javascript to view." is better than a blank page or permanent loading screen.

Post reply on HN