I tagged you as followed yesterday evening, and this exposed a very non-standard referencing of your MyTPM Blog space.

In Edit Profile, your Username gets fixed at account creation, but your are allowed to change your display name at will.

The Username is also the name of the server file folder, that points to your TPM account Homepage, with two small qualifications: 1) All upper caps are converted to lower caps; and 2) If your Username has spaces in it, they get converted to underscores.

Now here's where your account's weirdness is. Your posted comments get published under display name "starwalker", and the pointer to your account home page is "mox", yet when I navigate to your folder clicking of the starwalker link, I end up on a page that lists your display name as "Mox", not "starwalker". This ain't right. I tried linking to a starwalker folder, but was unsuccessful, so the problem isn't two separate folders that share partially overlapping links.

Try to change your display name to starwalker in "edit profile", then log-off your account, clear browser cookies, as well as browser cache, and then log-on to your account, and see if that fixed anything.

Justice, let bwak help you with Apple problems. I've never played around with Apple computers extensively. It isn't about being a MS or Linux fanboi. Truthfully, Apple is probably a better system for many common desktop tasks. It seems to handle media creation and editing with less hassle than Windows.

I took an alarm clock apart when I was four, and with screwdriver still in hand, suddenly got very curious about what was behind electrical wall plates. This caused my parents to amke the wise decision of putting all hand-tools in locations too high for me to reach. I still have that kind of curiosity, and like to pokemy hands inside of computer cases. I'm often tinkering with hardware and settings, and less frequently switching out hardware. Apple's marketing strategy of proprietary hardware greatly reduces the number of options available when playing with Apple computers' hardware.

Bwak's OS of choice is Apple, and is familiar with many of the usual issues that arise when browsing the internet using one.

CVille, there are hacks and trick to get around this issue, but as Bwak noted, this involves interfering with the methods used for monetizing TPM, and they do need, as well as deserve, to earn money for their work here. that reason, I am loath to publish instructions publicly. I thought I had an eamil pointer for you, but was unable to locate it just now in my address book. If you want to discuss this privately in emails:

pdsa
at
impietease
dot
com

is presently a very good address for doing it, as it's lightly used, seldom spammed, and checked at least once a day.

I am amused to learn you are getting targeted ad-served content meant for persons who are overweight, because I do not recall seeing them very frequently, and even though I'm about as likely to click through an online ad that is pitching magical weight-loss for people who just cannot get up off of their asses and take a walk now and then, as you are; I'm sized a bit bigger than the average adult male, and do have a few unnecessary extra accessories added on.

This deserves it's own category. I think, "Web 2.0 Missing The Targeted Ad-Served Content Provider Failure" is an appropriate tag.

From where I'm sitting right now, that should be OwrrrrwrrROOOOOARRRRRR!

Ah. Thank you Bobby.

Eds, let me know if I went over your head with html geekalese here. I'll try to be clear.

In my experience the double-space problem in blogs and comments is resultant from how normal line breaks in text have extra html tags added to them before being published at TPM. One linebreak gets a normal html linebreak added:
<br />
Two linebreaks gets marked up as a paragraph break:
</p><p>

Here's where it might get a little tough to understand. Whenever a blog or comment has a block-level html tag inserted, linebreaks in the text still get the aforementioned html tags inserted before being published. The most common one would be a blockquote:
<blockquote></blockquote>
but any ordered or unordered list is also a block level tag.

Here's my personal rules when using those two tags at TPM.

Blockquote:
before the quote, 2-linebreaks;
after the quote, 1-linebreak.

Lists:
before the list, 1 linebreak
strip all linebreaks out of the list code
after the list, no linebreak, continue on the same line as the list.

What Rowan mentioned about word processor programs is also very significant. Most modern word processor programs in all major desktop OS flavors, have incorporated into them, a Rich Text functionality, that was once found only within Windows programs. Rich Text was a wonderful idea, and is able to greatly reduce the effort needed to complete many editing chores, which require transferring data between two separate programs. Very few end-users understand how it works though, and for this reason, Rich Text can be evil. When a blog post has been first composed in a word processor, and then copy/pasted over into the default Rich Text Format setting of the TPM blog editor, it gets pasted as HTML, but not just any HTML. Word processors are extremely literal in their formatting instructions, and the format styling when exporting it as HTML is extremely convoluted to anyone who is comfortable using normal, simple HTML tags. It is rigid, and often does display fluidly across different machines. It's fine and dandy when printing out a hardcopy, hitting the margins perfectly, with fonts sized just the way you want 'em, but code designed to be viewed in browsers needs to be formatted as relative, not rigid. This is why current best practises web coding involves the use of relative measurements instead of fixed. Instead of a font-size being a specific number of points, it is scaled as a multiplier of the user's normal screen font-size. Instead of margins being set in points or inches, they are often set as a percentage of the total screensize. This way the display of these files will be acceptably consistent across all browsers and screen resolutions.

Additionally, a word processor's extra style formatting can easily conflict with TPM's own site-wide style formatting, really messing things up. The easiest work-around for this is to set the TPM blog editor Format selection to "Convert Line Breaks". This precludes anything being pasted into as Rich Text.

I;ve never had problems with my profile being updated after I edit it, although I can understand why it may seem uncertain if it completed properly at first, because it takes a while for some things to show up the site.(like your avatar picture)

the most/recent commented threads widget and the private messaging system are not thing i can help with, because I am only a site member like you, not administration. Site administrators sometimes start thread asking for members' comments about the site. That woeld be the best place to request functionality not currently available.

Although Private Messaging on a site like this can be abused, it would be very nice to be able to pass an email address to another member without having to dick around with the way it's formatted out, hoping that the member can decipher it, and the spammer email harvesting bots cannot.