Forum Replies Created
I’m also experiencing issues with both login and logout not showing the user being logged in in the top bar (even thouch caching for logged in users has been disabled). Has anyone been able to determine the optimal settings for buddypress + w3 total cache yet?
Allowing users to report spam would be a very useful feature. There’s only so much you can do in terms of technical spam prevention, and technical spam prevention always gets cracked eventually.
If the amount of spam reports for a certain account exceeds x, then freeze the account until an admin can review the account. The admin should then have the option to do an IP based ban of the account if it appears to be a spammer. Some very basic IP based messaging/commenting/posting rate limitation would help too.
Even more spam now, coming from this user: https://buddypress.org/community/members/joymab/
My vote goes towards adding a usability/interface design expert to the team. The work the programmers are doing on Buddypress is amazing and I am really impressed by the progress that’s being made, but a lot of functionality feels a bit clunky and unnecessarily complex to use. The design might feel logical and usable to more advanced users who work with computers a lot, but for those with less experience I can imagine it’s a different matter.
I think buddypress should be designed for the average user and not for the average programmer.
And the spamming continues. Anyone else getting spammed?
Got my second spam message as well. It seems to be affecting multiple BP installs so I think it should be a high priority to do something about it.
My vote is for a report spam button. When any action (activity, forum post, message etc) by a user is marked as spam, an admin should be notified. If more than x actions within x time of the user are marked a spam, the user account is locked until the admin is able to review the offending account.
Not sure if it’s been mentioned yet, but pagination at the bottom of the plugins page (https://buddypress.org/extend/plugins/) would be useful (right now it’s only at the top).
I’d like to second the points @gregfielding made. Besides that, I think overall it’s a pretty good design but might be somewhat confusing and overwhelming for newbies.
Yes, to clarify I do mean Facebook style media attachment from the textbox. I remember there was a large thread on the previous site with people looking for this functionality and some people mentioning that it was in development somewhere.
Just wanted to say I’m extremely impressed by the work being done on this plugin. Great job!
I know everyone is working extremely hard, but are there any updates on this featureset yet?
I’m a bit confused: what exactly is missing from the lifestream plugin that it is not suited for this purpose?
@Gpo1 That’s a great idea. Maybe they can work together with the MrMaz who already is working on a similar plugin that allows for not just photos but also other media attachments: https://buddypress.org/forums/topic/attachments-for-activity-items
@MrMaz How is the plugin coming along? If there’s any more developers interested in this plugin maybe they can join development.
@ruthlessbookie I think this will be a problem regardless of whether we allow people to pledge money towards a plugin. The pledges will merely be an extra incentive for developers who otherwise wouldn’t be compensated for all their efforts at all.
It’s a shame that the core implementation in BP forces you to use a twitter like @mention system for leaving comments on other people’s profiles. It’s not very user friendly for this specific purpose. One of the main reasons so many people that use twitter rely on third party software (connected through the twitter API) is to make the @mention system more manageable and usable, yet BP has this system as the only available option (and without third party applications to make it more usable).
The current BP system doesn’t allow you to use the two most popular and common methods of commenting onto the profile of a user. One method is directly posting a comment into a user’s activity stream (e.g. like on facebook), the other method is leaving a comment at a specific separate section (usually at the bottom) of a user profile. By far the most social networks use either the facebook or myspace style method for commenting on user profiles, and as such this is what most people are most familiar with. It’s a shame that the twitter based @mention system, which is relatively unpopular and quite difficult to use for this specific purpose, is the only available option in BP core.
Who else thinks that it would be a good idea to at least have the option to opt for alternate type profile commenting as part of the BP core system?
The cleanest solution for an invite plugin would be a plugin based on the open stack so people don’t have to share their password.
Does anybody know if open stack support is still planned? Maybe if enough people are interested we could pool together some funds to develop it as a plugin.
@Andy Sounds good I look forward to the new design. Have you considered integrating something like this: https://buddypress.org/forums/topic/idea-for-stimulating-plugin-development ?
@mlovelock Yeah it seems group functionality was pretty much disabled with the new site launch.
It used to be possible to join a group related to hiring devs on here but I think it’s been disabled starting with 1.2. You can still visit it here https://buddypress.org/groups/buddypress-job-board but I don’t think you can make any posts to it anymore. As an alternative you could look at sites like elance and getafreelancer.
Personally I think some sort of a buddypress devs jobs board along with a link to it at the developers section would be very useful for devs looking for jobs and buddypress users looking to hire.
@mentionsw I agree with your opinion that buddypress shouldn’t try to copy the Twitter model for user to user interaction. The Twitter design excels at some forms of user to user interaction but is incredibly awkward and difficult to use for doing something as simple as initiating and holding a conversation.
It’s no secret that the overwhelming majority of Twitter users stop tend to quickly stop participating in two-way conversations and instead become passive consumers of updates by a small group of very active twitter users. This is in a large part due to the fact that the twitter system is very unfriendly towards bidirectional user interaction. Even with a Twitter client it can be really easy to loose track of a conversation because @mentions are linked to the user instead of a specific tweet. Facebook and similarly designed services are vastly superior in this regard.
I don’t think buddypress should be copying the Twitter system while at the same time excluding the systems such as Facebook and Myspace which the large majority of people are accustomed with. Instead, the twitter system should be part of a system that gives buddypress users the option of different types of user to user interaction instead of forcing them to use one particular style.
On a side note, I don’t think this has anything to do with a generation gap between Twitter users and Facebook users. Sites like Twitter, Facebook, Myspace, Youtube all have different kinds of qualities that are suited to satisfy specific social needs of their respective users. For some needs people are more likely to use one network and for other needs people are more likely to use another network. Just because the Twitter system is relatively new and currently being hyped doesn’t make it superior to other systems.
@modemlooper It’s similar but it’s inconsistent and confusing for users. I have to agree with nickrita that this appears to be a case of ‘Verschlimmbesserung’. It makes it unnecessarily complex to do something as simple as to leave a comment on someone’s profile and continue a conversation from there.
If the user activity stream is really meant to be purely about activities of the user as Andy said, why are we able to leave replies that show up in the user activity stream? If this principle were to be applied consistently, the user should also not be able to post replies into a user activity stream (or at least they should not show up in the user activity stream but instead at the @mention subsection).
As a result of these inconsistencies we have we have this confusing hybrid of Twitter and Facebook. I really like the idea of @mentions as an added feature to the way users can interact, but it shouldn’t be the sole method of (semi-)public user to user interaction. One of the major weaknesses of Twitter (and one of the major reasons Twitter clients are so popular) is that it’s extremely difficult to initiate and keep track of (semi)-public conversations on their website. Just try using twitter.com to hold multiple conversations if you have a group of active friends on there, it’s extremely frustrating and labour intensive. Buddypress doesn’t have the luxury of anything that resembles twitter clients to cover up these kind of limitations that are inherent to the twitter system.
I feel that the current implementation of buddypress leaves these weaknesses of the design of the twitter system intact and even further exacerbates them by inconsistent application.
I therefore plead for a consistent design that allows users to post both messages and replies into a user activity stream regardless of whether it’s the site, group or user activity stream. This would take care of the issue of the missing wire while at the same time providing a consistent user interaction design for the activity streams across a buddypress site.
@motionsw What would you think of a system where a user would be able to leave a message directly on the page of the user at the activity stream, similar to the way Facebook does it (and consistent in design with how you can leave a message on the buddypress group & site activity streams with a textbox near the top)? Whether such a message would then turn up in the group & site activity stream would be handled by privacy settings.