So it's not going to use one of the big two package management systems (deb, rpm)? That's idiotic. So they've pretty much screwed themselves on it ever being adopted in most business applications. C'mon guys. Just use whatever is already out there and has withstood the test of time before reinventing the wheel. And yea..don't even get me started on a NEW init system...
A wicked thought passed through my mind: could some major Google shareholders have put him up to this? Google could be the only winner in this, shirley? I would highly doubt that, for the following reasons:
Google's stock price definitely isn't hurting enough to resort to such shady tactics
I doubt Google would go out of their way to destroy a major competitor when they're doing so well, only to open the door for potential antitrust litigation
I think it's cute how Unix vendors are scrambling to provide features that have been standard features in Linux nearly since it's inception. As the saying goes, too little too late.
Hell take a tundra and an F-150 and put them side by side. Besides aesthetic differences, explain to me how one is "clearly" different than the other. Easy, one's a great product and one's a piece of shit. Much like Linux vs UnixWare.
I don't understand. I't been a good two years since I tried to use wi-fi at a Starbucks, but when I did, I didn't pay anything for it. T-Mobile used to be the wifi hostspot provider for Starbucks. Within the past year, Starbucks switched to AT&T (which is essentailly just a rebranded Wayport wifi hotspot system) to provide their wifi hotspots. This is probably where the change in price came from.
A surefire way to ensure that this hack lasts as long as possible is to keep it super-secret and not let AT&T know they screwed up. Actually, it was Wayport's screw up, as they're the company that AT&T contracts to provide their wifi hotspot system.
If you trawl across the Pidgin and Adium tracs and through the Openfire forums there's a workaround in Openfire to do with explicitly setting the xmpp.domain property or something similar. Though I believe Adium added in a workaround at their end too. Yes, there is. But, Pidgin also has a separate 'Connect Server' input field under the 'Advanced' tab to specify the actual connect server vs the XMPP domain, should the two differ. The problem is Pidgin seems to completely ignore the 'Domain' field under the 'Basic' tab when you specify the 'Connect Server' on the 'Advanced' tab. So say my XMPP server is on domain `mydomain.com', but the actual hostname for the XMPP server is `xmpp.mydomain.com'. If you specify the domain to be `mydomain.com', then specify the connect server as `xmpp.mydomain.com', Pidgin will use `xmpp.mydomain.com' for SASL authentication instead of `mydomain.com', thus causing the authentication to fail...This wasn't the case in Pidgin 2.3.
Can you please tell me why you hate not being able to resize the input box. I use iChat and I love the fact that is expands as I need it. Uh, because I prefer to be able to resize it? Does it really matter? The fact is the there is an overwhelming number of users wanting that feature, and a minimal number of developers who don't...I look forward to downgrading to Pidgin 2.3 when I get home...until a usable fork emerges..
Oops, before anyone can correct me:
Hell, just recently they refused to make any changes to the way Pidgin handles SASL authentication to XMPP servers due to a change in the 2.4 codebase that completely breaks SSL encryption to the OpenFire XMPP server... That should be "due to a change in the 2.4 codebase that completely breaks SSL authentication"
Ya know, I can't blame the community for this fork. The gaim/pidgin developers have had a bad history of 'God complex'. Hell, just recently they refused to make any changes to the way Pidgin handles SASL authentication to XMPP servers due to a change in the 2.4 codebase that completely breaks SSL encryption to the OpenFire XMPP server, whereas the 2.3 codebase AND every other XMPP client seems to not have any issues. Their response was something along the lines of "yeah, well we're doing it right..every other client is doing it wrong". I find that hard to believe. This ultimately leaves me with 2 options: either don't upgrade past version 2.3 of Pidgin, or use another client. And yes, not being able to resize the input text box drives me absolutely crazy. I look forward to a forked version addressing this and the XMPP SASL authentication issues.
Their solution is to set up a filter to make sure that no system running the affected software will get automatically updated; once the filter is in place, SP3 will be released to the Web. A fix for the incompatibility will follow. Sounds more like a hack to me.
Too late, Metallica. Yall already blew it for me when the quality of your music took a sharp decline after the black album, and especially after yall decided to go after Napster, which essentially kicked off the RIAA's bullshit campaign. I don't think there's anything yall can do to recover from that one..
I can't help but think that the current big players in the fuel industry would try anything to prevent this sort of thing from happening. They like their record profits and I would imagine intend on keeping it that way, until their lobbying powers wear off and government eventually starts more heavily regulating this corrupt ass industry. I hope I'm wrong on this, however..
Assuming it is true that FOSS is costing vendors $60 billion, wouldn't you think it's about time to start embracing FOSS and it's wonderful model instead of trying to fight it off like some sort of cancer? *Cough Microsoft cough cough*.
Oh, and that's not to mention the occasional idiot dev who breaks things. Heh, yea I'm familiar with that (it's bit me in the ass before). Thats why I've decided a long time ago that Gentoo is not a disto worthy of a business environment. If only our previous admin has thought the same thing it would have saved me quite a bit of time. But on the plus side I did get a free trip to Chicago out of the deal:).
Slashdot Mirror
So it's not going to use one of the big two package management systems (deb, rpm)? That's idiotic. So they've pretty much screwed themselves on it ever being adopted in most business applications. C'mon guys. Just use whatever is already out there and has withstood the test of time before reinventing the wheel. And yea..don't even get me started on a NEW init system...
"Are you thinking 'boo', or 'booerns'?"
As bad as we all think things are getting in the free world, it's things like this that remind me it could be a helluva lot worse.
I always did feel like a slave when I was in high school. Now it looks like the schools will be providing the shackles to seal the deal.
Another strike agains Ballmer.
Can't slip anything past this crowd...I was referring to the feature of being free and open, not common Unix features.
Thank you Mr. Wizard. Didn't you have a show on Nickelodeon back in the 80s or something?
I think it's cute how Unix vendors are scrambling to provide features that have been standard features in Linux nearly since it's inception. As the saying goes, too little too late.
Just wow. I guess Nevada's governor has read one too many RIAA business howtos...
..UnixWars Episode V..Novell Strikes Back.
Ya know, I can't blame the community for this fork. The gaim/pidgin developers have had a bad history of 'God complex'. Hell, just recently they refused to make any changes to the way Pidgin handles SASL authentication to XMPP servers due to a change in the 2.4 codebase that completely breaks SSL encryption to the OpenFire XMPP server, whereas the 2.3 codebase AND every other XMPP client seems to not have any issues. Their response was something along the lines of "yeah, well we're doing it right..every other client is doing it wrong". I find that hard to believe. This ultimately leaves me with 2 options: either don't upgrade past version 2.3 of Pidgin, or use another client. And yes, not being able to resize the input text box drives me absolutely crazy. I look forward to a forked version addressing this and the XMPP SASL authentication issues.
Too late, Metallica. Yall already blew it for me when the quality of your music took a sharp decline after the black album, and especially after yall decided to go after Napster, which essentially kicked off the RIAA's bullshit campaign. I don't think there's anything yall can do to recover from that one..
...and will the FBI be helping subsidize the cost of storage solutions for ISPs too?
I can't help but think that the current big players in the fuel industry would try anything to prevent this sort of thing from happening. They like their record profits and I would imagine intend on keeping it that way, until their lobbying powers wear off and government eventually starts more heavily regulating this corrupt ass industry. I hope I'm wrong on this, however..
Assuming it is true that FOSS is costing vendors $60 billion, wouldn't you think it's about time to start embracing FOSS and it's wonderful model instead of trying to fight it off like some sort of cancer? *Cough Microsoft cough cough*.