There are many advantages of having a 'default' option over having it auto-selected.
* It's possible to post to another journal from the update page by supplying a username and password without having to log in first, and indeed, the update page can even be used when logged out. In this scenario a 'default' option is the only thing that makes sense.
* On the backend, being able to accept 'default' as an option (which it would then translate to the appropriate security level before saving the post) would mean that other non-Web clients can use that easily. True, it doesn't have to show on the Web frontend, but that brings me to another reason:
* The other journal options on the update page all have a "Journal Default" option, too. It would be nice for consistency, too.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2009-04-15 10:49 pm (UTC)There are many advantages of having a 'default' option over having it auto-selected.
* It's possible to post to another journal from the update page by supplying a username and password without having to log in first, and indeed, the update page can even be used when logged out. In this scenario a 'default' option is the only thing that makes sense.
* On the backend, being able to accept 'default' as an option (which it would then translate to the appropriate security level before saving the post) would mean that other non-Web clients can use that easily. True, it doesn't have to show on the Web frontend, but that brings me to another reason:
* The other journal options on the update page all have a "Journal Default" option, too. It would be nice for consistency, too.