When you play with the devil... you will get burned. So let this be a lesson for handing your customer's data over to the RIAA thugs.
On a lighter note, looks like the RIAA has really stream lined the process of putting the screws to the customer. Honestly, you can't get any faster then straight to debt collection agency! Looks like due process was really slowing down their efforts, but now that it has been nixed from the check list they are free to pursue their interests without that peksy court system in their way.
Too bad I can't just go around and asking debt collection agencies to gather up money for me. I'm sure someone would disagree with me if I randomly decided some poor bastard off the street owed me $3000 or face a very long trial attempting to prove that I don't.
Yee gads! I wonder if I can patent this as a business methodology?
Still, they didn't mention the download location then, so I suppose it counts as the second half of the article with a generous portion of laziness in between.
You confuse integration of services with integration of applications.
In the situation you described... this was all the function of a calendaring application. Email notification being simply the avenue for alerts. I'm not sure even the contestants of the perl obfuscation contest could role those actions into 5 or 6 apps.
There are a marvel of architecture concerns that could be implemented to do everything you want it to do.
A calendaring program with simple tray functionality would solve all of that. Email notification as an auxilary component of the calendar server would still be an option, but not the rule.
All in all, I never heraled seperate data sources which is what you seem to infer. Data can be shared and managed centrally with no problem. In fact, my point was data should be central and client applications need to be fed what they need to know.
Everything you describe could easily exist as seperate applications manageable via multiple front ends or via one front end. The idea should be further stated "seperation with central data sources."
I believe it was confusing because you are not looking past email only functionality. There are many data sets which could be related to one particular object... most of which your address book doesn't give two bits about. (literally)
Originally... it was a philosophical arguement, but when push came to shove it was the right tool for the job. This quelled things in the past and toned down the flame wars.
Skip to the present, someone in their spare time, who was contracted by OSDL, was working on a competing open source client or implentation. This in itself is not wrong at all, but the terms of their license say this is a big no no.
Some time ago, when such an arguement came up in the past the BK guy said they would just keep changing the protocol and breaking it, but that apparently wasn't really enough of a deterant.
Suffice it to say, their product is their livelyhood and in the end it was cost effective to drop linux support. In my own thoughts, dropping the linux side of life really means there is little reason for the competing faction to create an open source client. (I'm really hard pressed to remember if it was a client or not)
In the interm, they have offered free licenses for a good chunk of developers, but no one at OSDL. (if linus leaves, he qualifies for a free license).
Unfortunately, this is from memory and a little of it is mixed in with my interpertation. The original stated motives for dropping linux support in the long term were profit driven, but if you think about it you may reach the same conclusion I did.
Honestly, I don't really feel BK did anything really wrong here. It's a closed source proprietary product with a few open sourced pieces. Someone might offer some history on the matter, but they may owe their roots to linux. Still, the old saying comes to mind, "You knew I was a snake when you took me in." (Yeah, I know that has a negative connotation to it, but the idea is that when it's someone elses court it's their rules)
All in all, makes for a good book... can't wait to see the ending.
Since this is from memory... any updates or additions would be helpful. Either that or you can read all the threads elsewhere... it's not like these were secret phone calls.
Since we are only in a review process for open xchange the outlook connector problem could be interesting to solve. The painful problem I've had in the past is due to variances in the ldap structures the various versions of outlook and outlook express support. Somewhere, sometimes ago, someone documented some various differences. Note, this wasn't even regarding the connector.
The trick for me was configuring ldap with an sql backend and my ldap tables were created upon request. (additional overhead, but it cannot be helped)
At no point did I mean to imply it is a petty need. It's a problem I face currently and thus I've delved a good bit into the subject.
Building most everything from the ground up, I have had the luxury of standarizing on software deployments.
The PDA problem is going to be interesting, but our sales force is not to that point. Mainly because the product doesn't ship more then 2 weeks from contract signing and they don't necessarily need to sell in quantity.
I still do have windows servers on the network and I honestly think it's a bit of a pipe dream to be a 100% linux shop here. (Sometimes you are forced to go with a less expensive product and your vendor lies about linux support... I kid you not)
In any event, my original complaint was only regarding the "eggs in one basket" mentality and your particular situation looks to be the resultant of attempting to implement a still fairly young project into an existing shop.
Here, I've tried to ensure we are not tied to a specific implementation, as I look for feature sets that ensure we have the ability to build upon what we are given and manipulate that data through exterior methods if warranted.
So far... everything is working out... still more problems to tackle though.
Most office drones don't ask for that configuration per say... they just want certain things... outlook happens to have those and suddenly its not those features they want, but its outlook functionality. Actually, I have had more then a few feature requests for things outlook doesn't have. When you can pose the question, "What do you need in your day to day routine or what would make things easier|more efficient?" You really would be surprised what the brighter bulbs say.
Breaking the outlook mentality was my first approach, but the tools available at the time did not fulfil our feature list. Though I have to say, I had some good progress patching up the cvs of moregroupware at the time. When it came to a review we decided to wait for things to mature and continue to use our current infrastructure.
In my ldap auth setup, most users don't exist in the system at all, but just entities in ldap. The majority of the users are for samba pdc auth, but even so I tend to build the accounts with posix attributes as well.
So yeah, the subsystem believes they are real users (they are... they just don't exist in flat files)
In any event, I think that's pretty much the approach open-xchange is using.
Probably not in some major capacity, but I suspect it's there. All in all, maybe that is why they are in the mid sized category! [Think outside the box] Just kidding... mostly.
However, one thing about the article really annoyed me and that was the calendaring functions.
Not to go crazy on this one, but what is the big deal is requiring your calendar and address book be tied to your email client. I guess somewhere along the line everyone got mixed up and decided this is the way life should be.
It's not difficult to seperate the three and it is certainly not difficult to use them together (ie, mailto link, ldap interface for address). Then if you are really slick your address book ldap elements for your email clients are meta tables based on an extended set of data available... so you get to squeeze tons more information into a relatively organized space.
That said, I have to get around to configure Open-Xchange for work and setting up the outlook clients with the connector plugin. The suits really love that stuff... me... I just want them to use the ticket system more.
I've been to to one of the backhaul points myself by simple chance. I happened to be doing work that involved that facility... sadly their tech on hand knew very little and couldn't answer many questions. Which just tells me their net eng department is centralized somewhere far and away.
Two of my friends actually fell victim to mac address spoofs within a fairly short time frame. In both cases their service was returned to normal within a day and the offenders were caught. The nodes here are very small and we don't have a large metropolitan sized population.
(I'm guessing it was mac address spoofing, I didn't get any tech details, just a few uncertain details)
For me, it's been fairly good service and I'm worried that it will change when comcast comes to town. At least, I suspect they are going to kick my ass for the 5 gig I pull down every week.
Yeah, don't these things have to be approved, much like the proposed DirecTV and DishNetwork merger. While they were building up for the grand merger finale... it was eventually trumped and a flat no too.
Being a bankruptcy buy out... is there an exception?
I heard the next version of the GPL will require everyone to throw pies at Bill Gates.
At least, that's what I heard anyway.
When whatever changes come up, they will be reviewed and we can rant and rave about it at that time.
Nothing is founded, no concrete written agendas were tossed out by the article and all we have is a hypothetical situation that would be very different from the current model.
Like many have said and will say, it's usually a good idea to specify the version of the GPL in which you release software. Unless you really don't care what kind of changes are made at a later date.
I'm not saying all of this isn't going to come true, but at this juncture we could very well be required to throw pies to comply with the next redistribution agreement.
I just have Myth on my linux box. pvr250 and dxr3. I just use myth to schedule and record everything. Since I rarely watch television when it's actually on... it's the only way I catch the shows I like.
It's not something everybody is going to want to dump money into and for the investment cost was minimal.
The set top unit I'm going to eventually build will replace all of this. It will come in at around 500 for all the parts I have to purchase. Most everything else is taken from my various dead laptops.
My strategy has been to wait for deals on things and slowly gather pieces and occassionally I get some decent hardware free from my friends. ie, this is dead, you can have it;)
I had FC1 running patched up for a very long time, but for various reasons I eventually went with FC3. (Being fc4 is nearly out.. it's a little more polished then a fresh release now).
That being said, at the house when I want to update to a new FC release I can do it fairly easily. I simply have to change the release version and let it fly.
I did have a problem once where I had to manually reinstall one rpm.
Though nothing is guranteed in this manner and I'm sure it isn't as well played out as Debians.
Things really don't break enough to worry about rolling out mass changes at once, but any good admin can come up with an effective roll out stategy.
Still, Debian is a great distro and while I'm on a different side of the fence, we are all linux users.
Slashdot Mirror
If she wins, she can get some cash and pay off the RIAA. Maybe even have some change left over.
In the future, it will slow down the extortion machine, but the law suits will continue to go.
They are going to do everything they can do until someone pushes the line back a bit, but in the end it will not stop them.
When you play with the devil... you will get burned. So let this be a lesson for handing your customer's data over to the RIAA thugs.
On a lighter note, looks like the RIAA has really stream lined the process of putting the screws to the customer. Honestly, you can't get any faster then straight to debt collection agency! Looks like due process was really slowing down their efforts, but now that it has been nixed from the check list they are free to pursue their interests without that peksy court system in their way.
Too bad I can't just go around and asking debt collection agencies to gather up money for me. I'm sure someone would disagree with me if I randomly decided some poor bastard off the street owed me $3000 or face a very long trial attempting to prove that I don't.
Yee gads! I wonder if I can patent this as a business methodology?
Ominous...
Yeah, I grabbed it that same day too...
It was already released then...
Still, they didn't mention the download location then, so I suppose it counts as the second half of the article with a generous portion of laziness in between.
Who is the Gordon fellow? He thinks he is soooo smart that he can comment on the already tried and true Moore's Law.
I'll tell ya, the nerve of some people, sheesh.
Your proposal is acceptable.
How did the mods miss this... I laughed a good bit mr. ac.
In the immortal words of Bruce Campbell, "Come get some."
When you pry it from my cold dead hands.
Not so...
You confuse integration of services with integration of applications.
In the situation you described... this was all the function of a calendaring application. Email notification being simply the avenue for alerts. I'm not sure even the contestants of the perl obfuscation contest could role those actions into 5 or 6 apps.
There are a marvel of architecture concerns that could be implemented to do everything you want it to do.
A calendaring program with simple tray functionality would solve all of that. Email notification as an auxilary component of the calendar server would still be an option, but not the rule.
All in all, I never heraled seperate data sources which is what you seem to infer. Data can be shared and managed centrally with no problem. In fact, my point was data should be central and client applications need to be fed what they need to know.
Everything you describe could easily exist as seperate applications manageable via multiple front ends or via one front end. The idea should be further stated "seperation with central data sources."
I believe it was confusing because you are not looking past email only functionality. There are many data sets which could be related to one particular object... most of which your address book doesn't give two bits about. (literally)
That's what I have been looking at for a while.
It's nice to have a snappy client too. The complete network dependance can sometimes pile up painful screams of sales personel.
So far, not having any one product to fill my needs, I've began integrating most things with a common authentication backend. (ie ldap)
One of the last pieces is email. (Thanks to all so far for their insightful comments)
Originally... it was a philosophical arguement, but when push came to shove it was the right tool for the job. This quelled things in the past and toned down the flame wars.
Skip to the present, someone in their spare time, who was contracted by OSDL, was working on a competing open source client or implentation. This in itself is not wrong at all, but the terms of their license say this is a big no no.
Some time ago, when such an arguement came up in the past the BK guy said they would just keep changing the protocol and breaking it, but that apparently wasn't really enough of a deterant.
Suffice it to say, their product is their livelyhood and in the end it was cost effective to drop linux support. In my own thoughts, dropping the linux side of life really means there is little reason for the competing faction to create an open source client. (I'm really hard pressed to remember if it was a client or not)
In the interm, they have offered free licenses for a good chunk of developers, but no one at OSDL. (if linus leaves, he qualifies for a free license).
Unfortunately, this is from memory and a little of it is mixed in with my interpertation. The original stated motives for dropping linux support in the long term were profit driven, but if you think about it you may reach the same conclusion I did.
Honestly, I don't really feel BK did anything really wrong here. It's a closed source proprietary product with a few open sourced pieces. Someone might offer some history on the matter, but they may owe their roots to linux. Still, the old saying comes to mind, "You knew I was a snake when you took me in." (Yeah, I know that has a negative connotation to it, but the idea is that when it's someone elses court it's their rules)
All in all, makes for a good book... can't wait to see the ending.
Since this is from memory... any updates or additions would be helpful. Either that or you can read all the threads elsewhere... it's not like these were secret phone calls.
Since we are only in a review process for open xchange the outlook connector problem could be interesting to solve. The painful problem I've had in the past is due to variances in the ldap structures the various versions of outlook and outlook express support. Somewhere, sometimes ago, someone documented some various differences. Note, this wasn't even regarding the connector.
The trick for me was configuring ldap with an sql backend and my ldap tables were created upon request. (additional overhead, but it cannot be helped)
At no point did I mean to imply it is a petty need. It's a problem I face currently and thus I've delved a good bit into the subject.
Building most everything from the ground up, I have had the luxury of standarizing on software deployments.
The PDA problem is going to be interesting, but our sales force is not to that point. Mainly because the product doesn't ship more then 2 weeks from contract signing and they don't necessarily need to sell in quantity.
I still do have windows servers on the network and I honestly think it's a bit of a pipe dream to be a 100% linux shop here. (Sometimes you are forced to go with a less expensive product and your vendor lies about linux support... I kid you not)
In any event, my original complaint was only regarding the "eggs in one basket" mentality and your particular situation looks to be the resultant of attempting to implement a still fairly young project into an existing shop.
Here, I've tried to ensure we are not tied to a specific implementation, as I look for feature sets that ensure we have the ability to build upon what we are given and manipulate that data through exterior methods if warranted.
So far... everything is working out... still more problems to tackle though.
Well,
Most office drones don't ask for that configuration per say... they just want certain things... outlook happens to have those and suddenly its not those features they want, but its outlook functionality. Actually, I have had more then a few feature requests for things outlook doesn't have. When you can pose the question, "What do you need in your day to day routine or what would make things easier|more efficient?" You really would be surprised what the brighter bulbs say.
Breaking the outlook mentality was my first approach, but the tools available at the time did not fulfil our feature list. Though I have to say, I had some good progress patching up the cvs of moregroupware at the time. When it came to a review we decided to wait for things to mature and continue to use our current infrastructure.
Hrm,
In my ldap auth setup, most users don't exist in the system at all, but just entities in ldap. The majority of the users are for samba pdc auth, but even so I tend to build the accounts with posix attributes as well.
So yeah, the subsystem believes they are real users (they are... they just don't exist in flat files)
In any event, I think that's pretty much the approach open-xchange is using.
Are they really sure they are not using linux?
Probably not in some major capacity, but I suspect it's there. All in all, maybe that is why they are in the mid sized category! [Think outside the box] Just kidding... mostly.
However, one thing about the article really annoyed me and that was the calendaring functions.
Not to go crazy on this one, but what is the big deal is requiring your calendar and address book be tied to your email client. I guess somewhere along the line everyone got mixed up and decided this is the way life should be.
It's not difficult to seperate the three and it is certainly not difficult to use them together (ie, mailto link, ldap interface for address). Then if you are really slick your address book ldap elements for your email clients are meta tables based on an extended set of data available... so you get to squeeze tons more information into a relatively organized space.
That said, I have to get around to configure Open-Xchange for work and setting up the outlook clients with the connector plugin. The suits really love that stuff... me... I just want them to use the ticket system more.
It would be nice if Evolution had a win32 port.
I still can't believe this isn't an April Fools article.
Someone must be late to the game.
Yeah they do some fairly long backhauls.
I've been to to one of the backhaul points myself by simple chance. I happened to be doing work that involved that facility... sadly their tech on hand knew very little and couldn't answer many questions. Which just tells me their net eng department is centralized somewhere far and away.
Two of my friends actually fell victim to mac address spoofs within a fairly short time frame. In both cases their service was returned to normal within a day and the offenders were caught. The nodes here are very small and we don't have a large metropolitan sized population.
(I'm guessing it was mac address spoofing, I didn't get any tech details, just a few uncertain details)
For me, it's been fairly good service and I'm worried that it will change when comcast comes to town. At least, I suspect they are going to kick my ass for the 5 gig I pull down every week.
Yeah, don't these things have to be approved, much like the proposed DirecTV and DishNetwork merger. While they were building up for the grand merger finale... it was eventually trumped and a flat no too.
Being a bankruptcy buy out... is there an exception?
Some much appreciated insight would be helpful.
I heard the next version of the GPL will require everyone to throw pies at Bill Gates.
At least, that's what I heard anyway.
When whatever changes come up, they will be reviewed and we can rant and rave about it at that time.
Nothing is founded, no concrete written agendas were tossed out by the article and all we have is a hypothetical situation that would be very different from the current model.
Like many have said and will say, it's usually a good idea to specify the version of the GPL in which you release software. Unless you really don't care what kind of changes are made at a later date.
I'm not saying all of this isn't going to come true, but at this juncture we could very well be required to throw pies to comply with the next redistribution agreement.
Bad analogy...
That's one bad ass speaker system.
You can order the parts, generic casing and all the fun stuff if you really want too.
Our local shop used to build them... until they went defunct.
Me myself,
;)
I just have Myth on my linux box. pvr250 and dxr3. I just use myth to schedule and record everything. Since I rarely watch television when it's actually on... it's the only way I catch the shows I like.
It's not something everybody is going to want to dump money into and for the investment cost was minimal.
The set top unit I'm going to eventually build will replace all of this. It will come in at around 500 for all the parts I have to purchase. Most everything else is taken from my various dead laptops.
My strategy has been to wait for deals on things and slowly gather pieces and occassionally I get some decent hardware free from my friends. ie, this is dead, you can have it
Yeah...
If you only watch the first half of the movie its a pretty good love story with a happy ending.
I've never seen the other half of the movie.
Eh,
you can wipe the disk for a recover if the master password is tampered.
Read the provided roxbox link.
The reason contact wearers often have problems with monitors is because you stare!
You have a tendency to blink less and your contacts dry up.
no, snail mail written letter...
a court order would have been excessive.
This was also before the rampant hijacking as well.
I use apt-get myself, but I am a Fedora user.
I had FC1 running patched up for a very long time, but for various reasons I eventually went with FC3. (Being fc4 is nearly out.. it's a little more polished then a fresh release now).
That being said, at the house when I want to update to a new FC release I can do it fairly easily. I simply have to change the release version and let it fly.
I did have a problem once where I had to manually reinstall one rpm.
Though nothing is guranteed in this manner and I'm sure it isn't as well played out as Debians.
Things really don't break enough to worry about rolling out mass changes at once, but any good admin can come up with an effective roll out stategy.
Still, Debian is a great distro and while I'm on a different side of the fence, we are all linux users.