Forum Replies Created
-
The new form of parent detection is RAD. I’ve been waiting for this.
Okay, I’m fairly certain this one is resolved, but I’m going to leave it open for a while to see if anyone else has different input.
My answer, ultimately was to just use MAMP. It’s running great so far.
UPDATE:
For the svn:externals, I found informative help here:
http://www.chapter31.com/2008/05/22/setting-up-svnexternals-with-subclipse/
and
http://www.thecrumb.com/2008/02/22/svnexternals-setting-in-cfeclipsesubclipse/
I think this is a no-brainer *as long as it doesn’t make life more difficult for the average user.*
I really do like the re-theme, Andy. I hate to say it, but the previous them took up so much real estate on the screen, and the way panels and columns were laid out was pretty difficult to manage with css for making changes in child themes, for example.
I’m not going to fuss right now since I already built a child them off the parent (see arxpoetica.com), but one of these days I’ll convert over.
My two cents about IE6, people *really should* be scrapping as much as possible. It’s true that there’s still a substantial amount of people on IE6, and I’m not a hater (well, that’s not entirely true, I do hate IE6, ha), but when there are so much better alternatives to IE6, why continue to support something which, in terms of technology, is 90 years old. (I’m using dog years analogy here: the lifespan of technology is much shorter than humans, so you gotta adjust accordingly).
IE6 is on its last breath, no question.
The other thing is that BuddyPress *is* cutting edge, and I imagine people (maybe not the core team, but plugins developers) are going to start folding in HTML5 technology soon to what’s going down here. I know I plan on using such for my site in the not-too-distant future, and while IE is not HTML5 friendly period, and many browsers still have problems, IE6 is just out right the bane.
People need to realize that its support for IE6 is no longer a normal request. It *should* be a thing of the past, IMHO.
</rant>
Word. Patch it!
I’ve been having sign up spams (arguably a different issue) on my BP install, and just shut all signups down until I could figure out what to do about it.
Scouring the WordPress MU forums has made me realize three things:
1. Spamming is a huge problem for WordPress MU users
2. I’m betting that BuddyPress will/might have even larger problems due to the very nature of the beast (it’s all about users, right? Which is where the bots/spammers gravitate)
3. There are no sure-fire methods for preventing spammers
…well, there’s a fourth, too…
4. Many of the old hats on the WordPress MU forums are getting tired of explaining how to defend against so-called “splog” signup bots and spammers.
Just some observations, as BP just received its first official spammer. (Yes, I got the email too, and saw the small twitter firestorm this morning over it.)
Oh, I failed to mention Will Norris, who already wrote an OpenID plugin for WordPress, which works pretty good, but seems to be missing a few key features.
There’s some talk of integrating OpenID into the core of WP, but there’s also disagreement on this. With BuddyPress putting it on the iteration roadmap, this may change people’s minds in the long run as they realize how Identity *IS* the platform (the core) of the Internet.
Waclaw — I’ve started working on a jQuery plugin for distributed social networks (the social stack). One thing that’s needed is a process for “discovery.” There are several solutions already out there implementing various kinds of things along this line, but nothing quite like what you’re calling for.
Go look up Chris Messina, Luke Shepard and David Recordon (Facebook), Joseph Smarr and John McCrea (both Plaxo). They’re all advocating this type of stuff.
(You can watch them here: http://thesocialweb.tv/ ) (hasn’t been active in a little while, though, but look at the archives)
Anyway, I think I’ve seen you in the dev chat, so maybe I’ll talk to you there too, when time permits. There’s much to say on this, and I’m hoping to do some good legwork on getting things ready. While I don’t have *only* BuddyPress in mind as the platform, it is the most interesting platform (and viable) at the moment.
Trying to figure out the same thing…
I think the comparison, in that case, would be wordpress vs. drupal, and then drupal social vs. buddypress…
Nice. Just what I need about right now.
Sorry for being a little slow on this topic, but activity streams are hard to wrap my mind around, mostly because I don’t quite get the technology. Does openmicroblogging — is this a viable part of Joseph Smarr’s so-called “social stack”? (I think they’ve moved on to calling it something else now, not “social stack,” but I digress…)
I’ll be building a version of a micro stream soon enough, or trying to adapt a former one (such as the “wire”?) to suit my own purposes.
As I understand it, there’s already a bit of a WordPress plugin:
Why rebuild the wheel, when it’s built? Perhaps we should borrow/resuse from that plugin
There’s a bit of development/discussion going on over here for WordPress itself:
http://groups.google.com/group/diso-project/browse_thread/thread/84481ef2e912a099
http://groups.google.com/group/diso-project/browse_thread/thread/b9f1b8865d3d8526
Regarding who is responsible for data, it seems there is a lot of misunderstanding about OpenID out there. I’m not the ultimate evangelist on all this, but 90% of these types of concerns have already been addressed by the real know-hows of distributed social networking.
OpenID does *not* mean everyone has access to everything. Rather, it just becomes a viable way to port information, when necessary or desired, more easily, as well as providing a way for an individual to be identified more easily at any given site — but, again, this doesn’t preclude telling every site everything. Trust is still a site by site variable.
Here’s a list of great reads (plus a web “TV” show!) for those interested in understanding what’s true and what isn’t:
http://factoryjoe.com/blog/page/12/ (old, but addresses some common concerns)
http://josephsmarr.com/2008/04/23/data-portability-privacy-and-the-emergence-of-the-social-web-web-20-expo/ (also old, but an original “diso” reference”)
http://www.sociallipstick.com/2009/03/a-proposal-for-a-conceptual-open-stack/ (social stack reworked)
http://factoryjoe.com/blog/2009/02/13/this-week-in-video-facebook-and-the-openid-design-workshop/ (a bunch of videos from the OpenID Summit)
http://thesocialweb.tv/ (periodic episodes updating the latest in diso)
The final thing I would add is, like it or not, distributed social networking (OpenID and the like) are _already_ here: Google, Facebook, Yahoo!, AOL, MySpace, and a host of other providers have already embraced OpenID, and the clock can’t be turned back. There are still a lot of variables to be worked out (such as “single sign out”!), but BuddyPress would do well to support it, if not because it is a highly useful technology, then at least to support the percentage of customers who are going to want (demand?) the technology.
Anyway, back to RPX and BuddyPress…
Just to address JohnJamesJacoby’s first concern, that’s not how OpenID works. “Sniffing” ain’t allowed. Authentication takes place *not* on the new site, but on the old site, i.e., Google or Facebook, and the *only* thing the new site is getting in terms of authentication is an oAuth token saying “Google says you’re good, so I’m going to authenticate you, using Google’s token and whatever other information you and Google have chosen to give me.”
That means the new site gets NO password.
ZERO.
ZILCH.
Now porting other data, and concerns over privacy with regards to that? Well, it’s not using Google or Facebook’s data, it’s *porting* it, so, yes, I can see privacy concerns cropping up all over the place with that, and it is a little Wild West right now.
But that will get better over time. Somebody will think of a way to better secure your data, etc.
Incidentally the OLD way for porting data *did* have the new site capture your password, i.e., to import friends on Facebook, you had to enter your email and password for, say, gmail, and then trust that Facebook wouldn’t keep it but would only scrape the data from gmail *one time*…THAT is dangerous, and, thankfully, OpenID and oAuth (distributed social networking) is doing away with that bad practice.
Incidentally, I did just implement RPX on my local copy of BuddyPress.
Totally works. Very cool.
I’ll let you know when I figure out how to transfer the RPX functionality to a main page.
So has anyone seen Gigya Socialize yet? http://www.gigya.com/public/Content/GS/Home.aspx
Same idea/principle as RPX, only a little more integrated. They have a WordPress plugin, but I can’t seem to get it working on MU, at least not my local copy (which may be the problem).
BuddyPress *really* ought to have the implementation of the “social stack” as high priority, even though much of the specs on what that all entails is still being ironed out.
But with Facebook, Google, MySpace, Yahoo, etc. all embracing OpenID, you can see where this is all headed. (Joseph Smarr calls it a “sea change”: http://therealmccrea.com/2009/04/10/surviving-thriving-in-the-online-identity-wars-joseph-smarr-at-web-20-expo/
Anyway, I’m going to be trying to implement one of these OpenID signin authenticators, and get it working from the main page. I’ll try and remember to report if I learn anything or get it working.
