33 Comments

  1. Andreas Nurbo

    Anyone correct me if im wrong. But how many of Automatics services that is stuff that runs on their servers are open source, i.e not the plugin installed with WordPress? PollDaddy, Akismet, VaultPress, JetPack, Gravatar, IntenseDebate, VideoPress, SimpleNote?
    If its as I suspect that everything is closed source, i find it somewhat curious about the different attitudes to software. On server, closed and proprietary fine. Together with WordPress must be OS, and apparently on your phone. Must be OS.


  2. I heard about a project a while ago (before the PressGram anouncement) which sounded a lot more promising to me. It was going to be open source. I don’t know if it is still under development or not though.


  3. @Andreas Nurbo – That’s an entirely different situation. As Jeff pointed out, all of the proprietary Automattic services are server side. I don’t think they have any distributed closed source products, or at least not that I’m aware of.

  4. Andreas Nurbo

    @Ryan Hellyer – If you promote open source its a little odd to draw the line at ones server. Open source has nothing to do with distrubution per se. Especially given the hardcore stance towards GPL that exists in the community and the leadership. The reason I can see is that Automattic would give away its business model by doing so. But then being so hard against it is a little iffy.
    @Jeffro – See above.

    Anyway this is a little offtopic.

    If i had had an iphone id probably try out the plugin and app. It looks really good.


  5. @Andreas Nurbo – what @Jeffro said, GPL is copyleft and you have to publish the source code under the license (and most copyleft licenses) if you distribute the product, an app is a prime example of this: a distributed product that’s made available for people for free or as a purchase. http://en.wikipedia.org/wiki/Copyleft

    To be clear though, Pressgram doesn’t break the GPL since it’s code was not derived from any work that was copyleft. The decision to go with copyleft or not is a personal one and one that John is entitled to, but of course everybody has differing opinions on what the right way to go is.

    Personally I’m excited to try it out, but wish it was GPL so it would help move the WP app space forward instead. :)


  6. I’m mildly curious about the sustainability of Pressgram. Aside from future acquisition, how would such an app generate any sort of revenue to warrant the time investment?

  7. Andreas Nurbo

    @Isaac Keyet – I’m well versed in the GPL, but im talking about open source. Requesting and wanting people to make their stuff open source but not doing it one self is the thing I have issue with.

    Hopefully Pressgram finds a suitable income model that support it moving forward so they can create an Android app so I can test it out =).


  8. Re: Pressgram

    I no longer trust John Saddington. His abrupt, no warning closures of both WPDaily and 8Bit was very unprofessional. His excuse that keeping the license to Pressgram proprietary helped his workflow is total BS. He could have made the code open source and still kept it to himself until he was ready to release it. Then the project could really take off because of the already active WordPress community. I smell a profit motive and control issues at work here. He relies on the open source nature of WordPress and yet keeps a service built on top of that proprietary? He probably thinks he’ll make more money by keeping the code proprietary but he’s further marginalizing a community that he’s already been disrespectful to.

  9. Andreas Nurbo

    @Robert Lilly – The app is not built or use any WP code, the rest is server based, the plugin is GPL (I think) so whats not too like?
    If you have such issues take them up with Automattic and other people that makes services for WP but do not release the source.


  10. @Andreas Nurbo – You seem to have an ax to grind with Automattic, and that’s not relevant to the blog post, nor the comments based on it. We have no idea what license(s) they’re using internally because no one but Automattic has access to that code, therefore it’s irrelevant to anyone outside the company.

    In John’s case, he has released this app for public consumption. So, his choosing not to open source it (which I agree he legally has the right to do) is something we are affected by, it’s very relevant, if we want to use the app. I just think his motives for doing so are suspect. I’ve already given my reasons for not trusting him, which was the entire point of my original comment.

  11. Andreas Nurbo

    @Robert Lilly – No issue with Automattic, issue with the different standards that are applied when it comes to view on OS in the WP sphere.
    I’m all for proprietary apps, plugins, services. But if one is a huge OS proponent then one should be it all the way.
    No issue with John wanting to make money down the road with his proprietary stuff. Wish him all the best of luck with that. (Since making a living on donations for free open source software does not work for almost anyone =)


  12. @Ryan Hellyer – Wow! I think the concerns raised in that post, and even more in the comments, could all be addressed by making this project open source and then getting the benefit of eyeballs with different areas of expertise. John can still monetize this, but the code, the service, etc. would be more trustworthy and not dependent on a single person’s/company’s whims.

  13. Andreas Nurbo

    @Ryan Hellyer, @Robert Lilly – Making this OS had not resolved this issue. This issue is that he uses the xmlrpc functionality and that will always make the password info public if the site is not on https. All tools that uses xmlrpc are subject to man in the middle, wireless packet sniffing and so forth. Same as when you login using the browser. XML-RPC really should use alternate method to verify account info. So ppl complaining about this really should get the info correct first. Personally think he should make a plugin to handle the info, would be little more “secure”, so not use the default unsecure xmlrpc functionality. Thought that was the case from the get go.
    Essentially complaining about this is the same as saying that WordPress is insecure.
    Unless I’ve missunderstood something.


  14. @Andreas Nurbo – I assume most people figured the phone application itself was storing the password, not the phone application.

    If you are going to store passwords, then it should be made upfront with a giant warning sign when you sign up. I don’t know if that is the case here or not.


  15. @Andreas Nurbo – Oops, I meant “I assume most people figured the phone application itself was storing the password, not the PressGram website.”

  16. Ted Clayton

    @Ryan Hellyer Wow. And you guys are reading Stephanis’ 2nd post on this as well, right?

    Sarah Gooding had plugged straight into userland’s primal anxieties over loss of control …. then the erstwhile deliverance turns out to have been seeing the black-hats, card-for-card, and upping the ante on the game.

    I don’t have any idea what John Saddington’s trip is …. confronted by Stephanis, he is now backpedelling, or something. But whether John is for-real the oily operator of the week, or was just caught up in the flow and missed that he was playing his support-base for fools & suckers …. the fact is, his own TOS were plainly hostile to users, and contradicted the message under which eg Sarah Gooding, and WPTavern.com, promoted his product.

    Wow. Dancing With The Stars, r us.


  17. @Ted Clayton -This article wasn’t a promotion of his product – just an interview with someone who’s doing something interesting with WordPress. I sincerely hope he changes his licensing to OS – have no idea why he isn’t doing it right away since the app is already launched. He would only stand to benefit from all the input, especially since the WP community is known for having tons of feedback and an abundance of people willing to contribute to OS projects they find to be worthwhile. I’ve really enjoyed the investigative posts Stephanis is publishing on the app and all of the great discussions that are happening here and over there.:)


  18. @Sarah Gooding -Short of saying it’s rubbish, you can’t write an article about something without promoting it :P I think that’s what Ted was referring to rather than implying it was a “promotional article” as such.

  19. Andreas Nurbo

    @Ryan Hellyer – Well I dont see that the server stores the credentials just that it uses them as part of the original request from the app. Sure it results in two possible hijack attempts instead of just one if the app communicated directly.
    but disclosure is always best.

  20. Ted Clayton

    @Ryan Hellyer – That’s right. WPTavern might not be quite the cover of Rolling Stone, but it’s a pretty fair ‘bully pulpit’ for those with products of potential interest to the WordPress usership. Any nominally positive coverage here, acts to promote whatever is being discussed.

    As such, anybody that has a product for WP they’d like, um, publicized to those who might find it useful, on the pages of WPTavern (etc), by their skilled staff of writers (etc) … it is clearly your responsibility – and an important one – to ensure that any, um, ‘backstory’ is fully exposed to the staff, before they expend the effort to write your story up nicely & publish it.

    If you have something you’d like to have covered in one of the leading WordPress news websites, there definitely should not be any dog-piles hidden in the tall grass, for them to get all over their shoe and track through the house.


  21. Congrats to John on the launch although we are finding out some things now that we didn’t know before the launch. However, at lease from what I’ve seen, John is doing a good job with damage control and has been making the necessary changes related to how the product works and the Terms Of Service.

    With that aside, I did an old-man rant on Episode 120 of WordPress Weekly. The question I have is why do so many people like Instagram or Pressgram? In my opinion, I’ve seen more images ruined with dumb filters versus images that were enhanced by them. It drives me insane every time I see someone post a supposedly awesome sunset only to have it look black and white because they applied filters to it. Good job ruining nature’s beauty! That’s why I’m fully behind the #nofilters movement on Twitter. All Instagram has done is make it incredibly easy to ruin pictures. I know there is more to Pressgram than just filters and images but the overall concept is still a head scratcher for me.



  22. lamees

    Lovely post Sarah. You writing is fluid, clear and very engaging. I enjoyed hearing your voice through your words.

    I want the app to be available for android users too.

    I look forward to what’s ahead in the future.


Comments are closed.