Identifying the linked-to post in a topic (SMF patch)

[PowerGlove]

Hey, everybody!

This suggestion came from Cyrus, and I think it's a really good idea, so I thought I'd sink some time into it, and put together a patch.

Basically, the idea is to make it easier to identify the target post after clicking an ordinary post link, like: https://bitcointalk.org/index.php?topic=4193.msg60743#msg60743.

Normally, the (optional) fragment identifier at the end of the URL (#msg60743 in the example link) suffices to position the viewport so that the linked-to post is obvious/unambiguous. But, sometimes that mechanism isn't precise enough, like when the post is the last or second-to-last one on its page (then, I often find myself hovering over the subject link and comparing it to the address bar to confirm that I'm reading the right post).

I also sometimes lose track of the linked-to post when I scroll around the page for a bit to get some context before reading the actual post (then, I find myself going to the address bar and hitting Enter so that the browser snaps to the right post again).

In the worst case, both of those situations occur: After landing on the relevant topic-page, you scroll around a bit for some context, then you use the Enter trick to snap to the right post, but that's not reliable for the last or second-to-last post, so you have to do the address-comparing thing too.

I also have to imagine that report-handling would be a little more pleasant for moderators if they had a reliable way to always quickly identify the linked-to post.

Anyway, it's tempting to make the linked-to post really stand out by putting a differently-colored background or border on it, or an inset/outset box-shadow or something, but, all the variations of that idea that I tried ended up looking pretty naff (and, anyway, I don't really like messing with the SMF aesthetic that a lot of veteran members prefer as-is). In this case, I think it's wiser to just do something really subtle and "quiet" (after all, the forum has been just fine for a long time without this, so I don't think it should be something that jumps out from the page and draws your eye too much; it should just be something that people who know what to look for, will look for).

I've done this patch in two styles:

Style A

This one just makes the subject-line of the linked-to post render differently than normal (with font-style: italic).

Code:

--- baseline/Sources/Display.php	2011-02-07 16:45:09.000000000 +0000
+++ modified/Sources/Display.php	2024-04-04 00:02:44.000000000 +0000
@@ -230,24 +230,25 @@
 					SELECT COUNT(*)
 					FROM {$db_prefix}messages
 					WHERE ID_MSG < $virtual_msg
 						AND ID_TOPIC = $topic", __FILE__, __LINE__);
 				list ($context['start_from']) = mysql_fetch_row($request);
 				mysql_free_result($request);
 			}
 			
 			// We need to reverse the start as well in this case.
 			$_REQUEST['start'] = empty($options['view_newest_first']) ? $context['start_from'] : $topicinfo['numReplies'] - $context['start_from'];
 
 			$context['robot_no_index'] = true;
+			$context['requested_msg'] = $virtual_msg;
 		}
 	}
 
 	// Create a previous next string if the selected theme has it as a selected option.
 	$context['previous_next'] = $modSettings['enablePreviousNext'] ? '<a href="' . $scripturl . '?topic=' . $topic . '.0;prev_next=prev#new">' . $txt['previous_next_back'] . '</a> <a href="' . $scripturl . '?topic=' . $topic . '.0;prev_next=next#new">' . $txt['previous_next_forward'] . '</a>' : '';
 
 	// Check if spellchecking is both enabled and actually working. (for quick reply.)
 	$context['show_spellchecking'] = !empty($modSettings['enableSpellChecking']) && function_exists('pspell_new');
 
 	// Censor the title...
 	censorText($topicinfo['subject']);
 	$context['page_title'] = $topicinfo['subject'];

Code:

--- baseline/Themes/default/Display.template.php	2010-10-22 01:38:35.000000000 +0000
+++ modified/Themes/default/Display.template.php	2024-04-04 00:03:41.000000000 +0000
@@ -359,32 +359,33 @@
 					echo '
 								<a href="', $scripturl, '?action=pm;sa=send;u=', $message['member']['id'], '" title="', $message['member']['online']['label'], '">', $settings['use_image_buttons'] ? '<img src="' . $settings['images_url'] . '/im_' . ($message['member']['online']['is_online'] ? 'on' : 'off') . '.gif" alt="' . $message['member']['online']['label'] . '" border="0" />' : $message['member']['online']['label'], '</a>';
 			}
 		}
 		// Otherwise, show the guest's email.
 		elseif (empty($message['member']['hide_email']))
 			echo '
 								<br />
 								<br />
 								<a href="mailto:', $message['member']['email'], '">', ($settings['use_image_buttons'] ? '<img src="' . $settings['images_url'] . '/email_sm.gif" alt="' . $txt[69] . '" title="' . $txt[69] . '" border="0" />' : $txt[69]), '</a>';
 
 		// Done with the information about the poster... on to the post itself.
