I think it’s using permalink.php in member/single/activity
IMHO – it’s the most useless page in the standard BuddyPress set up, serving only to look bad and frustrate users who are expecting to see some “added value” when they click on the view link for a status update.
Perhaps there’s a good use for it?
I agree with both of you, and also would like to know any ideas for giving this template a better use.
Even on THIS site they have removed the permalink and it re directs you. I agree, useless page.
Nah, since I won’t allow separate blogs (and I’m running a single user WP) my users can use the update for blog type posts. Then if you click view, all the comments will be there too. This is useful in that when you filter by updates, you get all the ‘blog posts’ they’ve made and can use the permalink for linking others to that particular post.
@lunakm – You see all the comments in the activity stream anyway… but, ok… having the link to give someone is useful in your use case.
Part of the annoyance, is that the view link is there by default, gives a poor user experience, is useless 99% of time, and difficult to remove (it’s not as simple as an edit in a template file).
Keeping the permalink page is fine, but the view link to it probably shouldn’t be included as part of the default long activity header string that’s generated by the core activity files.
i.e. the view link should be opt-in, not ‘re-implement’ a core function (or write a ‘very clever’ string parsing filter) if you want to remove it
I would say this is one of the issues that is frustrating for frontend developers that some ‘things’ require disproportionate effort to effect change, The view link mentioned one of those, there is a limit to the very clever string parsing filters I’m prepared to write to make a link disappear 
@hnla – yes, a lot of the ‘disproportionates’ probably just need the API / template tags stripping back to something finer grained. Leaving the control on string building, content and presentation in the front end templates.
Exactly, but I’ve aired my views on this subject before, revisiting the API is something that requires doing at some point .
