I see with the sessions that it would be an interesting thing to overcome. I'll leave these here...
Because I like to know when thread 'x' is going to get knocked off profile...
$('.thread-plate__post-by-user').each(function (i, e) { $(this).append("<br/>#" + (i + 1)); });
Maximum threads is 200, sometimes max visible in profile is 197...
var totalThreads = $( '.thread-plate__post-by-user:last-child' ).length;
if ( totalThreads === 1 ) {
$( '<span>' ).text( ' | This profile has ' ).attr( 'id', 'user-thread-total' ).append( $( '<strong>' ).text( totalThreads + ' thread' ) ).insertAfter('.user-post-count > strong');
}
else {
$( '<span>' ).text( ' | This profile has ' ).attr( 'id', 'user-thread-total' ).append( $( '<strong>' ).text( totalThreads + ' threads' ) ).insertAfter('.user-post-count > strong');
}
Because you can still save up to 300 characters in signatures...
$( '.reply-box__area--signature' ).attr( 'maxlength', 300 );
var s1 = $( '.reply-box__area--signature' ).text();
if ( $('.signature-box__title')[0] ) { var s2 = document.getElementById( 'reply-box__area' ).value = s1; }
In relation to permissions, that's nice and I did not know that Chrome allowed optional allowances towards extensions. Always thought that they were a blanket set.