+		$is_requested_message = isset($context['requested_msg']) && $context['requested_msg'] == $message['id'];
 		echo '
 							</div>
 						</td>
 						<td valign="top" width="85%" height="100%">
 							<table width="100%" border="0"><tr>
 								<td valign="middle"><a href="', $message['href'], '"><img src="', $message['icon_url'] . '" alt="" border="0" /></a></td>
 								<td valign="middle">
-									<div style="font-weight: bold;" id="subject_', $message['id'], '">
+									<div style="font-weight: bold;', $is_requested_message ? ' font-style: italic;' : '', '" id="subject_', $message['id'], '">
 										<a href="', $message['href'], '">', $message['subject'], '</a>
 									</div>';
 
 		// If this is the first post, (#0) just say when it was posted - otherwise give the reply #.
 		echo '
 									<div class="smalltext">&#171; <b>', !empty($message['counter']) ? $txt[146] . ' #' . $message['counter'] : '', ' ', $txt[30], ':</b> ', $message['time'], ' &#187;</div></td>
 								<td align="', !$context['right_to_left'] ? 'right' : 'left', '" valign="bottom" height="20" style="font-size: smaller;">';
 
 		// Can they reply? Have they turned on quick reply?
 		if ($context['can_reply'] && !empty($options['display_quick_reply']))
 			echo '
 					<a href="', $scripturl, '?action=post;quote=', $message['id'], ';topic=', $context['current_topic'], '.', $context['start'], ';num_replies=', $context['num_replies'], ';sesc=', $context['session_id'], '" onclick="doQuote(', $message['id'], ', \'', $context['session_id'], '\'); return false;">', $reply_button, '</a>';

Style B

This one places a small, low-opacity Unicode arrow just before the subject-line of the linked-to post.

Code:

--- baseline/Sources/Display.php	2011-02-07 16:45:09.000000000 +0000
+++ modified/Sources/Display.php	2024-04-04 00:02:44.000000000 +0000
@@ -230,24 +230,25 @@
 					SELECT COUNT(*)
 					FROM {$db_prefix}messages
 					WHERE ID_MSG < $virtual_msg
 						AND ID_TOPIC = $topic", __FILE__, __LINE__);
 				list ($context['start_from']) = mysql_fetch_row($request);
 				mysql_free_result($request);
 			}
 			
 			// We need to reverse the start as well in this case.
 			$_REQUEST['start'] = empty($options['view_newest_first']) ? $context['start_from'] : $topicinfo['numReplies'] - $context['start_from'];
 
 			$context['robot_no_index'] = true;
+			$context['requested_msg'] = $virtual_msg;
 		}
 	}
 
 	// Create a previous next string if the selected theme has it as a selected option.
 	$context['previous_next'] = $modSettings['enablePreviousNext'] ? '<a href="' . $scripturl . '?topic=' . $topic . '.0;prev_next=prev#new">' . $txt['previous_next_back'] . '</a> <a href="' . $scripturl . '?topic=' . $topic . '.0;prev_next=next#new">' . $txt['previous_next_forward'] . '</a>' : '';
 
 	// Check if spellchecking is both enabled and actually working. (for quick reply.)
 	$context['show_spellchecking'] = !empty($modSettings['enableSpellChecking']) && function_exists('pspell_new');
 
 	// Censor the title...
 	censorText($topicinfo['subject']);
 	$context['page_title'] = $topicinfo['subject'];

Code:

--- baseline/Themes/default/Display.template.php	2010-10-22 01:38:35.000000000 +0000
+++ modified/Themes/default/Display.template.php	2024-04-04 00:05:27.000000000 +0000
@@ -359,33 +359,34 @@
 					echo '
 								<a href="', $scripturl, '?action=pm;sa=send;u=', $message['member']['id'], '" title="', $message['member']['online']['label'], '">', $settings['use_image_buttons'] ? '<img src="' . $settings['images_url'] . '/im_' . ($message['member']['online']['is_online'] ? 'on' : 'off') . '.gif" alt="' . $message['member']['online']['label'] . '" border="0" />' : $message['member']['online']['label'], '</a>';
 			}
 		}
 		// Otherwise, show the guest's email.
 		elseif (empty($message['member']['hide_email']))
 			echo '
 								<br />
 								<br />
 								<a href="mailto:', $message['member']['email'], '">', ($settings['use_image_buttons'] ? '<img src="' . $settings['images_url'] . '/email_sm.gif" alt="' . $txt[69] . '" title="' . $txt[69] . '" border="0" />' : $txt[69]), '</a>';
 
 		// Done with the information about the poster... on to the post itself.
