Why not just use Sipie? - goodtime_nicemac

Does sipie come with an online live interactive guide?

Sipie is just one of the programming layers that we use. It is not the core of our sofware. I would say VLC or Mplayer is the core or bottom layer. Sipie is the middle layer.

Sipie does not directly support Macs by the author. He also did not write the Mac OSX GUI for Sipie. VM and I wrote it ourselves and figured out how to make it work with our GUI interface. Which in my opinion blows away and unix command line application. If you like using the command line Sipie that is fine. But it does not give the the live interactivity that SiriusMac provides free of charge to its users.

BTW, if you to go about this Mac, does it give any credit to Free BSD? I think not.

We are only making copyright claims to the Software that we wrote and this is the SiriusMac.app and our setup scripts. Yes we wrote those too.

None of the notices from Sipie which is opensource has been removed. All original credits to the author in intact.

Also our version of sipie fixes some bugs to the software. And we did not take credit for fixing those bugs either.

Sincerely,

Goodtime

Reply to This

Sunday, May 06 2007 @ 08:32 AM PDT

Why not just use Sipie? - unicks

I already said that the UI is nice, and yes SiriusMac provides an online guide, it does look nice, and is great front end to Sipie for a user who doesn't want to use the CLI.
But, seeing as chose to rant, I'll try to answer your points one-by-one.

1) Sipie works out of the box on Mac OS X, assuming the the prerequisites have been met, (python 2.4.x, BeautifulSoup, Mplayer and proctools). No modifications are necessary to the source, only to the config file after the initial run of sipie.

2) Please open /Library/Documentation/Acknowledgements.rtf on your Mac read the file and you'll see the following paragraph :-

 
FreeBSD, Inc. ( BSD Operating System )
This product contains software provided by FreeBSD, Inc. and its contributors.
Copyright © 1994-2004 FreeBSD, Inc. All rights reserved. 
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

As you can see this is is a clear credit to the FreeBSD project. This credit is distributed in a "Acknowledgments" file that can be read as part of the distributed software that I have chosen to use (in this case Mac OS X), I can read this file and understand the licenses and sources of any contributing software or technology that has been used to make the software that I am using.

3) I didn't dispute this fact, but if you really want to get into this argument then I would also like to point out that you haven't complied with the rules of the GPL when distributing your application, you are inviting donations for your work, and the adequate credits and acknowledgments have not been given to software that you are distributing, people don't know what they are donating for.
4) You admit to changing the sipie.py script for so-called "bug-fixes"? Why isn't this identified anywhere in the bundle? Why have you not commented or identified these changes?
I refer you to the GPLv2 :-

  
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

But to be honest I can't see any "bugfixes" only minor changes to sipie.py
For example, you have used /Applications/VLC.app/Contents/MacOS/clivlc -I dummy instead of mplayer and some other stuff related to the captcha viewer, but remember you still need to identify these changes and provide "prominent notices stating that you changed the files and the date of any change".

I suggest you release a new version of SiriusMac with a sipie.py acknowledgment in place, a clear notice to what has been changed in sipie.py as a patchfile or even a link to a patchfile on your website, and also clear comments in the code describing what has been changed and when.

Reply to This

Sunday, May 06 2007 @ 02:02 PM PDT

Why not just use Sipie? - goodtime_nicemac

The credits and dated changes to Sipie will be added to our next version of SiriusMac and it will be done during our next update cycle, not before.

For the record, the users who donate are paying for support & development of the GUI. They are not paying for Sipie or any of the other supporting products that make SiriusMac work.

All credits inside Sipie remain intact. Sipie is a single file application and it does not come with another other acknowledgment files. We have not discredited anyone. We will add our changes and date them to the Sipie.exec file.

Look closer at the Sipie code, you did miss an importmant bug fix and we will point this out in the next update. But we will not reveal the bug here.

SiriusMac is free software. In other words, users do not have to pay anything to use SiriusMac.

We will make the changes when we release our next version.

Sincerely,

Goodtime

Reply to This

Sunday, May 06 2007 @ 05:15 PM PDT

Why not just use Sipie? - goodtime_nicemac

The credits and dated changes to Sipie will be added to our next version of SiriusMac and it will be done during our next update cycle, not before.

For the record, the users who donate are paying for support & development of the GUI. They are not paying for Sipie or any of the other supporting products that make SiriusMac work.

All credits inside Sipie remain intact. Sipie is a single file application and it does not come with another other acknowledgment files. We have not discredited anyone. We will add our changes and date them to the Sipie.exec file.

Look closer at the Sipie code, you did miss an important bug fix and we will point this out in the next update. But we will not reveal the bug here.

SiriusMac is free software. In other words, users do not have to pay anything to use SiriusMac.

We will make the changes when we release our next version.

Sincerely,

Goodtime

Reply to This

Sunday, May 06 2007 @ 05:16 PM PDT

Why not just use Sipie? - goodtime_nicemac

By the way.

Thank you for publicly posting your Mplayer code to us. We might use it in our next version and give credit to you in our acknowledgment file. You have saved us a bunch of trouble. Thanks a million.

Sincerely,

Goodtime

Reply to This

Sunday, May 06 2007 @ 05:22 PM PDT

Why not just use Sipie? - goodtime_nicemac

http://nicemac.com/index.php?topic=479.msg2535#msg2535

A public acknowledgement has been posted in the above link.

This and other acknowledgements will be added to a acknowledgements.rtf in the next public release of SiriusMac.

Sincerely,

Goodtime

Reply to This

Sunday, May 06 2007 @ 05:57 PM PDT

Why not just use Sipie? - unicks

No problem, this isn't code but the set of mplayer arguments that worked for me with sipie, Feel free to use it, no credit is necessary as stand alone command-line switches or arguments are not covered by any license. BTW for your reference I'm using Mplayer 1.0rc1-4.0.1.
Also I was using custom functions for pkill and pgrep within sipie, but in the end I compiled proctools, which was much more stable.

Good luck with your product.

Reply to This

Sunday, May 06 2007 @ 05:59 PM PDT

Thank you - goodtime_nicemac

unicks,

Thank you for pointing out this error on our part and it will be rectified in the next version of SiriusMac. Thank you for joining the nicemac team as well.

Looking forward to working with you.

Sincerely,

gt

Reply to This

Sunday, May 06 2007 @ 07:54 PM PDT

Thank you - Jay

I am not a developer of any sort. In fact, I am a geographer, and normally I wouldn't give a hoot about any of the above back-and-forth regarding software development. However, I do care about giving credit where credit is due. And, I'm a fan of civilized discourse. Accordingly, I give lots of kudos to both the above developers and the person who showed the developers what's what. Kudos to unicks for sticking to his/her guns and proving his/her point with grace (i.e. without taking it personally and devolving into name calling). Kudos to goodtime_nicemac for 1) writing a nice application; 2) defending their product without being too dickey (though at first it looked as if they might); 3) accepting that they made a mistake, could learn a thing or two from a veteran, and taking responsibility for it; and 4) fixing it with grace. Your back-and-forth was a pleasure to read, especially since I'm right now doing research in Southeast Turkey where nearly everyone (even the women) gets extraordinarily bent out of shape at the smallest slight. Your back-and-forth is a testament to the power of civil discourse.

Reply to This

Sunday, July 29 2007 @ 02:51 PM PDT