Ask HN: Where to publish a critical work with potentially offensive content • Hacker News Board

Re: Ask HN: Where to publish a critical work with potentially offensive content

#51

Post by noxer » Mon, Oct 17, 2022, 9:22 AM UTC

neongreen wrote: post #22

I run brick.do, which lets anyone publish anything. It’s basically a WYSIWYG pastebin with support for subdomains, nested pages, CSS, and JS. All your posts are disconnected from each other unless you explicitly decide to claim authorship — that is, by default nobody can discover than posts/sites A and B are by the same author. We also don’t divulge authorship information to anyone. We’ve been threatened with lawsuit…

The forced sign-in is an instant turn off. There is no way I'm going to sign in to a random website in 2022 before I tried the product and know its what I want. This will make most people leave and probably collect a bunch of trow-away email addresses at best, I dont think that is the goal.

Have a look at telegra.ph for how it probably should work, maybe require the login to publish to the public in the end.

Re: Ask HN: Where to publish a critical work with potentially offensive content

#52

Post by neongreen » Mon, Oct 17, 2022, 11:01 AM UTC

noxer wrote: post #51

neongreen wrote: post #22

I run brick.do, which lets anyone publish anything. It’s basically a WYSIWYG pastebin with support for subdomains, nested pages, CSS, and JS. All your posts are disconnected from each other unless you explicitly decide to claim authorship — that is, by default nobody can discover than posts/sites A and B are by the same author. We also don’t divulge authorship information to anyone. We’ve been threatened with lawsuit…

The forced sign-in is an instant turn off. There is no way I'm going to sign in to a random website in 2022 before I tried the product and know its what I want. This will make most people leave and probably collect a bunch of trow-away email addresses at best, I dont think that is the goal. Have a look at telegra.ph for how it probably should work, maybe require the login to publish to the public in the end.

Noted.

One thing to keep in mind here is that anything that allows anonymous publishing/uploading/etc will be used for malware delivery. This is what killed Firefox Send: https://blog.mozilla.org/en/products/firefox/firefox-news/up...

Even with forced sign-in, we see multiple phishing attempts per month. People sign up and create pages saying something like "You have a new IMPORTANT PDF FILE, click here to open". The links always lead to fake OneDrive pages. This hurts our users because then the whole domain is marked as suspicious.

My gut feeling is that without forced sign-in this could be done at scale. I don't know how Telegraph solves it.

This said, I think "maybe require the login to publish to the public in the end" could be a good workflow. No idea how many people feel the same way you do, though. Off the top of my head I can't remember any other mainstream SaaS things that do it.

Re: Ask HN: Where to publish a critical work with potentially offensive content

#53

Post by Raed667 » Mon, Oct 17, 2022, 3:38 PM UTC

neongreen wrote: post #52

noxer wrote: post #51

Earlier quoted context omitted.

The forced sign-in is an instant turn off. There is no way I'm going to sign in to a random website in 2022 before I tried the product and know its what I want. This will make most people leave and probably collect a bunch of trow-away email addresses at best, I dont think that is the goal. Have a look at telegra.ph for how it probably should work, maybe require the login to publish to the public in the end.

Noted. One thing to keep in mind here is that anything that allows anonymous publishing/uploading/etc will be used for malware delivery. This is what killed Firefox Send: https://blog.mozilla.org/en/products/firefox/firefox-news/up... Even with forced sign-in, we see multiple phishing attempts per month. People sign up and create pages saying something like "You have a new IMPORTANT PDF FILE, click here to open". The…

Maybe allow for a preview of the editing process and before publishing you prompt for a sign-up with the explaining you gave above?