+		$is_requested_message = isset($context['requested_msg']) && $context['requested_msg'] == $message['id'];
 		echo '
 							</div>
 						</td>
 						<td valign="top" width="85%" height="100%">
 							<table width="100%" border="0"><tr>
 								<td valign="middle"><a href="', $message['href'], '"><img src="', $message['icon_url'] . '" alt="" border="0" /></a></td>
 								<td valign="middle">
 									<div style="font-weight: bold;" id="subject_', $message['id'], '">
-										<a href="', $message['href'], '">', $message['subject'], '</a>
+										', $is_requested_message ? '<span style="opacity: 30%;">&#8702;&nbsp;</span>' : '', '<a href="', $message['href'], '">', $message['subject'], '</a>
 									</div>';
 
 		// If this is the first post, (#0) just say when it was posted - otherwise give the reply #.
 		echo '
 									<div class="smalltext">&#171; <b>', !empty($message['counter']) ? $txt[146] . ' #' . $message['counter'] : '', ' ', $txt[30], ':</b> ', $message['time'], ' &#187;</div></td>
 								<td align="', !$context['right_to_left'] ? 'right' : 'left', '" valign="bottom" height="20" style="font-size: smaller;">';
 
 		// Can they reply? Have they turned on quick reply?
 		if ($context['can_reply'] && !empty($options['display_quick_reply']))
 			echo '
 					<a href="', $scripturl, '?action=post;quote=', $message['id'], ';topic=', $context['current_topic'], '.', $context['start'], ';num_replies=', $context['num_replies'], ';sesc=', $context['session_id'], '" onclick="doQuote(', $message['id'], ', \'', $context['session_id'], '\'); return false;">', $reply_button, '</a>';

As always, everyone's thoughts/notes/votes are appreciated.

@theymos: Style A doesn't add or remove any markup, so post scrapers (probably) won't be affected by the change. Style B introduces a new <span> element just before the <a> element that wraps the subject-line, so if that's the one you like (assuming that you like either one to begin with), then LoyceV and TryNinja would probably appreciate some notice before you merge it, so that they can tweak their scrapers if necessary.

[1714525109]

1714525109

[1714525109]

1714525109

[1714525109]

1714525109

[BlackBoss_]

I read your description many times to understand problems in this context and I faced with indexing problem after clicking on a link too. I see your solution is good but I also see you mentioned about issue for moderator when handling report.

I propose you to code a SMF patch, together with this one or another one, to quote a linked post. So with that patch, we will have two things like

- Linked-to post like this patch.
- A quote of that post.

If I am a moderator, and receive a report, with a post link, I will get its link and if possible, a quoted content of that reported post.

[NotATether]

PowerGlove, you seem to know a lot about the custom SMF front end, so let me ask you a question:

When you open the HTML source of this page for example, there are a bunch of "shadow" posts under the OP. These are invisible posts that have the same HTML structure as real posts, but they don't have anything inside them. There is usually a random amount of these displayed, anywhere from one to three. So what is the deal with that, and where do they come from?

[LoyceV]

