Nathan Explosion

It's not a widget.
It's called "Topic Summary" on v4, "Topic Overview" in v5, and the settings for it are in the ACP via admin/?app=forums&module=forums&controller=settings&searchResult=forums_topic_activity_desktop

Add this to your theme's custom CSS:
li.cForumRow.ipsDataItem div.ipsType_richText { display:none; }  

Create a product in Commerce, put it in a group of its own in Commerce. Configure your badge rule to use the 'Member purchases a product' and filter on the group from above. Award the badge via the rule User purchases the product, user gets the badge.

No CSS/JS needed, as you'll find that the following editor setting dictates whether a 'gap' appears between the quote and the content:

 
"Start new paragraph"

"Go to next line"

 

use the search and type "post"

Yes

Have you tried /* yet?

Don't copy/paste the URL - instead, add it as an attachment "again" using the option indicated

@David.. I know you indicated you had uninstalled the resource, but if you are still using my application then you should turn off the "Show 'Rare' tag on badge?" settings that are available in the application settings. When generating the html for a badge using IPS code, this setting will result in a call to the 'isRare' function in \IPS\core\Achievements\Badge, which itself calls getBadgeStats, so if you are viewing a topic where a number of people are displaying badges then it could trigger the situation mentioned in that other topic if the cached data has expired - I'll be adding something to my application to warn about this behaviour.
Also - if you ever need my assistance to check an issue with my resources then contact me on the site from which you downloaded the resource. I'm no longer on here regularly, so mentioning me isn't going to achieve much. Report on my own site = I see it.
If anyone else wants to try to reproduce multiple calls to the getBadgeStats function, then it can be done by going to a user profile for someone who has rare badges, and then refreshing multiple times at the same time as the expiry of the cached stats.

Recommend the post that is considered to be the currently correct one?
Result - it's at the top of each page..

Ensure site working as-is on 7.4 Disable any non-IPS plugins/applications that you may have installed Turn site offline via ACP Switch PHP version to 8.0 or 8.1 - site will stop working Run this https://invisioncommunity.com/files/file/7046-invision-community-requirements-checker/ and fix any issues Download update from client area, upload it to your site via FTP Go to /admin/upgrade manually

Just run a search, with NO parameters..accept the defaults.
And then when you see the results, click on the Spammers filter.

Edit the highlighted template (ideally, edit your own version of the default templates)

 
Find this line:
{{foreach $record->comments( NULL, NULL, 'date', 'asc', NULL, NULL, NULL, NULL, FALSE, isset( \IPS\Request::i()->showDeleted ) ) as $comment}} Change 'asc' to 'desc' and save.

With all patches applied? There was one specifically for this issue, so check the support page in the ACP to see if any patches are waiting to be installed.

<script> alert("{expression="\IPS\Member::loggedIn()->email"}"); </script>  

Like that? If so, it's probably simply a case of them quoting the content then copying the quote and pasting into an existing quote...and rinse/repeat.
Quoting works the way you see it - 1 level. But there are ways around it, as mentioned.

https://invisioncommunity.com/clientarea/

Where's that? Happy to be blind on this one.
Anyway...simply change the "Available for..." field so that it's only available to those you want to see it:

You pay for a new license, and then the renewals.

Go into the ACP and type delete into the search bar and click on the Permanently delete content result.

That isn't obfuscation.
That is an ipV6 address

OK.
But it's likely to be that has happened
All registrations go through the spam prevention settings, and depending on your configuration then an admin may need to validate the account.

Apply the patch that was released to fix this: