happx x mas

hope you all had some good time with family, friends or geeks. were going low for 2011. best time to put new effort into the blog.

that auto update for wp went surprisingly well and im trying out the new wp theme twenty-eleven. not so individualistic but still sweet. editing with an android pad is a bit crappy and even with the app its only an inch better. So i leave it for today with a little happy xmas quote. With an extra x.

 

 

 

dont copy files to uploads/pics/ in TYPO3

there are some reasons why TYPO3 copies every file into the well known uploads/pics/ folder that you “reference” in the backend in content elements. after copying the file there, it´s (ordinarily) protected from being deleted by the newb user or changes. if the editors changes stuff, the file is copied again after save with the _01 appendix. that leads to a bunch of issues like orphan files. theres some solution for that, but it is best to prevent that for good — if you like.

$TCA['tt_content']['columns']['image']['config']['internal_type'] = 'file';

that put into extTables.php or so sets that the file is used as is. the file is linked to where the user did upload it and no file reference is created.

connect to a webdav with windows 7

if you try to enable the webdav (web based distributed authoring and versioning) service with a linux server and apache2 it´s a piece of cake. the only thing you need to keep in mind is to make it ssl and auth_digest. this is so that windows clients can connect to the thing. theoretically. after all my unsuccessful attempts with the wizard ( i tried it like a hundred times with all different url formats ) a desperate try with net use made it work!

net use z: \\subdomain.domain.tld@SSL:443\webdavfoldername

will ask for a user and a password to gain access and to mount the webdavfoldername (your webdav alias in apache´s virtualhost conf) to drive letter z:

this is a hell of a lack that windows 7 has, but of course webdav seems to be an anathema to microsoft.

useful addendums to the command above are /persistent:yes and /User:user password and i hope it helps you save worthy hours.

know more about the requesting browser

propably you´ve heard about the modernizr javascript which tests the requesting browser for css3 and html5 capabilities and then sets classes to the root <html> element which your apes css coders use for selector queries. no more conditional hacking. that sounded so good that i stuck it and found this little post about server-side modernizr.

another handy javascript piece is yepnope. best is: both scripts join forces and reduce http requests and, thus save the world!

all in all this is great news for systems like TYPO3 that already provide conditions for environment variables like the client´s browser family, the os and so on. wouldn´t it be a nifty thing if the system chose the template to provide depending on the client´s capabilities to handle them?

simple way to access websites that seem to be censored

fortunately, i find myself living in a country that appears to accept freedom of speech, freedom of data. while i´m quite aware that this ideology is not to be supported in future concepts to keep masses controlled i find every citizen should try to gain knowledge in bypassing common web censoring methods. how do you think about that? i find this very interesting and simultaneously hope that the information in the web remains free.

bypass ip locks

if you happen to sit behind an ip barrier that i.e. stops wikileaks you might bypass it in ways (free of charge) like these

  • use translate.google.com and open the page that is censored, if google is not cooperating with the bad guys ;)
  • use compressor services like loband if you can live with the html only version
  • use proxies –> ixquick allows you to use a search result in proxy manner
    • use ixquick search engine and search for the censored page
    • click “proxy” behind the url of interest, then ixquick will serve as proxy

ixquick screenshot

simple thing to do and it does not cost anything. of course you could set up tor to communicate privately (hence making ip resolving useless).

another approach would be to ask a service like web2mail to compress the website you want to see and let them send it to your email box. then you see the requested page after unpacking the file you received. clicking a link would result in asking web2mail for the target and another email.

All these ways were told during a talk at this year´s sigint that you can watch at media.ccc.de

slept well?

recently i reactived my smartphone from it´s oblivion and hence all the mobile activities were a bit cutoff during the last weeks. let me say months, but that was not only the issue with the smartphone. damn cell battery is becoming weak a half year after purchase.

i thought about the virtual effigy most people produce. fortunately, my activites mostly stay controlled and no excessive drinking bout became evident (afaik) in the network (right now). don´t know if that is the main aspect of data security but the trail we leave in the sand is quite persistent. wow, i just wanted to write down that my blog is underpopulated which is a pity, and i end up contemplating about the virtual identity issue.

give me a few posts to habituate myself to blogging. nevertheless, i´m cool with 1-to-n communication (where n includes you, whether you´re bot or human). leaving us defining when an entitity will be able to extract the semiotic meaning of itself, i´d rather go now and have some real life – beginning with a tasty shisha.

and i hope my smartphone will at least stand by for the next few hours, calling that a “milestone”.