Normally, the (optional) fragment identifier at the end of the URL (#msg60743 in the example link) suffices to position the viewport so that the linked-to post is obvious/unambiguous. But, sometimes that mechanism isn't precise enough, like when the post is the last or second-to-last one on its page

When images without height/width tags load, the page "jumps" a bit, which makes the post I'm looking for not the first one that shows even if it's in the middle of a long page.

I also sometimes lose track of the linked-to post when I scroll around the page for a bit to get some context before reading the actual post (then, I find myself going to the address bar and hitting Enter so that the browser snaps to the right post again).

I do that too

LoyceV and TryNinja would probably appreciate some notice before you merge it

I have so many (old) scrapers, I can't tell if this is going to break something. I'll just see when it happens.

I think your changes are too subtle to quickly identify the post I'm looking for.

[FatFork]

PowerGlove, you seem to know a lot about the custom SMF front end, so let me ask you a question:

When you open the HTML source of this page for example, there are a bunch of "shadow" posts under the OP. These are invisible posts that have the same HTML structure as real posts, but they don't have anything inside them. There is usually a random amount of these displayed, anywhere from one to three. So what is the deal with that, and where do they come from?

There is a topic where this was discussed a bit: https://bitcointalk.org/index.php?topic=5474601

As shahzadafzal explained, there is something in the backend that generates these "dummyPosts" and could be related to forum ads.

Only theymos can answer this, but I think it has something to do with the "ad", this bitcointalk ad that appears on every page after the first posts. Because I see there's a pattern, although the number will change as the ad changes, but the ID of this ad has something to do with these posts and this number.

Also, sometimes this post appears once, sometimes twice, or maybe three or four times in a row. It can be above the ad, or sometimes it's around the ad.

[ibminer]

LoyceV and TryNinja would probably appreciate some notice before you merge it, so that they can tweak their scrapers if necessary.

BPIP grabs this title for the smerit log as well, so if style B is chosen, a notice would also be nice to suchmoon or I although I will double-check later if it actually effects us, I just know the order of the tree elements are important on some of the pages.

edit:
Style C?  Or too obvious?
 


Would be on the <td> above that div:

Code:

<td valign="middle" style="background: rgb(200,200,200);border: 2px solid rgb(60,60,60); padding: 7px;">

[NotATether]

As shahzadafzal explained, there is something in the backend that generates these "dummyPosts" and could be related to forum ads.

Only theymos can answer this, but I think it has something to do with the "ad", this bitcointalk ad that appears on every page after the first posts. Because I see there's a pattern, although the number will change as the ad changes, but the ID of this ad has something to do with these posts and this number.

Also, sometimes this post appears once, sometimes twice, or maybe three or four times in a row. It can be above the ad, or sometimes it's around the ad.

I'm not sure if it's related to ads since in this particular rendition of this topic, the ad HTML is below the <div>'s for all the dummy posts (which itself is below the OP).

[PowerGlove]

PowerGlove, you seem to know a lot about the custom SMF front end, so let me ask you a question: (...)

I can only guess at what those might be. I think a satisfying answer would have to come from theymos.

I think your changes are too subtle to quickly identify the post I'm looking for.

Yep. I can appreciate that point of view. It's worth pointing out, though, that it's difficult to gauge things just by looking at the example images in the OP; when you see either style A or style B in its proper context (that is, when a differently-rendered post is surrounded by posts that aren't rendered differently), then the differently-rendered post stands out pretty obviously (at least, to my eyes it does).

BPIP grabs this title for the smerit log as well (...)

Oops, how could I forget about you and suchmoon? My bad.

(...) Style C?  Or too obvious?

I think that one is maybe a little too loud. (But, I'm aware that I lean pretty subtle most of the time.)

I mean, my point of view isn't really any more valuable than anyone else's, so if most people think/feel that something a bit more obvious is necessary, then I'm happy to produce patches for styles C/D/E/etc. based on any idea(s) that people like.

One thing to consider, though, is that some users are running modified/customized stylesheets, so a robust solution should try to avoid relying on hard-coded color values (from that point of view, styles A and B are nice and resilient; they'll likely work as intended with any custom stylesheet).

Personally, I think style B has quite a lot of promise; the way it's presented in the OP looks pretty good to me as-is, but the HTML for that style (<span style="opacity: 30%;">&#8702;&nbsp;</span>) actually has two degrees of freedom to play with: both the opacity value and the specific Unicode symbol can make a pretty big visual difference. For example, if you bump the opacity up to 60% and change the symbol from U+21FE to U+2B0A (so, <span style="opacity: 60%;">&#11018;&nbsp;</span>), then, it'll look like this:



I suppose, if I ignore my thoughts about custom-stylesheet resilience, and do a slightly taller glyph (U+2BAF), in 60% opacity primary blue, or something, then it's easy to get it to pretty much jump out from the page (<span style="color: #0000ff99;">&#11183;&nbsp;</span>):



(Something to consider when picking a glyph, is that some of them can either render quite differently or be missing entirely on some devices/browsers/fonts; if that ends up being an actual issue, then, I think what I'll do is bake the symbol into a little transparent PNG, and re-work the patch around that.)

[Upgrade00]

Sometimes the post you're looking for will not even be on the landing page after clicking on the link. This I believe happens when some posts in the thread were deleted. Will this pose a problem or it happens too few times for it to actually matter.

I will also want a more obvious marker, maybe a darker highlight that fades away after a few seconds on the page. Is this even a possibility?

[Sandra_hakeem]

I will also want a more obvious marker, maybe a darker highlight that fades away after a few seconds on the page. Is this even a possibility?

There's a possibility that Gloves would put up a patch with the darker highlight, but not with an instruction that it fades away on its own after a couple of seconds; not unless you manually refresh the page -- considering the fact that the forum's time-out is way beyond your description.

[Alone055]

I will also want a more obvious marker, maybe a darker highlight that fades away after a few seconds on the page. Is this even a possibility?

What's the point of having a marker if it fades away or disappears and you will still have to find the linked-to post by re-entering the link in the URL bar? The actual reason behind this proposal is so that you don't lose the post that you clicked a link to and be able to find it easily even after scrolling up or down on the page.

You need to read this part of the opening post once again I believe because you clearly didn't understand the context of the change being proposed or implemented:

I also sometimes lose track of the linked-to post when I scroll around the page for a bit to get some context before reading the actual post (then, I find myself going to the address bar and hitting Enter so that the browser snaps to the right post again).

In the worst case, both of those situations occur: After landing on the relevant topic-page, you scroll around a bit for some context, then you use the Enter trick to snap to the right post, but that's not reliable for the last or second-to-last post, so you have to do the address-comparing thing too.

[ibminer]

BPIP grabs this title for the smerit log as well (...)

Oops, how could I forget about you and suchmoon? My bad.

Ah, no worries, it looks like the <span> wouldn't really effect our parsers anyway.

In terms of hard-coding any styles in general, is there any reason you are not avoiding the <span> all together and adding an "id" to the <a> element, then just adding to the CSS file?  

<a id="selected_post"... then

Code:

#selected_post::before {
  opacity: 30%;
  content: "\2192";
}

[Upgrade00]

<snip>

Reading the thread shows that OP was asking for personalized suggestions, basically the pov of other users. I personally will easily keep tabs on a reply if it is highlighted to me once I land on the page, even if hat fades of later. And it's a middle ground between having less obvious markers which can easily be missed and loud ones which will stand out too much in the page.

Try having some individualized opinions yourself, not so hard, eh?

[joker_josue]

Style A

This one just makes the subject-line of the linked-to post render differently than normal (with font-style: italic).


~~

@theymos: Style A doesn't add or remove any markup, so post scrapers (probably) won't be affected by the change. Style B introduces a new <span> element just before the <a> element that wraps the subject-line, so if that's the one you like (assuming that you like either one to begin with), then LoyceV and TryNinja would probably appreciate some notice before you merge it, so that they can tweak their scrapers if necessary.

It's not that I've experienced this type of situation as a big problem over the years. But, in reality, it was something that already happened, especially on longer pages. I think this adjustment would be useful.

But, I believe the best approach is option A, which requires less code addition, being more a matter of style. And it's always easier and more practical to make these types of adjustments. I would just add maybe a color change, or a different font size, to make this situation stand out more than just italics.

Besides, for me, it could be a good improvement to the dynamics of the forum.
Congratulations PowerGlove for this good initiative.

[TryNinja]

I’ll have to double check when I get my laptop in ~3 days but as long as you leave the title alone inside its own tag, I can always adjust my scraper. Just don’t commingle the arrow and the actual title in a way you can’t programmatically differentiate both of them.

[Alone055]

Reading the thread shows that OP was asking for personalized suggestions, basically the pov of other users. I personally will easily keep tabs on a reply if it is highlighted to me once I land on the page, even if hat fades of later. And it's a middle ground between having less obvious markers which can easily be missed and loud ones which will stand out too much in the page.

Try having some individualized opinions yourself, not so hard, eh?

Seems like you have taken it personally although my intention wasn't to make you feel that way. When we talk about personalized suggestions and opinions, they are supposed to be a solution to the problem being discussed. I don't see any value in a personalized suggestion that isn't in any way solving the problem. That was what I was trying to say if the marker fades away, there is no point in having it in the first place because you would still lose track of the post you were redirected to, you might be able to easily identify the posts but it doesn't mean it's a universal solution, and that is what is being discussed here. 

Talking about having individualized opinions myself, I did face the problem being discussed here all the time, however, the solutions discussed seemed perfect to me, so I didn't want to repeat anything, but since I didn't find your opinion suitable, I thought of pointing that out since all of us have freedom of speech in the forum and I have every right to do that. 

[PowerGlove]

Sometimes the post you're looking for will not even be on the landing page after clicking on the link. (...) Will this pose a problem or it happens too few times for it to actually matter.

Missing/deleted posts won't confuse this patch. What'll happen is that none of the posts will be "marked". (Typically, when I land on a topic-page that's missing the post I was looking for, I usually know that's what's happened because the viewport hasn't snapped to a post, and I can still see the SMF menu; that'll still be the case with this patch.)

In terms of hard-coding any styles in general, is there any reason you are not avoiding the <span> all together and adding an "id" to the <a> element, then just adding to the CSS file?

That's a cool idea (that is, using a content string on a ::before pseudo-element), but, besides the advantage of avoiding adding a <span> element (which, all concerned parties seem to agree will either not disturb, or be pretty easy to adjust their parsers for), there are a few drawbacks (in no particular order):

(*) To me, it feels unnatural to put something in the global stylesheet for such a specific, single use-case. (Though, I'm aware that that's mostly a matter of preference, and I do see some other used-just-once stuff in the stylesheet already. I guess, if I were building a new frontend for Bitcointalk from scratch, I'd probably be inclined to avoid inline styles and to observe stricter separation between content and presentation.)

(*) With this patch, there's no avoiding having to make a small change to Display.php and a small change to Display.template.php (with or without your CSS idea). So, involving the stylesheet would add a third patch-point. Needing 3 co-ordinating pieces for this feature to work makes things a little more fragile and complicated than they should be, I think. (I'm also inclined to believe that theymos is more likely to decide to sit down and review/merge a patch, when that patch involves no more components/changes than necessary.)

(*) When the "marker" is added this way (via a ::before pseudo-element), it forms part of the actual subject-line link (as opposed to sitting next to it in a sibling element), and so, when you hover over it, for example, it looks/responds like it's just some extra characters in the subject-line (which is undesirable for a few reasons, but, the main one, I guess, is that I don't want to introduce any unnecessary confusion around where the marker ends and the subject-line begins; if someone tries, for example, to artificially place the marker into their subject-line before posting, then I want there to be some semi-obvious difference between a genuine marker and a "fake" one). It also picks up the link's color (which lowers the contrast of the marker), and its opacity value ends up affecting a small part of the link's :hover text decoration, which looks kind of messy.

But, I believe the best approach is option A, (...) I would just add maybe a color change, or a different font size, to make this situation stand out more than just italics.

I've looked at a lot of hues by going around the color wheel in ~15 degree increments, and, maybe I'm just really picky, but they all look "wrong" to me in one way or another. What does end up working rather nicely, though, is making the subject-line black. Another thing that works pretty nicely is underlining the subject-line. Underlining also kind of makes sense semantically, in a weird way: Normally, you only see the subject-line underlined when you're about to click on it, but, in this context, you already have clicked on the link (otherwise you wouldn't be seeing it rendered differently to begin with).

Style C

This one just makes the subject-line link black.

Code:

--- baseline/Sources/Display.php	2011-02-07 16:45:09.000000000 +0000
+++ modified/Sources/Display.php	2024-04-04 00:02:44.000000000 +0000
@@ -230,24 +230,25 @@
 					SELECT COUNT(*)
 					FROM {$db_prefix}messages
 					WHERE ID_MSG < $virtual_msg
 						AND ID_TOPIC = $topic", __FILE__, __LINE__);
 				list ($context['start_from']) = mysql_fetch_row($request);
 				mysql_free_result($request);
 			}
 			
 			// We need to reverse the start as well in this case.
 			$_REQUEST['start'] = empty($options['view_newest_first']) ? $context['start_from'] : $topicinfo['numReplies'] - $context['start_from'];
 
 			$context['robot_no_index'] = true;
+			$context['requested_msg'] = $virtual_msg;
 		}
 	}
 
 	// Create a previous next string if the selected theme has it as a selected option.
 	$context['previous_next'] = $modSettings['enablePreviousNext'] ? '<a href="' . $scripturl . '?topic=' . $topic . '.0;prev_next=prev#new">' . $txt['previous_next_back'] . '</a> <a href="' . $scripturl . '?topic=' . $topic . '.0;prev_next=next#new">' . $txt['previous_next_forward'] . '</a>' : '';
 
 	// Check if spellchecking is both enabled and actually working. (for quick reply.)
 	$context['show_spellchecking'] = !empty($modSettings['enableSpellChecking']) && function_exists('pspell_new');
 
 	// Censor the title...
 	censorText($topicinfo['subject']);
 	$context['page_title'] = $topicinfo['subject'];

