It would be great if timeline progress could be saved (with reasonable reliability) without having to set up an account. Revisit this when/if technology changes.
Can't store the state in a cookie. 4096 bytes max. Probably have more, but can't rely on that and overflow degrades badly (cookie is discarded). Setting lots of cookies is not good behavior and not worth it.
HTML5 localStorage sounds perfect, but triggers interactions about the app wanting to store state. That makes some people nervous because they don't know what is being asked and they worry the app is somehow doing something bad. Not worth it.
Session state storage is just as much server effort as an account, but accounts allow contact, don't get lost, and allow more than one person on a computer without confusion. Requiring sign-in seems better/clearer.
Signing in with other social media platforms involves loading those platforms to use their APIs, so the site becomes part of that tracking. The process is not significantly smoother than creating an account, and for people worried about social media intrusion it can cause concern. Essentially you are expending effort to add more (possibly concerning) code while giving up the possibility of contacting users directly. Nope.
It would be great if timeline progress could be saved (with reasonable reliability) without having to set up an account. Revisit this when/if technology changes.
Can't store the state in a cookie. 4096 bytes max. Probably have more, but can't rely on that and overflow degrades badly (cookie is discarded). Setting lots of cookies is not good behavior and not worth it.
HTML5 localStorage sounds perfect, but triggers interactions about the app wanting to store state. That makes some people nervous because they don't know what is being asked and they worry the app is somehow doing something bad. Not worth it.
Session state storage is just as much server effort as an account, but accounts allow contact, don't get lost, and allow more than one person on a computer without confusion. Requiring sign-in seems better/clearer.
Signing in with other social media platforms involves loading those platforms to use their APIs, so the site becomes part of that tracking. The process is not significantly smoother than creating an account, and for people worried about social media intrusion it can cause concern. Essentially you are expending effort to add more (possibly concerning) code while giving up the possibility of contacting users directly. Nope.