Forum Replies Created
And let’s drop this bitterness. Let time take its course, as it has. This too shall pass.
Id be careful making claims like that if I were you. Theres easily viewable proof that we were using the name BuddyPress Media over two years before you started using the name BuddyPress Media.
I’m very careful when I make such claims. Just because we were smaller then, we didn’t use GitHub or a public repository for releasing our under-development code. We were of the opinion then that we must create a basic usable version and start on WordPress.org plugin repository. When we submitted the first very minimal version, we weren’t aware of the GSOC project till WPMU wrote a blog post about it.
A long long time ago we were a small dev shop from India as @foxly has said somewhere. However, over a period of time, we’ve evolved and how.
2012-09-07 – rtCamp users begin posting help requests for rtCamps plugin on the BP-Media team’s Google Code page. We help them anyway.
That was so nice of you. Thanks for that!
2013-01-05 – BP-Media publicly invites rtCamp to join the BP-Media development team. They decline.
This was for a very obvious reason. The way we deal with our users is diametrically opposite to yours. We want a leaner, lighter and tightly integrated with WordPress plugin. You want a plugin that has minimal dependency on WordPress or BuddyPress. We want to release features as and when they are finished. You want to release everything, at once.
Then rtCamp flooded the keyword search by tagging all their posts with bp-media, and then rtCamp started claiming they were the BuddyPress Media dev team.
Come on man!
but instead I had to spend half of it dealing with other plugin developers trashing my team on the forums
In open-source, the best strategy is NOT to compete, it is to work together. If the ten thousand developers that have made large contributions to Linux had tried to create ten thousand different operating systems instead of working together to build something awesome, the Internet as we know it probably wouldnt exist.
True that. Let’s merge WordPress, Drupal, Joomla and all other popular CMSes and create this superhero CMS. Let’s merge BuddyPress, elgg, Social Engine into one and have the best social networking solution.
A problem can be solved in fundametally different ways. That’s why in the open source or anywhere else, you have different products.
Back to development, let us go.
Twitter: @buddypressmedia @rtcamp
When we submitted the plugin to the WordPress repository, if there would’ve been a problem with the name, we would’ve been told so. So, I don’t feel that was the issue here.
The second BuddyPress Media has never been released, officially. BP-Album was released after BuddyPress Media. General common sense dictates that if you have an existing plugin by the same name, you go ahead and change the name. We all do that. It’s obvious that otherwise the users will get confused and all three parties lose out, both the development teams and users. Which is what just happened here.
Which plugin is a better plugin is always open to discussions and enquiry. That’s competition and it brings out the best from the competitors for the users. Win win. Utopia.
As far as naming hoopla is concerned, even if we are asked to remove BuddyPress from the name, ever, we have no qualms rechristening. However, it needs to be official.
So, let’s lay this discussion to rest. I invite all of you to come see what we’ve built. It’s not perfect. Its not ideal. It does what it promises amd does it well. It is evolving fast, becoming less buggy, faster, prettier and more accessible with time. Most importantly, we talk to our users and listen to them.
We might interest you.
If you do check it out, BuddyPress Media is a media manager adding and abetting users’ community experience.
Users get to upload images into multiple albums that they are free to create, edit or delete. BP-album, as it stands, creates a My Pictures album where users upload their pictures.
BuddyPress Media goes a step ahead and allows users to upload videos amd audio, as well. Then it goes ahead and plays the audio and media with an html5 video player that falls back on flash & silverlight.
The uploader is the default WordPress uploader. When a user uploads media, activities are created.
All this is available at the group level, as well.
The only other thing that BP-album does is allow users to set privacy levels of each image. This is currently under development at BuddyPress Media along with the ability to upload media directly from the activity stream.
All the media can be favourited and commented upon.
All this is free and open source.
The premium addons that we sell, perform an extra task. On a capable server, we enable users to uplaod videos and audio in any format and convert these to standard mp3 and mp4 formats.
The comparison stands verifiable by a single install.
The project is hosted on github http://github.com/rtCamp/buddypress-media for anybody to extend it any way they feel like. In fact, someone can possibly create free alternatives to our premium offerings, using all the free and open source code. That’s how transparent it is.
The deductions are yours to make.
I don’t think that’s how it is. However, in any case, the name of the plugin matters only to a certain extent. I’m sure users value functionality, accessibility, attentive ears more than whether a plugin is named in a certain manner.
So, we wouldn’t be bothered by such an issue. We shall cross the bridges when they arrive.
I agree, when the plugin was developed initially, it was just a port between BuddyPress and Kaltura. However, subsequently, it evolved into an independent user media manager and we separated the Kaltura port into a paid addon.
However, I’m here with news about the BP-Album successor. The team got so irritated by the constant confusion that they’ve removed all their code and hidden it in a top secret place and are getting a secret name copyrighted. They are then going to create the associated usernames and other handles of their social media machinery.
After that they’ll be releasing it as a surprise with a bang to their users. I’ve heard it from @foxly here:
It did anger us, but I personally find this whole BuddyPress Media vs BP-Media business very oddly humorous. I don’t see such conversations usually!
@Hugo I agree. A media manager for BuddyPress will logically be called BuddyPress Media. And that is why when we started off, our plugin was called BuddyPress Media.
After this happened, BP-Album developers also decided to expand BP-Album into a higher realm and for some reason decided to disregard the fact that a plugin by that name, already exists.
Also, for various reasons, some beyond my comprehension, it was a more vocal and more popularly discussed plugin, compared to the original BuddyPress Media that we were steadily developing.
With time, our work has been rewarded on a good scale and helped us improve the functionality, fix bugs quickly thanks to our users and bundle a couple of languages. Our development has been very transparent and accessible for users who have been talking to us, fortunately, throughout.
But that’s enough of blowing our own trumpet. We’ve been getting repeated user requests for an importer for BP-Album and with this new development, we will push this higher on our priority than it was.
Yes, this was a small bug in the code. Which is why it displayed a warning, in some versions of PHP.
Due to this bug, all that happened was that the BuddyPress Media menu in the admin bar did not get displayed. We are in the process of adding an option to enable/disable this menu. That’s when the bug crept in.
You don’t have to delete a plugin for that. We apologise if it caused you any inconvenience. We’ve released a fix for this just now (2.5.2).
@mercime BP-Album has been out of production for a long time now and throws more warnings than any plugin I’ve seen in recent times.
The second namesake BuddyPress Media’s team has removed the GitHub repos, removed the svn repo on code.google.com and generally been off the scene for a while. I have no idea and no news of why that is! We were looking forward to the launch and gearing up for some good old-fashioned competition.
I am one of the developers for BuddyPress Media. We hadn’t had any plans for an importer till some time ago. However, since users have been asking for it, we’ll add this soon.
You can follow the discussions and progress here: https://github.com/rtCamp/buddypress-media/issues/152
I am from the team that develops BuddyPress Media. Like @shanebp says, the rotation data is stored in the exif data. Generally, most devices that can detect their orientation correctly assign the data. So, when storing or uploading, things remain normal. However, older devices and iOS don’t do this and images and videos are displayed with awkward rotations.
Ideally, a browser should be able to detect this and automatically correct the rotation. However, (surprise, surprise) only Internet Explorer 10 does this.
We are working on this and there is an open issue here: https://github.com/rtCamp/buddypress-media/issues/118
We plan to fix this at least with BuddyPress Media, soon!
Seems like you gave up on BuddyPress. Apologies, if we had a hand in it.
Sorry! Never received this reply in my mailbox and because we’ve been terribly busy over the holidays, didn’t return to this forum.
I’ll check things today and revert, asap.
I’m registered here: http://justbefamous.com/members/saurabh/
I guess, I don’t have the permission to upload images. Could you check my permissions?
Yes, I logged in via facebook. The other way is too cumbersome, in comparison.
Nevertheless, just try how it goes with the default buddypress theme, once. It is way beyond our business hours (about 10 pm), so I’d only be able to check it in the morning, tomorrow, along with the team. We’ll register via the standard form, then.
We haven’t experienced this before. I tried registering on your site, but it asks for an activation to acess buddypress.
What happens if you switch to the default theme? At times, themes using non standard ways of using js are known to interfere with our functionality.
The group media functionality is very new and introduced in just 2.3. Hence, there is just the bare minimum functionality. Could you add this as a feature request on our github repo here: https://github.com/rtCamp/buddypress-media/issues.
As of now, they would just have to copy paste the url, which sucks frankly. We are not sure how to link the users’ uploads in a group to their profiles or activities. We have multiple ideas but can’t zero in on ‘the’ one.
Any ideas you’d have are most welcome.
@foxly Ha, ha! You are a clever one.
3 reasons why that can’t be done:
1. Our vision for the plugin is pretty much in contrast to yours, won’t work nice.
2. We bake our own bread, we eat our own dog food! What we write is closely tied with what we need, too.
3. If we compete instead, both the teams will be forced to outdo each other. That equals to two very good plugins, two options for users, two alternative ways of doing similar things. That’ll work out well for all of us, including users, I believe.
That being said, we are a commercial organisation (rtCamp Solutions Pvt Ltd) and such community projects satisfy our vested interests:
* of giving back to the community that helps us earn our bread (and butter ),
* interaction with the community,
* developing our skills and knowledge.
I don’t think, we can give that up, easily. Best of luck for your plugin, though!
Discovered this conversation just now. I’m from the team that develops buddypress media mentioned by @rickkumar.
Now, I’m not getting into the comparison game. Our plugin is not thoroughly tested, till now. We decided to get our hands dirty, early, so we could use user feedback and community involvement, faster.
Now that our plugin’s vision is getting aligned with real users, we are in the process of restructuring. Ours is much smaller in size and doesn’t boast of a host of features or an amazing ui. But, it is out there, available and being improved upon continuously, with live user feedback.
You can see this evolution in our support forums http://rtcamp.com/support/forum/buddypress-media/, http://wordpress.org/support/plugin/buddypress-media and on github https://github.com/rtCamp/buddypress-media/issues .
It does everything it promises to do, manage media and it does it well. The roadmap is present here: https://rtcamp.com/buddypress-media/roadmap/. Won’t comment on the other plugin. I’m already intruding.
Now as for the error, the WordPress explanation cited by @modemlooper, is fairly simple and straightforward. When there is no filtering needed, a function like wpdp_prepare must fail. So WordPress is just putting things right. It broke our code, but we spent a little time doing find and replace for the function and corrected it.
@foxly can’t really disagree with your emotion. Often been tempted to go that way, decrease the dependency on WordPress. However, for the sake of lightness and tight functionality, and because that helps us debug the cores, WordPress and BuddyPress, themselves, we’ve stuck to using default wp functionality for as much as possible.
I hope that helps this conversation.