This is not a bug, this is the members unique Ning ID. A members username can change over time, but the Ning ID does not change. You can find the mapping between Ning ID's and usernames using a REST request of the members profile.
Thanks Devin! I did understand it is the user id. But the actual user name should be returned, not an id #. The entire XML feel is returned. We would have to parse the entire file, grab the ids, replace them, ouch ouch.
That was the bug, user "id" returned rather than "username" as in any feed.
Sorry for the wait! I realized that rather than getting the blog posts from the REST endpoint, you could use your networks generated RSS feeds. These feeds contain the translated member ID.
on a private network we may want to use REST to create a feed so the whole world won't know how to get the feed. the built in fails on privates, which is as desired.
but, WOW, no feed anywhere on the planet puts a user ID instead of a human's name. There are obviously a few lines of code missing that would take the ID# and replace with the string.
I'm sure if this was pointed out they'd see that flaw. there could be no reason anyone would want the ID# and have to re-parse the entire output. right?