Code:

--- baseline/Themes/default/Display.template.php	2010-10-22 01:38:35.000000000 +0000
+++ modified/Themes/default/Display.template.php	2024-04-07 23:42:42.000000000 +0000
@@ -359,33 +359,34 @@
 					echo '
 								<a href="', $scripturl, '?action=pm;sa=send;u=', $message['member']['id'], '" title="', $message['member']['online']['label'], '">', $settings['use_image_buttons'] ? '<img src="' . $settings['images_url'] . '/im_' . ($message['member']['online']['is_online'] ? 'on' : 'off') . '.gif" alt="' . $message['member']['online']['label'] . '" border="0" />' : $message['member']['online']['label'], '</a>';
 			}
 		}
 		// Otherwise, show the guest's email.
 		elseif (empty($message['member']['hide_email']))
 			echo '
 								<br />
 								<br />
 								<a href="mailto:', $message['member']['email'], '">', ($settings['use_image_buttons'] ? '<img src="' . $settings['images_url'] . '/email_sm.gif" alt="' . $txt[69] . '" title="' . $txt[69] . '" border="0" />' : $txt[69]), '</a>';
 
 		// Done with the information about the poster... on to the post itself.
+		$is_requested_message = isset($context['requested_msg']) && $context['requested_msg'] == $message['id'];
 		echo '
 							</div>
 						</td>
 						<td valign="top" width="85%" height="100%">
 							<table width="100%" border="0"><tr>
 								<td valign="middle"><a href="', $message['href'], '"><img src="', $message['icon_url'] . '" alt="" border="0" /></a></td>
 								<td valign="middle">
 									<div style="font-weight: bold;" id="subject_', $message['id'], '">
