Hacker Newsnew | past | comments | ask | show | jobs | submit | 6xggd7's commentslogin

And what were they going to tell the guy? It's not like they were going to give him a choice, or offer him restitution.

Not doing something like this leads to stupid stuff like having POTUS' handle be "real donald trump" (yes, I know choosing that handle predates his being POTUS, but you get the idea).


> Not doing something like this leads to stupid stuff like having POTUS' handle be "real donald trump" (yes, I know choosing that handle predates his being POTUS, but you get the idea).

I actually find this a charming reminder of the old days of the web. there's a certain populist quality to the idea that no one is important enough to snatch a particular username that some commoner took first. I agree situations like @realdonaldtrump are kind of silly, but it doesn't hurt anyone. anyone who actually has a large audience has a verified account so there's little doubt regarding who actually controls it.

that said, we really do need a responsible way to reclaim truly inactive accounts without enabling "reset my password via email" type attacks.


Are you saying that if another Pavel Lishin ascends to the office of U.S. President, you'd support him just being able to take away my Twitter handle?


You're suggesting that there is no other appropriate handle they could have come up with beyond "sussexroyal"? And beyond that, what gives one person the right more than any other to a particular handle? Even with your POTUS example.

So yes, I think they should have at least asked first and tried to resolve it amicably.


So if someone becomes president, they should be able to take my handles? Seems worse to be so egregiously unfair.

No one should be able to get something any more than any one else. Of course that’ll never be the case. But why excuse the behavior and even encourage it?


Who's still using Apache?


Ugh, seriously. I mean, who wants a stable http daemon that's well supported, well documented, and well understood by a giant community of users? Sounds boring to me...


I use it. On purpose. It's a good general purpose web server and does a good job.


It's also copiously documented and extremely well-understood. There will always be bugs in software but you can usually fix problems quickly, there's few surprises or gotchas. I trust it.


Two million servers, according to Rapid7: https://blog.rapid7.com/2019/04/03/apache-http-server-privil...


40% of web?


"Apache is used by 43.8% of all the websites whose web server we know." according to https://w3techs.com/technologies/details/ws-apache/all/all

I would venture a guess and say it's largely because all the shared hosting providers use it. Less and less people actually choose it given a choice.


Yeah sorry, I meant on purpose.

Most shared hostings still use Apache for compatibility with .htaccess and rubbish like that.


Rubbish? You mean like keeping the web working and making sure URLs never die? Not everything needs to be upgraded to the latest hot thing. HTTPD is proven & stable; this is a rare bug.


For example with RHEL you have apache in base repository, but for nginx you must either add unsupported epel or nginx own repositories. If you want commercial support from RHEL, but you don't want to buy another commercial support fro Nginx, you have to use apache httpd.


That's not true, Red Hat actually has nginx in its Software Collections: https://access.redhat.com/documentation/en-us/red_hat_softwa...


I am. It is extremely fit for purpose. What do you think is wrong with it?


Me. Why shouldn't I?


Haven't you heard, Apache isn't Web Scale.


I'm sure Linus used clean language 99.999% of the time. He sends dozens of mails daily, so his rate of swearing is not out of the ordinary. The media made it to be something newsworthy, when it was not.


Well, there may be some selective reporting, but I'm pretty sure you could go through the public writings of other prolific open source contributors (e.g. Larry Wall) without even digging up ONE instance of public profanity.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: