If you wanna follow us or stay informed about the latest SteamCalculator news, just add us: http://twitter.com/steamcalculator

If you wonder, what the SteamCalculator might be, to keep it simple: The SteamCalculator is tool for gamer, which can be used to calculate the value of a Steam Account. It basically sums up all your games, which are registered via Steam, and tells you, how much it is worth. Some people call it a new tool for ePenis measurements.
If you do not know what a Steam Account is, you will have no use for the SteamCalculator anyway – sorry.
If you claim yourself to be “gamer”, you should have Steam installed on your PC already. If not…, dude, your missing something!

But let’s get back to the topic. As time passes, people keep sending me feedback with feature requests and even, unfortunately, bugs. Actually, there are quite a lot bug reports coming in these weeks.

• One of the most annoying ones, would be the “my acount is not private” bug. For some reason some accounts only work with profile IDs and not with their custom URLs. This causes the calculator to says it’s an “private” account, even though it’s not.
• Second problem would be all the “broken links”. It is hard keeping track with Valve’s “lets change some IDs”-plans. AppIDs (unique IDs for Steam games) are fine, as long as they are no demo or beta versions, which will be deactivated after a while. But worst of all, are packages. Their subIDs keep changing… damn, got to find a way to fix that.

These are just two bugs, which will be solved soon. A way bigger problem actually is, invalid input by the user. People keep typing their account names (normally a email) or have even an invalid XML profile. Yes, that’s right, it is possible to have invalid UTF-8 chars in your profile, which kills the calculator. I have a total of 22,447 users, which have “broken XML profiles” so far. Even browsers show a unknown character (no, that does not mean, I haven’t installed the font). Well yes, there are ways to work around that problem, but it’s like having keys for a car, which still needs to get hot wired, because it’s keys don’t fit.

In fact it is a user problem. Most of them are “leet kiddies” abusing UTF-8 to literally draw images into their profiles (some look good, though). Or they have friends or joined a group, which is using UTF-8 to create special symbols in their names.
And that is the thing. Some smart people invented “standards” like ISO 10646 to avoid such a mistakes. But who expects kids to know about international standards? Sometimes, it is their computer, which messes everything up. Just to give you a number, to highlight the problem. About 46.2% of all profiles contain an invalid UTF-8 character. Hat means, half of my users can’t even use the SteamCalculator. My biggest goal for second version of the SteamCalcultor, would be to decrease that number, because seriously, who would think it’s his fault, if the calculation fails? No one, right! At the end, they blame me, for doing such a poor job. Well, it’s time to change that.

So, if you have any suggestions for the new version, feel free to post them or, if you wish, send them via email to info [et] steamcalculator [dot] com.
And yes, I am looking for a new fresh design.

Link the protocol and choose an application.

I used this example to let TweetDeck open URLs with Firefox:

Install it right here…

None of these lines are working. Instead I receive mails, complaining about “unexpected EOF while looking for matching “” \ “syntax error: unexpected end of file”.
Referring to the man pages (man 5 crontab), “%” are “newline characters” and needs to be escaped with backslash:

The “sixth” field (the rest of the line) specifies the command to be run. The entire command portion of the line, up to a new-
line or % character, will be executed by /bin/sh or by the shell specified in the SHELL variable of the crontab file. Percent-
signs (%) in the command, unless escaped with backslash (\), will be changed into newline characters, and all data after the first
% will be sent to the command as standard input. There is no way to split a single command line onto multiple lines, like the
shell’s trailing “\”.

In other words, to get it working, add backslashes (\) in front of your “%”s and your fine:

To make sure, you got the right cam, plug it into your computer.
Check if your camera matches my ID by running:

There should be something like this:

If your ID matches, please continue, otherwise you might be lucky and can start installing Gstfakevideo straight away. However this “Howto” was only tested for a QuickCam Messenger with the ID above. For other IDs please take a look here: https://wiki.ubuntu.com/SkypeWebCams

All you need before we start:

Remove the old quickcam_messenger module because it will not deliver the correct colors for our cam. If you do find a solution for this problem, please leave a comment! Thanks. Anyway removing the installed module:

To make sure it is not going to be loaded again we add the following line at the end of /etc/modprobe.d/blacklist.conf

Download the new qcmessener module:

Apply this patch:

Continue installing:

Ignore the “Kernel configuration is invalid.” errors.

Give it a test:

If every thing works go on and install Gstfakevideo:

Create a new file (i.e. in your home directory) called skype.sh and add these lines:

And run:

Now reload the module

Info: run

to view more options.

Create a new file /etc/modprobe.d/qcmessenger.conf and add:

This makes sure, that your webcam will always be /dev/video1 (as /dev/vidoe0 is needed for gstfakevideo) and uses “dblbuf” (correct colors).

Add your account to the “video” group:

Finally fire up Skype by running skype.sh. That’s it!

Please leave a comment if you got some problems or want to give me feedback.

Here is a test image.

Serverseitig
In der /etc/ssh/sshd_config folgende Zeile hinzufügen:

Restart des SSH Dienstes nicht vergessen.

Clientseitig
In der /etc/ssh/ssh_config folgende Zeile hinzufügen:

Persönlich favorisiere ich die serverseitige Variante, da das Verbindungsproblem sowohl client- also auch standortunabhängig heben lässt. Wem der Zugriff auf den Server verwehrt wird, dem bleibt halt nur die clientseitige Version.

If it is not woking after a restart, make sure you installed mingetty.

• 2 cl Wodka
• 2 cl Cointreau
• 4 cl Orangejuice
• 1 small egg-white
• Ice cubs
• 1 cl green Creme de Menthe

Preparation

1. Mix every thing except the Creme de Menthe in a shaker.
2. Strain it in a medium ice filled cocktail glas.
3. Add a dash of Creme de Menthe.

Doch diese Fehler sollen uns nicht nur belustigen, sondern uns Entwicklern auch die Augen öffnen, damit wir solche Fehler in Zukunft vermeiden.