-										<a href="', $message['href'], '">', $message['subject'], '</a>
+										<a ', $is_requested_message ? 'style="color: black;" ' : '', 'href="', $message['href'], '">', $message['subject'], '</a>
 									</div>';
 
 		// If this is the first post, (#0) just say when it was posted - otherwise give the reply #.
 		echo '
 									<div class="smalltext">&#171; <b>', !empty($message['counter']) ? $txt[146] . ' #' . $message['counter'] : '', ' ', $txt[30], ':</b> ', $message['time'], ' &#187;</div></td>
 								<td align="', !$context['right_to_left'] ? 'right' : 'left', '" valign="bottom" height="20" style="font-size: smaller;">';
 
 		// Can they reply? Have they turned on quick reply?
 		if ($context['can_reply'] && !empty($options['display_quick_reply']))
 			echo '
 					<a href="', $scripturl, '?action=post;quote=', $message['id'], ';topic=', $context['current_topic'], '.', $context['start'], ';num_replies=', $context['num_replies'], ';sesc=', $context['session_id'], '" onclick="doQuote(', $message['id'], ', \'', $context['session_id'], '\'); return false;">', $reply_button, '</a>';

Style D

This one puts a text-decoration: underline on the subject-line link.

Code:

--- baseline/Sources/Display.php	2011-02-07 16:45:09.000000000 +0000
+++ modified/Sources/Display.php	2024-04-04 00:02:44.000000000 +0000
@@ -230,24 +230,25 @@
 					SELECT COUNT(*)
 					FROM {$db_prefix}messages
 					WHERE ID_MSG < $virtual_msg
 						AND ID_TOPIC = $topic", __FILE__, __LINE__);
 				list ($context['start_from']) = mysql_fetch_row($request);
 				mysql_free_result($request);
 			}
 			
 			// We need to reverse the start as well in this case.
 			$_REQUEST['start'] = empty($options['view_newest_first']) ? $context['start_from'] : $topicinfo['numReplies'] - $context['start_from'];
 
 			$context['robot_no_index'] = true;
