Friday, October 26, 2012
Multiple Mediawikis on one host and/or short URLs
I wrote up a guide to setting up the above mentioned pieces of the puzzle, head here if you are interested.
Friday, October 19, 2012
apache ssl warnings on client localhost
Have you seen these before?
[Fri Oct 19 18:48:22 2012] [info] Seeding PRNG with 1824 bytes of entropy
[Fri Oct 19 18:48:22 2012] [info] [client ::1] Connection to child 0 established (server tehsuck.de:80)
The reason for this is, that spawning a new process for every request is expensive (time and ressourcewise) and thus apache prespawns them and keeps them around. When it now manages this group of proces that all listen to a port and wait for a connection, it just wakes them by talking to them on the port specified last in the config.
Now maybe you have seen these:
[Sun Oct 14 09:55:39 2012] [info] Seeding PRNG with 1824 bytes of entropy
[Sun Oct 14 09:55:39 2012] [info] [client ::1] SSL library error 1 in handshake (server tehsuck.de:443)
[Sun Oct 14 09:55:39 2012] [info] SSL Library Error: 336027900 error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol speaking not SSL to HTTPS port!?
These are caused by the same process because the threadmanager apparently doesn't know SSL, so it tries to speak plain HTTP on port 443 which is wrong of course.
This is the result of
LISTEN *:80
LISTEN *:443
somewhere in your apache config.
So in order to turn the latter into the former swap the order and then to get rid of the messages use
and apped the follwing to your Customlog directive
env=!loopback
[Fri Oct 19 18:48:22 2012] [info] Seeding PRNG with 1824 bytes of entropy
[Fri Oct 19 18:48:22 2012] [info] [client ::1] Connection to child 0 established (server tehsuck.de:80)
The reason for this is, that spawning a new process for every request is expensive (time and ressourcewise) and thus apache prespawns them and keeps them around. When it now manages this group of proces that all listen to a port and wait for a connection, it just wakes them by talking to them on the port specified last in the config.
Now maybe you have seen these:
[Sun Oct 14 09:55:39 2012] [info] Seeding PRNG with 1824 bytes of entropy
[Sun Oct 14 09:55:39 2012] [info] [client ::1] SSL library error 1 in handshake (server tehsuck.de:443)
[Sun Oct 14 09:55:39 2012] [info] SSL Library Error: 336027900 error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol speaking not SSL to HTTPS port!?
These are caused by the same process because the threadmanager apparently doesn't know SSL, so it tries to speak plain HTTP on port 443 which is wrong of course.
This is the result of
LISTEN *:80
LISTEN *:443
somewhere in your apache config.
So in order to turn the latter into the former swap the order and then to get rid of the messages use
SetEnvIf Remote_Addr "127\.0\.0\.1" loopback
SetEnvIf Remote_Addr "::1" loopback
and apped the follwing to your Customlog directive
env=!loopback
Wednesday, October 17, 2012
changing the title of listings
This question cropped up in the channel yesterday and is quite obvious in the source
but not so in the documentation. If you want to change the name of the listing (think
localization) then you need to change three things.
\renewcommand\lstlistingname{Quellcode}
\renewcommand\lstlistlistingname{Codefragmente}
\def\lstlistingautorefname{Alg.}
The first line is the name at every listing, the second the title for the list of
listings and the third if you want to autoref a listing.
SemanticBundle for MediaWiki
So i inherited this wiki 1.16 with the insane number of 50 plugins. I am now just upgrading the hell out of it and one plugin that quite tripped me up was SemanticBundle. You need to leave it enabled in the LocalSettings.php but then go to Extension/SemanticBundle/SemanticBundleSettings.php (sometimes the middle part reads semantic-bundle) and disable everything after the
enableSemantics( parse_url( $wgServer, PHP_URL_HOST ) );
line. Then go to <yourwiki>Special:SWAdmin page and click initialize (no, upgrade did not work for me - it still crashed even though it was installed before)
Afterwards just remove the comments you added earlier.
enableSemantics( parse_url( $wgServer, PHP_URL_HOST ) );
line. Then go to <yourwiki>Special:SWAdmin page and click initialize (no, upgrade did not work for me - it still crashed even though it was installed before)
Afterwards just remove the comments you added earlier.
Monday, October 1, 2012
Google and Bettina Wulff
For anyone not into German politics, let me retell the story, it's not really important since there are cases like this one in many countries. The issue is simple, our former second lady was rumoured to have worked at an escort service years ago. The claim seems to be completely made up but that's what rumours are all about. Be as it may it spread around the internet and Google's autocomplete suggested it to anyone searching for her after some time. She was and is quite peeved about it and sued Google, the result of that lawsuit is yet to be determined.
Now the quintessence of the problem is, whether Google is required to censor it's results (and the suggestions are results in a way). It has done so in the past, ordered by court or law (e.g. Italy/France/Egypt or even DCMA), semivolontarily (e.g. China a few years ago or recently RS/torrents in the suggestions) or completely volontarily (e.g. the recent anti muslim video scandal).
Let's state a few facts that i have a feeling are not obvious to everyone.
Is it Ok to force google to remove autosuggestions? I'd say yes, but the case at hand would have to be even clearer than for mere search results. It is definitely desirable to censor, (child) pornography from there for example. Mrs Wulff on the other hand has no right to demand this. The tabloids would have to be outlawed long before that.
The only compromise i could imagine would be to make a list of the results/suggestions not shown alongside their frequency accessible somewhere. This wouldn't solve the problem of technical feasability though.
Now the quintessence of the problem is, whether Google is required to censor it's results (and the suggestions are results in a way). It has done so in the past, ordered by court or law (e.g. Italy/France/Egypt or even DCMA), semivolontarily (e.g. China a few years ago or recently RS/torrents in the suggestions) or completely volontarily (e.g. the recent anti muslim video scandal).
Let's state a few facts that i have a feeling are not obvious to everyone.
- It is technically possible, but only to a degree. I've heard before, that it is and that it isn't and both extremes are pretty much nonsense. I'm not going to discuss how searching works on the inside but you could always put a filter on the end results, there is no denying that. It wouldn't be costly either, compared to the processing, the data experiences already and the fact that it has happened in the past prove this. Still it would be completely out of the question to do try and filter everything that might be offensive. It would be close to impossible to come up with a list that fits everywhere, human intervention is too costly and last but not least, what's acceptable and what isn't is just not canonical (think different countries, cultures, religion).
- It's not a new problem. I don't even understand why my favourite newspaper made that claim in the first place, it's just way too far out there. There are so many precedences for every aspect of the story and I'm not just talking about the internet here. For the specific case of Mrs Wulff just think of all the garbage the yellow press rumours every day. It's just a sad fact of being in the spotlight.
- This is not about free speech. Although i can't argue with active undertakings to hide certain results being "censorship" of some kind, so is not pushing certain others. Every little tweak Google would make to their search algorithm would have similar albeit indirect effects. Also at least from a German point view, it is ok to prevent certain things to be said. The German constitution deliberately weighs off freedom of speech vs demagoguery vs slander preventing you saying things considered incitement of the people or insultations. This is difficult, since there are fine invisible lines, that are not obvious or the same to everyone but in practice it works and is reasonable.
- This is not a completely naturally occuring phenomenon. Yes, the automatic suggestions are solely generated by the amount of users that search for a specific phrase, but (big but) a lot of them only search for those because they were suggested to try them (i wouldn't come up with half that junk, that i have searched for, just because the suggestions were so outlandish).
Is it Ok to force google to remove autosuggestions? I'd say yes, but the case at hand would have to be even clearer than for mere search results. It is definitely desirable to censor, (child) pornography from there for example. Mrs Wulff on the other hand has no right to demand this. The tabloids would have to be outlawed long before that.
The only compromise i could imagine would be to make a list of the results/suggestions not shown alongside their frequency accessible somewhere. This wouldn't solve the problem of technical feasability though.
Labels:
freedom of speech,
google,
net politics,
press
Subscribe to:
Posts (Atom)