Podcast: Play in new window | Download
| 03:38 |
News: WordPress.com goes over 1 million blogs WordPress.com recently saw the creation of their millionth blog. That’s exceptional growth by anyone’s standard, and congratulations go out to everyone at Automattic for working so hard to make WordPress.com the success that it is. |
| 06:22 |
News: Movable Type 4 (re)embraces Open Source SixApart recently announced that Movable Type 4 will be Open Source Software and released under GPL, yet they’ll charge for it?! Aaron and I agree that this is too little, too late for the WordPress predecessor. |
| 12:32 |
News: Unless you’re running WordPress 2.2 or 2.0.10, your blog is vulnerable! Aaron recently reacted to an unscientific survey with his own unscientific survey, finding that most blogs are behind on updating their installations of WordPress to the most recent version, making their blogs extremely vulnerable to attack or hijacking. |
| 18:14 |
News: WordCamp San Francisco 2007 is nearing and appears to lack organization Matt Mullenweg may have wanted WordCamps organized all over the world, but Aaron and I would settle for the one actually being organized. A little more than a month away, and there’s no R.S.V.P. list or agenda. As much as we appreciate Automattic organizing the conference, we’re voicing the concerns of a lot of people when we voice our frustrations over the seeming lack of organization and advance information.We also talked about our plans to hold a session on podcasting and record an episode there. |
| 27:19 |
News: Weblog Tools Collection holds 2nd Annual Plug-In Competition and Sandbox Design Competition One of our favorite blogging tools sources, Weblog Tools Collection, has begun running two competitions nearly concurrently. The 2nd annual competition for WordPress plug-ins ends July 31st and features some nifty prizes, and the Sandbox Design Competition makes its first appearance, ends 12:00 AM (GMT), Sunday, July 29, 2007 and offers some nice chucks o’change. |
| 32:30 |
Feedback, comments and questions:
|
Pingback: Living in the Whine Country » Archive » Where is the Wordcamp 2007 information blasts?
I agree with Jerald’s correction on the term “ripped off.” Yes, you can’t get ripped off under GPL. And, I understand that by releasing something under GPL, I’m exposing myself to that possibility.
I should be okay with all derivatives of my designs and I’m trying hard to be…okay :).
However, when “theme modifiers” make no real effort to contribute something new and hide behind “taking the high road” to re-release a modified version in order to benefit off of it, I can’t help feeling… ripped-off. If there’s a technically correct term out there with the same connotation then please let me know. I’ll start using that instead of ripped-off.
You can argue all day about what terms to use. But, isn’t it obvious that the term ripped-off has to do with ethics? On paper or by the license’s rules, being okay with all derivatives is what GPL is about, but I doubt that anyone would purposely put in countless hours to get their stuff taken advantage of in a ripped-off way, regardless if you’re a designer or coder.
And because of that belief, I don’t agree that voicing my opinions about rip-offs or even trying to discourage such behavior is hypocritical or means that I’m not fit for GPL.
If I’m wrong then maybe Aaron is right :). Maybe I’m not fit for GPL, but I doubt that many designers are fit for this license (I’m just one of the few that voice my opinions) because it’s easier to get your design “ripped-off” than to get your codes ripped-off. Before I dig myself another hole here, I meant it’s easier to recognize a rip-off design than to recognize rip-off source codes.
And, it’s easy to say maybe you’re not fit for this license. Even if that’s true, what else can I do?
I want to contribute just like everyone else. But no matter what license I release under, my designs are going to be copied, modified, or ripped-off anyway. If that’s the case then why limit the usage of my work for everyone else because of some bad apples?
Maybe I’m unfit for GPL, but GPL fits me or… my situation, perfectly.
About the Youtube Comments plugin, Youtube API doesn’t provide authentication of videos. I can do a simple check in the code but you know, it can be easily *cough* h*ck*d :)
One note. The Weblog Tools Collection is not hosting/sponsoring the Sandbox Designs Competition. Mark was gracious enough to allow me to post the initial announcement there. Hoorah, Mark.
It’s been sponsored by a few different folks and administered by myself. It’s at http://www.sndbx.org.
Thanks!
Small Potato: Thanks. I hear what you’re saying but I also hear what Jerald is saying and tend to agree with the legality over the ethics. Ethics don’t stand up in court, y’know what I mean? I’m glad things are working out for you. :)
Yea, I know :-). You’re right and Jerald’s right.
My response was simply trying to explain that I’m bothered by that problem from the ethics point of view. And that, designers (and coders) who feel the same way aren’t necessarily unfit for GPL.
Thanks Aaron
I got myself into that one, didn’t I? (Or maybe it’s you who have gotten yourselves into something!)
Give me a little time and I’ll attempt to structure an overall concept. I’ll admit that it’ll probably be best sent via email in this case.
(Don’t say I didn’t warn you though. Be prepared for what could possibly turn-out to be one of many classic tangents.) ;)
Pingback: WordPress: Another Million Mark « Changing Way
Pingback: Sandbox Designs Competition » Update before the weekend
Another fantastic podcast!
Most if not all of the Automattic team will be at WordCamp. Most members arrive in town right before it.
WordPress 2.3 release is planned for September 20, 2007
WordPress 2.0.x main reason for being maintained is a commitment by Ryan, Mark, and others to the people that use WordPress, not whether or not it is included in a Linux distro — though, of course, we are sensitive to do meet the needs that allow it be included.
WordCamp: Matt joined the discussion and says “it’s coming together” and I am sure registration will be enabled and the 411 will be shared ASAP.
WordPress.com does not yet have tags. Well we do, but they are actually just categories as they have always been. We have delayed taking the related tag code from WordPress core trunk until it has been tested more.
Like WordPress.com, LiveJournal publishes much of its stats.
The WordCamp website is being updated at the moment, apparently. Our voice has been heard.
Oooooo! I like the dark background and the logo. Pretttty!
I have been thinking about the webfeed without a blog or website idea for awhile. Hearing you guys discuss it in Episodes 24 and 25 prompted me to experiment.
Feed
http://feeds.feedwithoutablog.com/FeedWithoutABlog
Landing Page
http://feedwithoutablog.com
Excellent example, Bob! I think this was the idea that Aaron was toying with as well (from what I gathered anyway).
Now… The interesting side to this – is how to find newer, ‘reduced’ or subversive methods of branding. Favicons are an obvious example – small, compact – all a person needs to have a visual identity in both the RSS and desktop link file (or favorites) area.
Depending on the aggregator (client-side) – to what extent can branding occur, or how streamlined or even necessary is it? Experiment with that, and see if it accomplished a new way of thinking toward branding.
Something I touched on in my email to the guys here is, that we often determine branding as purely a visual imagery concept – when in reality, I’m in the belief that branding is also text. Slogans, titles, key-phrases – the things that associate relationships to us individual or as an entity. Confirm this by conducting a search on Google. What do you see? Each string of text, is not only informational – but it is in a sense – or has the possibility to be – branding.
Hi, I really enjoy this podcast. Have been listening to you from the very beginning and will surely continue to do so!
One comment related to your recent discussion on many sites using something older than the newest version of WordPress. In our part of the world, getting the newest one in use depends heavily on the (often overloaded) volunteer person, who has been making the translation/localization to our language & providing the full WP package to be downloaded from his site. Other than WP-life sometimes eats up his time from translation/localization work, and we (users) cannot do anything, but wait a bit longer. With the vulnerabilities in our blog…
Again, no-one around here doesn’t seem to know a clever, collaborative way of localizing the newest WP version incrementally as a team – and I personally don’t know if WP has been well built to support that. So, if you’re aware of a good, easy way to distribute the localization effort to several persons (and, of course, preferably so that we could utilize all earlier localized strings), please let us know.
When it comes to software vulnerabilities and patching them quickly in general, I seriously believe that WP could do a better work there. Maybe provide an automat(t)ic notification, download/installation functionality, or something like that. Again, for purely bug fixing / vulnerability patches, this should also happen so, that localization is not lost.
All answers highly appreciated. Thank you for your efforts to keep us up-to-date on what’s happening on the WordPress community.
Pingback: Announcement and some links for light reading at WPBOARD.Com
I just finished listening to your altest podcast and although informative on the various
licenses it actually raised more question in my mind than it solved.
Let’s set the scene.
I’ve downloaded Pordpress and set up a Blog with a default theme. But that theme
isn’t ‘me’. And of course it looks like every other new WordPress blog. So I install
another – close to what I want my blog to look like. But not quite!
In style.css
I change the background color.
I change the font.
I change the font-size.
I don’t like the placement of the main body – so I move it.
I change the header image.
In *.php
I don’t like *. So I change it.
… and the list goes on (and on) …
I do the same for some of the plug-ins.
The Theme and Plug-in are changed, but still most of it is the original
authour’s work, I just made it look “better”.
Slowly it becomes ‘My’ blog and not a copy of someone elses blog.
I add an attribution line near the bottom, it’s a WordPress Blog and is
based loosley on ‘xyz theme’.
My question – in practical terms, how much of this is cricket, kosher, ethical, legal
under the various licenses? I’m not going to re-release it or distribute it to
others. The casual blog reader will never see the files, just the end product of the
changes. With Stylish or Web Developer/Grease Monkey a user can easily see the Style
Sheets – with the original author’s name (I leave that)