+			$context['requested_msg'] = $virtual_msg;
 		}
 	}
 
 	// Create a previous next string if the selected theme has it as a selected option.
 	$context['previous_next'] = $modSettings['enablePreviousNext'] ? '<a href="' . $scripturl . '?topic=' . $topic . '.0;prev_next=prev#new">' . $txt['previous_next_back'] . '</a> <a href="' . $scripturl . '?topic=' . $topic . '.0;prev_next=next#new">' . $txt['previous_next_forward'] . '</a>' : '';
 
 	// Check if spellchecking is both enabled and actually working. (for quick reply.)
 	$context['show_spellchecking'] = !empty($modSettings['enableSpellChecking']) && function_exists('pspell_new');
 
 	// Censor the title...
 	censorText($topicinfo['subject']);
 	$context['page_title'] = $topicinfo['subject'];

Code:

--- baseline/Themes/default/Display.template.php	2010-10-22 01:38:35.000000000 +0000
+++ modified/Themes/default/Display.template.php	2024-04-07 23:43:30.000000000 +0000
@@ -359,33 +359,34 @@
 					echo '
 								<a href="', $scripturl, '?action=pm;sa=send;u=', $message['member']['id'], '" title="', $message['member']['online']['label'], '">', $settings['use_image_buttons'] ? '<img src="' . $settings['images_url'] . '/im_' . ($message['member']['online']['is_online'] ? 'on' : 'off') . '.gif" alt="' . $message['member']['online']['label'] . '" border="0" />' : $message['member']['online']['label'], '</a>';
 			}
 		}
 		// Otherwise, show the guest's email.
 		elseif (empty($message['member']['hide_email']))
 			echo '
 								<br />
 								<br />
 								<a href="mailto:', $message['member']['email'], '">', ($settings['use_image_buttons'] ? '<img src="' . $settings['images_url'] . '/email_sm.gif" alt="' . $txt[69] . '" title="' . $txt[69] . '" border="0" />' : $txt[69]), '</a>';
 
 		// Done with the information about the poster... on to the post itself.
