4 ms·
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.
by noxer 4y ago
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.
- neongreen 4y agoNoted. 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/update-on-firefox-send-and-firefox-notes/ 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.
- Raed667 4y agoMaybe allow for a preview of the editing process and before publishing you prompt for a sign-up with the explaining you gave above?