Direct reply: You could add the 2 links to user settings and homenode editting to your browser bookmarks, you could create a local html page with links to all your favorite/frequently used links, or you could enable the personal nodelet and adds links there.

Indirect reply, aimed to all monks:

I don't mean to sound negative here, so if it sounds that way, just remember that is not my intention ;) This is a plea to everyone really. I am not pointing fingers at anyone in particular, this is just a general pattern I am pointing out. I myself have been guilty of this, as it is easy to get carried away with ideas sometimes. There used to be a time where tweaking the site to fit each person's level of satisfaction meant introducing major new features; things that many monks wanted to see implemented as it would change the way the site worked. As time has gone on and the large changes have been implemented, an increasing number of monks have begun requesting little features that don't change much at all.

I know that programmers are defined to be of the lazy type, but really, what is the point of changing something to save one or two lousy mouse clicks? We used to add useful features that actually modified the way things work. Now we've come to the point of nitpicking the small details that are already implemented, but aren't done the exact way every single monk wants to see them.

Please, before submitting a new feature request, take into consideration the following key points:

• Is this new change worth the time and effort that will be required in order to implement it? If it's something that is already there, just one click away, chances are the answer is 'no'.
• Is this change likely to be appreciated by a majority of the monks, or is it something so small and insignificant that only a few will want the change implemented.
• Is the change likely to take up a significant amount of additional server resources that is just not worth the outcome of the change?
• Is the feature something that should actually be implemented directly into the website interface, or would it be more ideal to create an external client?

Basically all I am saying is that each individual needs to draw a line between "I think we should implement this because it will be useful to the majority of users" and "I want this implemented just because I want it.". Personalization is nice, but it is extremely easy sometimes to get carried away.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.