+		$is_requested_message = isset($context['requested_msg']) && $context['requested_msg'] == $message['id'];
 		echo '
 							</div>
 						</td>
 						<td valign="top" width="85%" height="100%">
 							<table width="100%" border="0"><tr>
 								<td valign="middle"><a href="', $message['href'], '"><img src="', $message['icon_url'] . '" alt="" border="0" /></a></td>
 								<td valign="middle">
 									<div style="font-weight: bold;" id="subject_', $message['id'], '">
-										<a href="', $message['href'], '">', $message['subject'], '</a>
+										<a ', $is_requested_message ? 'style="text-decoration: underline;" ' : '', 'href="', $message['href'], '">', $message['subject'], '</a>
 									</div>';
 
 		// If this is the first post, (#0) just say when it was posted - otherwise give the reply #.
 		echo '
 									<div class="smalltext">&#171; <b>', !empty($message['counter']) ? $txt[146] . ' #' . $message['counter'] : '', ' ', $txt[30], ':</b> ', $message['time'], ' &#187;</div></td>
 								<td align="', !$context['right_to_left'] ? 'right' : 'left', '" valign="bottom" height="20" style="font-size: smaller;">';
 
 		// Can they reply? Have they turned on quick reply?
 		if ($context['can_reply'] && !empty($options['display_quick_reply']))
 			echo '
 					<a href="', $scripturl, '?action=post;quote=', $message['id'], ';topic=', $context['current_topic'], '.', $context['start'], ';num_replies=', $context['num_replies'], ';sesc=', $context['session_id'], '" onclick="doQuote(', $message['id'], ', \'', $context['session_id'], '\'); return false;">', $reply_button, '</a>';

(The four styles are conceptually orthogonal: A = subject-in-italics, B = subject-with-graphical-prefix, C = subject-in-black, D = subject-underlined. A + D = in italics and underlined, D + B = underlined and with a graphical prefix, etc.; I think, if it were up to me, I might just go with C: it's nice and simple, with plenty of contrast, so it's really easy to pick out the "marked" post, and it still looks SMFish to my eyes. Though, for some types of color blindness, I can see other choices/combinations making sense.)

[TryNinja]

Style C

This one just makes the subject-line link black.

I like this one better, tbh.

No changes to the html tree and I personally find it easier to identify on the page.

[LoyceV]

I'm probably going to quote this out of context once in a while:

if I were building a new frontend for Bitcointalk from scratch

Good luck

[joker_josue]

Style C

This one just makes the subject-line link black.

I like this one better, tbh.

No changes to the html tree and I personally find it easier to identify on the page.

I agree too. I think this way is more efficient for what is proposed. And most importantly, it doesn't change the current structure, it's just a matter of layout.