A link link was recently added to all answers. Perhaps just today. I just noticed it for the first time a few minutes before I read this question. See Olafur's answer: meta.stackexchange.com/questions/1569/…
–
ravenJul 1 '09 at 23:01

Is the link new? I swear I'd never noticed it before.
–
Gareth SimpsonJul 2 '09 at 8:48

You could also upvote the answer, and then find the answer(s) you upvoted.
–
Tom RitterJul 1 '09 at 19:10

3

this will be even better when/if the search syntax includes filters to narrow things down to answers I upvoted.
–
Jason SJul 1 '09 at 22:07

4

@Tom Ritter: If the answer isn't a good answer to the question, this seems like a poor implementation. I've had cases where I wanted to remember/revisit an answer, but it wasn't a good answer to the original question, and thus did not deserve an up vote.
–
tnorthcuttAug 31 '09 at 20:18

@Tom Ritter: up-voting would leave a trail to find the answer you wanted, but IIRC you can't undo an up-vote after a certain amount of time has passed. So you wouldn't be able to get rid of it as a bookmark once you no longer wanted to remember it.
–
Adam PoradMay 14 '10 at 20:16

EDIT
And as per comment under using the share link is a simpler method of creating a link.

You need to examine the page source code to do that. That is very easy to do. For instance in Firefox use Ctrl+U
You then need to search for the answer you need to link.
In Firefox the source is opened in a new tab or window and searchable using Ctrl+F
Identify the answer number.
Create a bookmark using

The (thread's) questions URL or bookmark

Append a hash symbol #

Followed by the number you discovered.

I do not know if that link is to a permalink and will be stable but I imagine the worst it will do is fail to find the specific answer and default to the top of the thread.

Quicker and easier to click "Fave" on an answer than use browser
bookmark functions and deciding where to save it

We'd have "bookmarked" answers right in our Stack profile

However, these pros are all pointless unless Stack implemented a user defined "section" area for our fave answers, so we could order them and have folders/sub folders etc.
As otherwise we just have a potential clutter of fave answers in our Stack profile in one huge long list. Once you have (say) 40, how can they easily be found and used for future reference?

However, if they did have some kind of ordering system, they'd then just be duplicating browser features, and I find that a pointless waste of dev time, and as such a useless feature really.

In that, we already have the feature with browser bookmarks as good as Stack could make it (if an ordering system was given with the feature), or better than Stack would make it if fave answers were just a big list of answers we liked.

Bookmarks are perfect

I think people should consider more closely how great bookmarks can be.

Make a new Stack bookmark folder for answers, then sub folders relevant to whatever you bookmark there, and then name files relevant too.

Such as:

/Stack Answers

-> /PHP

->-> PDO prepared statements great notes

->-> time() function perfect usage description

-> /CSS

->-> Z-Index good description

->-> Difference between positions - absolute, relative etc

The Stack Share link is perfect for getting the URL to store as a bookmark.

Other caveats to answer faves

Stack content can be removed at any time, so if an answer is of great resource to you, and future reference, it and many others can be lost.

If you don't like browser bookmarks, and or are wanting a great collection of info and useful data for future reference, then perhaps you need to be copy/pasting answer text into a collection of files on your PC, in folders named to store them sanely.

Having fave answers would also would mean a potential for people to upvote an answer without any justification other than it helped them, and might not be a good answer for the question.

Habits can be formed, where someone reads an answer, likes it, makes it a fave and upvotes it.
Not ideal really.

-1. Bookmarks may be useful for some people (including you), but they are nowhere near "perfect". If the site didn't already have favourite questions, your logic can also be used to argue against them being implemented. Arguing against a feature request just because you don't mind its costs doesn't take the other users of the site into consideration.
–
March HoFeb 10 at 13:01