Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>But this is a technical document about browser features, I'm a little frustrated that this is being coordinated over a proprietary SaaS service instead of over Git[0] with markdown or something.

Then maybe the public SaaS services should be of a better quality so that Mozilla employees want to use them.

>I think a lot more than that, I'm frustrated that the document is being made publicly available on that platform. When someone links to a web standard on Github, often it's because the standard is seeing active participation. For something that is being linked to a public view, I would have loved to see at least a PDF export or something.

There is a PDF export for google docs which is available to all users. File > Download > PDF.



> Then maybe the public SaaS services should be of a better quality so that Mozilla employees want to use them.

Maybe a company that has been throwing money into dozens of random privacy initiatives outside of the browser market (some good and some bad) would be a good fit for solving that problem? Dogfooding software is a really good strategy for UX design after all.

> There is a PDF export for google docs which is available to all users. File > Download > PDF.

That's exactly what I mean. Someone wrote this blog post, could they have hit the PDF export button and then linked to that PDF hosted on Mozilla's servers? That would have prevented the vandalism problem they ran into.

The issue I have isn't that I can't export to PDF from Google Docs. The issue that I have is that I have to visit Google Docs and load a ton of proprietary Javascript just so I can hit a PDF export button. Google Docs has an API, Mozilla could have a script that's just auto-exporting a PDF and hosting it on a public endpoint on a regular interval.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: