VA can relaunch the site under a new domain, get CmdrTaco to set up a will in case he's hit by a bus, whatever.
And the fact that people can share logins doesn't negate anything. If someone challenges the registration based on fraudulent identity of the alleged owner, "I know his login and password" isn't going to get you very far.
I work in web design. I've set up sites for people and hosted them and run them. There is absolutely no problem with having the client company/person as admin contact and owner of the domain, while I handle absolutely everything. If I disappear, they can find a new company to run the site.
If someone can squat on a domain and make money from no content, clearly domains are too cheap or advertisers are paying too much.
I suspect, however, that most squatters don't make enough money on the domains themselves to make the business worthwhile, and they are more interested in their resale value. However, they park ads on the domain in the mean time, because why not?
It doesn't matter if money changes hands, so long as the standard process is followed--i.e. the domain goes back into the pool where anyone can buy it.
3) Prohibit exchange of domain names. Don't want one? Let it expire and it goes back into the pool. No, you can't sell it, any more than you can sell your telephone number.
But again, this wouldn't benefit the registrars, so it won't happen.
Package management is my biggest issue with OpenSuSE.
They started with YaST in the 9.x series. Then for a while, APT4RPM was the thing everyone used. Then the APT repositories disappeared and I had to switch to Yum, though the web site recommended switching to SMART. Now the official package manager is something I can't even remember the name of because nobody else uses it... *looks it up* Zypper.
I mean, WTF? Five different package managers in a couple of years, and they haven't done the intelligent thing and switched to a proven system that actually works? I mean, I understand why RedHat use RPM--they shat it out, so they feel obliged to keep using it. But why does SuSE keep using it, and why do they keep switching the front end?
"Meanwhile, I have looked into use Rails and found it a great example of shitty code practices."
As someone using Ruby and Rails on a regular basis, I have to say that this is my experience too.
I got involved in a flamewar with developers of a well-known Rails application over my contention that documentation was required. Their position is that you don't need any documentation if you have unit tests; you can simply read the unit tests to work out what the supported API is.
It's a pity SOAP 1.2 isn't back-compatible with SOAP 1.1. Kinda spoils the easy integration story.
I've been trying to connect to a SOAP 1.1 implementation using Java, and the current Java API (SOAP 1.2) doesn't support rpc/encoded required to pass data to my SOAP 1.1 back-end.
But the implementor made a mistake, and also commented out another similar usage, in a different function, ssleay_rand_add. This was a huge mistake, as the purpose of ssleay_rand_add is to add randomness into the random state.
Given that the code is so shoddily written that neither of the functions has a comment to say what it's supposed to do, I think I can forgive him for that.
Slashdot Mirror
I just hope they rule that I can keep my weaponized anthrax. I need it for duck hunting.
VA can relaunch the site under a new domain, get CmdrTaco to set up a will in case he's hit by a bus, whatever.
And the fact that people can share logins doesn't negate anything. If someone challenges the registration based on fraudulent identity of the alleged owner, "I know his login and password" isn't going to get you very far.
The ability to sell Slashdot doesn't depend on the ability to sell the domain name registration.
And the benefit, if you'll recall, is stopping the rampant speculation in domain names, which subtracts value from the Internet.
And in fact, Cfront was a compiler, not just a preprocessor; it was just a compiler that compiled C++ into C.
And that's important to the Internet because..?
I work in web design. I've set up sites for people and hosted them and run them. There is absolutely no problem with having the client company/person as admin contact and owner of the domain, while I handle absolutely everything. If I disappear, they can find a new company to run the site.
If someone can squat on a domain and make money from no content, clearly domains are too cheap or advertisers are paying too much.
I suspect, however, that most squatters don't make enough money on the domains themselves to make the business worthwhile, and they are more interested in their resale value. However, they park ads on the domain in the mean time, because why not?
It doesn't matter if money changes hands, so long as the standard process is followed--i.e. the domain goes back into the pool where anyone can buy it.
Umm, all you have to do is make sure the company owns the domain. That doesn't stop you doing all the setup, development and hosting for them.
Just like advertising agencies launching a new product don't own the trademark, but still do all the product launch, poster design, and so on.
You missed
3) Prohibit exchange of domain names. Don't want one? Let it expire and it goes back into the pool. No, you can't sell it, any more than you can sell your telephone number.
But again, this wouldn't benefit the registrars, so it won't happen.
Package management is my biggest issue with OpenSuSE.
They started with YaST in the 9.x series. Then for a while, APT4RPM was the thing everyone used. Then the APT repositories disappeared and I had to switch to Yum, though the web site recommended switching to SMART. Now the official package manager is something I can't even remember the name of because nobody else uses it... *looks it up* Zypper.
I mean, WTF? Five different package managers in a couple of years, and they haven't done the intelligent thing and switched to a proven system that actually works? I mean, I understand why RedHat use RPM--they shat it out, so they feel obliged to keep using it. But why does SuSE keep using it, and why do they keep switching the front end?
Ah yes, the Goatse Principle.
NSCoffee *joe = [[NSCoffee alloc] init];
NSGrounds *coffee = [[NSGrounds alloc] initWithBeans: DEFAULT_ROAST];
[joe brewCoffeeFromGrounds: coffee];
[joe addTspSugar: 1.0];
while ([joe containsLiquid]) {
user [joe getSip];
}
[joe release];
"Meanwhile, I have looked into use Rails and found it a great example of shitty code practices."
As someone using Ruby and Rails on a regular basis, I have to say that this is my experience too.
I got involved in a flamewar with developers of a well-known Rails application over my contention that documentation was required. Their position is that you don't need any documentation if you have unit tests; you can simply read the unit tests to work out what the supported API is.
Riiiiight.
I dunno, if they make it smaller enough and faster enough I'd pay $60 for it, even with no extra features.
How did we end up in a world where locking up an innocent person for 42 days, without even accusing them of a crime, is considered "moderate"?
I bought my BlackBerry Curve from T-Mobile with no contract. T-Mobile gives you a choice.
Ruby is a language that does pretty much all the good stuff Perl does, without Perl's horrible ugly syntax and crufty semantics.
Or to look at it another way, it's a language that does all the good stuff Python does, without the stupid syntactically significant whitespace.
It's a pity SOAP 1.2 isn't back-compatible with SOAP 1.1. Kinda spoils the easy integration story.
I've been trying to connect to a SOAP 1.1 implementation using Java, and the current Java API (SOAP 1.2) doesn't support rpc/encoded required to pass data to my SOAP 1.1 back-end.
Yeah, if only Apple sold a laptop that was cheaper than a MacBook Pro. They could call it a MacBook or something.
And if only they had a sub-$1000 cheap desktop computer too.
Or buy the DRM-free music on the iTunes Music Store.
I was talking about the OpenSSH code.
If the code was properly documented he wouldn't have made the mistake.
Seriously, guys, document the code to at least say what the functions are supposed to be doing, before you criticize someone for guessing wrong.
Given that the code is so shoddily written that neither of the functions has a comment to say what it's supposed to do, I think I can forgive him for that.