Tuesday, October 24th, 2017 | Gadgets, Insights, Linux, Tech-savvy | No Comments
Today I’d like to share a nice project that I stumbled upon: Pi-hole®: A black hole for Internet advertisements.
Basically it is a small DNS proxy that filters DNS queries based on lists of ad and tracker sites.
It’s pretty kewl, as you just set it up once and all your devices on your LAN will benefit from it.
I have been using Pi-hole (default settings/lists on Raspbian Strech) for a couple of days now without problems and a noticeable better internet browsing experience.
Give it a try and put your old Raspberry to some use!
Tuesday, August 29th, 2017 | Insights, Linux, Misc, Tech-savvy | No Comments
Ausgangslage: Ich mache Podcasts. Ich arbeite mit Linux. Ich möchte gerne in das iTunes Podcast Verzeichnis. (Eigentlich will ich ja nix außer meinen RSS Feed in ein Verzeichnis pushen…)
Kollege: “Um bei iTunes deinen Podcast ins Verzeichnis zu bringen brauchst du kein iTunes auf deinem Rechner, nur ‘ne Apple-ID.” (Source)
Na gut, prima, ich lege also eine Apple ID an (im Web) und versuche es.
Ich werde mit einer Fehlermeldung abgewatscht:
“Podcasts Connect erfordert einen iTunes Store-Account.”
Darunter ein Link: Zum iTunes Store
Ich klicke auf den Link, der schlicht auf itunes.apple.com verweist und kann mich – oh Wunder – mit meiner Apple ID dort anmelden. WTF? Also habe ich doch einen iTunes Store-Account?! Apple, ich bin verwirrt.
Ich google also die Fehlermeldung. Dort lese ich, dass man sich in iTunes und nich auf der iTunes Seite anmelden muss. Geil, wie dass die Fehlermeldung “Podcasts Connect erfordert einen iTunes Store-Account.” offenbart.
In iTunes soll man sich anmelden und dann dort ein zwei Informationen zu seinem Account hinterlegen. Nun gut.
Meine Nerven liegen also bereits leicht blank als ich zu einem Kollegen mit Mac gehe und mich in iTunes anmelde. Super. Der Wizard zur Anmeldung will dann direkt eine Zahlungsmethode von mir. Es gibt keine direkte Möglichkeit das zu umgehen. WTF again?! Ich fühle mich ins Jahr 2009 zurück versetzt, als ich schlicht einen iPod Touch in Betrieb nehmen wollte, was, ohne Kreditkarte, nicht möglich war. Dürfen Menschen ohne Kreditkarte keine iPod nutzen?
Fick dich Apple! Mir geht deine Philosophie in vielen Bereichen so gegen den Strich, dass ich im Strahl kotzen könnte. Ich mag keinen Zwang, vor allem nicht, wenn jemand meine Kreditkarteninformationen haben will. Dann spiele ich halt wieder mit den Open Source Schmuddelkindern. Da fühl ich mich sowieso wohler. Und sag nicht ich würde es nicht alle Jubeljahre mit dir versuchen, aber wir zwei passen anscheinend einfach nicht zusammen.
Wer jetzt meint, dass ich selber schuld bin und dass das bei Apple halt so ist: ich habe vor einiger Zeit einen YouTube Kanal aufgemacht (icanplaystayshun), einfach mal so zum Spaß. Mit einem Google Konto. Schnell, kostenlos, unkompliziert.
Hat Google ein Podcast Verzeichnis? Scheiße! Wieso bin ich da nicht vorher drauf gekommen!? Das guck ich mir mal an!
Edit 1: 30.08.2017
“Podcasts are not available in your country
Podcasts are coming soon to Google Play Music, but unfortunately, they’re not yet available in your country.”
Und Google Play Music kann man auch in der kostenlosen Variante nicht ohne Zahlungsinformaitonen nutzen.
“Our music deals require that you have a form of payment on file to confirm your country of residence as music rights vary by country”
Also auch nicht besser. Schade. Wenigstens geben die einen “guten Grund” an. Auch wenn mein freier Podcast mal nix mit “music rights in my country” zu tun hat. Hallo? Podcast! Selbst produziert! Ich will doch nur ins Verzeichnis! 🙂
Edit 2: 30.08.2017
Werde mir jetzt noch Stitcher ansehen. Dann habe ich aber die Schnauze voll 😀
So, das scheint geklappt zu haben. Die wollten auch recht viele Infos (Adresse) und die Terms und Conditions haben es auch in sich. Garagen Sprech ist nun dort in der Approval Phase und Dennis tötet mich beim nächsten Cast weil ich wieder in Anglizismen versinke.
Was ein Kack, nur um mal so ‘nen RSS Feed publik zu machen…
Edit 3: 31.08.2017
Wir sind online! 😀 Stitcher hat den RSS Feed nun in sein Directory aufgenommen.
Thursday, August 24th, 2017 | Insights, Linux, Quirks, Tech-savvy | No Comments
I was about to release another “post-installation tasks” post when I thought it might be a good idea to focus on a specific topic first: Hi DPI (aka 4k resolution monitors) and how Fedora, my weapon of choice, is performing. Fedora ships with Gnome 3 on Wayland. So this will be my starting point.
Set-up Gnome to use Hi DPI mode
This sounds to easy. But rest assured, this is only the first general steps as a lot of apps, even Gnome (3.24.2) itself, does not respect / support this setting consistently. (here are two native Gnome examples of mixed Hi Res and Low Res components Example 1 Example 2)
Still, for me the overall experience is finally worth setting up a Hi DPI desktop environment.
Install Gnome Tweak Tool
$ sudo dnf install gnome-tweak-tool
Fire it up, go to “Window” and set the Hi DPI mode to 2x. (In the near future Gnome wants to support arbitrary scaling factors, on a per device i.e. monitor basis. Looking forward to that!) You may need to log in and out of your session for the setting to take effect.
Update 25.08.17 There is another Gnome setting, and after that Gnome itself renders just fine! Bliss! Thanks Michael Reinartz for pointing this out!
$ gsettings set org.gnome.desktop.interface scaling-factor 2
Apps that work well out of the box (on my machine)
and after the “Update 25.08.17” hint:
Audacious 3.8.2 (Winamp Interface)
Apps that scale well after some handiwork
Chromium 60 (maybe Chrome – I don’t use it right now)
Chromium needs a special parameter:
--force-device-scale-factor=2, just add it to a copy of the .desktop file in your personal user space.
cp /usr/share/applications/chromium-browser.desktop ~/.local/share/applications/
Put that parameter just behind the executable:
... Exec=/usr/bin/chromium-browser %U --force-device-scale-factor=2 ...
eclipse 4.7 Oxygen
I use a launch script for eclipse, just add
export SWT_GTK3=0 to it. The
export UBUNTU_MENUPROXY=0 fixed a problem with disappearing menus in eclipse. I can omit the entry without problems, I just leave it here in case you might need it.
#!/bin/bash export SWT_GTK3=0 export UBUNTU_MENUPROXY=0 ./eclipse/eclipse -showlocation
Apps that do not scale at all (yet)
They say you need to recompile it with
There are themes available with hi res icons but I will just wait for 2.9 as it should support Hi DPI natively.
At least the full screen mode looks nice 😉
As you can see Hi DPI is still work in progress. Still, I figure Hi DPI usable by now and will not go back. Looking at a “printed screen” is just too amazing.
Hope I gave you some insights and if you have something to add just leave a comment. Thanks!
Friday, July 21st, 2017 | Activities, Food, Insights | No Comments
A friend of mine told me there is something like “reverse bbq” – first, cook the meat in an oven at the desired heat and when it is done let it kiss the sizzle zone of your bbq. Okay, this is my try.
I was shopping and saw this T-Bone steak.
I had a late night dinner. I did not like it too much, I guess the beef steak is still my favourite meat. Right now I am fed up with red meat. I opt for Schinken Krakauer again at the moment. Yummy left-over sausages!
Thursday, July 6th, 2017 | Activities, Food, Insights | No Comments
This time I just bought a steak and grilled it. No frills.
The steak. A regular beef steak, I thought I can hardly foobar the most standard beef available.
Grilled. Seasoned. Served. 😛
Medium rare. Yes! \m/
It worked. Even though the meat quality itself was somewhat subpar (supermarket meat counter) the outcome was just what I wished for. The days of shitty minute steaks from the discounter are definitely over. I may stick to the occasionally sausage though (just love my Schinken-Krakauer) but no more cheap meat for me.
Saturday, July 1st, 2017 | Activities, Food, Insights | No Comments
I recently attended Santos Pure Beef seminar – which was great yet I can hardly say I was able to absorb all the meat cutting techniques let alone become a bbq sensei. This is my first attempt to bbq something else than sausages and minute steaks.
The meat I wanted to buy was not available (Teres Major), so I bought the cheapest part that still looked decent, a “Bürgermeisterstück” aka Tri-tip – in case I foobared this one it would not be too much of a loss. That whole lump cost €8.99.
The seasoning was easy. Just some salt and pepper.
Maxed out my grill at 350 °C (~660 °F).
Cross grillage brandings. (Couple of minutes each side)
So, this is the result. Looks great from the outside. (30 minutes, indirect, one burner on minimum flame ~ 120 °C)
Unfortunately I overcooked it. It was in between medium well and well. Bummer. But hey, it was my fist try and the taste was still very good 🙂 Next time I might only bbq the outer parts and use an oven at ~80 °C for maybe 20 min to finish it.
I saw this random add on Facebook, some 5 piece Star Wars canvas depicting Lord Vader. Loved it. Honestly, I love personalized ads, as they show me stuff I really like.
This time I fell for a fraud. It seemed legit, I guess, there was PayPal to pay, free worldwide shipping (this should have rung a bell already) and 32.99 USD seemed a good deal.
Bought and paid October 1st.
Contacted seller November 6th.
Hi there, I am still waiting for my “STARWARS 5 PIECE CANVAS LIMITED EDITION”. Purchased at first of October.
Is there anything wrong?
Never got a reply.
Double checked the website November 16th.
Okay, seems I was to naive to trust in this bargain. Contacted PayPal, hope I will get my money back.
So, please, if the offer looks the least dodgy think twice. It can happen, even to old online veterans. When in doubt use a service like PayPal who might give you another layer of buyer protection.
Friday, October 28th, 2016 | Insights, Music, Tech-savvy | 1 Comment
First, let me introduce what transparency in data compression means, excerpts from Wikipedia:
In data compresion and psychoacoustics, transparency is the result of losy data compresion acurate enough that the compresed result is perceptualy indistinguishable from the uncompresed input. In other words, transparent compresion has no or imperceptible compresion artifacts.
Transparency, like sound or video quality, is subjective. It depends most on the listener’s familiarity with digital artifacts, their awarenes that artifacts may in fact be present, and to a leser extent, the compresion method, bit-rate used, input characteristics, and the listening/viewing conditions and equipment. Despite this, sometimes general consensus is formed for what compresion options “should” provide transparent results for most people on most equipment. Due to the subjectivity and the changing nature of compresion, recording, and playback technology, such opinions should be considered only as rough estimates rather than established fact.
Judging transparency can be dificult, due to observer bias, in which subjective like/dislike of a certain compresion methodology emotionaly influences his or her judgment. This bias is comonly refered to as placebo, although this use is slightly diferent from the medical use of the term.
To scientificaly prove that a compresion method is not transparent, double-blind tests may be useful. The ABX method is normaly used, with a nul hypothesis that the samples tested are the same and with an alternative hypothesis that the samples are in fact diferent.
In case you managed to read the above paragraph and are still here: congratulations! How do you feel? Slightly nauseous? Even annoyed? Maybe. The above text has been slightly altered. I “compressed” it by removing all double consonants. You can still read it, sometimes you might even not realize the change from the original text. Most probably you found a few (annoying) errors. Keep in mind how reading that text made you feel.
I was talking to a friend of mine the other day, and he explained to me why he dislikes audio compression with an easy analogy. Listening to compressed sound can be compared to reading text that is missing characters, that you might not even notice. Your brain will fix the issues and you will be perfectly capable of reading the text. Still, your brain has to work more than it would reading the unaltered text. Same goes for audio compression (read psychoacoustics). Lossy audio compression still tries to sound like the original (i.e. retaining the perceived quality) by removing things you are not meant to hear anyway. Easy example: just after a loud sound, like a hi-hat hit, other frequencies, that you cannot hear anyway due to this high impact noise, will get removed (masking effect). Sounds legit. So throw it away. Still, compression will make your brain, your perception work harder to fill these gaps of information. Maybe. Most probably. Like reading the above text made your brain work harder. Reading the foobared text was less enjoyable. So why should you listen to music that will subconsciously decrease the “enjoyability” of listening instead of feeding your ears the real deal?
Finally, I have an easy explanation why you should not listen to (badly) compressed music but stick to lossless compression like flac or the original. It simply will be more enjoyable for your ears and brains, even though you might argue the super-duper encoded files your were listening to before were “transparent”. Maybe they are more likely entities of unwitting torture 😉
For me the days of lossy compression are not over. That would be naive. Still, I will try to listen more and more to the best possible source at hand (as hard drive space is not really and issue any more). I already encoded my mp3s 1 or 2 steps “higher” than the “transparent” setting is for me (e.g. in case you hear no difference in -V 3 compared to -V 4 go for -V 2). I enabled high quality streaming in Spotify (i.e. ogg Vorbis q9 according to Spotify). Right now I plan to build an audiophile music player (Raspberry Pi, Volumio, DAC, Reclocker) and re-encode my favorite CDs using flac. Even though I might not actually hear any differences if will just make me feel better listening to it. A placebo? Maybe. It’s one I will take. Happy listening!
Thursday, September 29th, 2016 | Gadgets, Insights, Tech-savvy | No Comments
I cannot write about this topic any more, so I let my HDMI cable tell the story.
Tuesday, September 13th, 2016 | Insights, Linux, Tech-savvy | No Comments
I guess everybody who ever came across a *nix prompt knows the infamous “rm -rf” command and only uses it when it’s really save. Well, pretty much save and then whoopsy … files gone. So here goes my latest foobar.
I wanted to create a symlink from my small home partition to a big data portion for my gnome-boxes, as disk images tend to get big. So I created and “cd”ed into the destination folder:
and checked whether the dir is empty thus suitable. It was.
So now I symlinked the current directory to ~/.local/share/gnome-boxes
ln -s . /home/nick/.local/share-gnome-boxes/
So far so good. I “cd”ed into the original folder to check whether the link was created okay, but it only showed something like
gnome-boxes -> .
gnome-boxes -> /bfd/gnome-boxes/
WTF? The . is a reference to the current directory which was /bfd/gnome-boxes at the time I used it. Hmm, the ln took that dot pretty literally (which is obviously my fault).
So, I wanted to get rid of that wrong symlink. First, as the “directory” gnome-boxes was a symlink, i.e. a file, I tried to simply delete it with rm. That was when the real fun began.
You can test this behavior, create a test directory, that holds a file (touch file) and a directory (mkdir dir). Then go create that bogus symlink (ln -s . ./test)
drwxrwxr-x. 2 nick nick 4096 13. Sep 12:50 dir -rw-rw-r--. 1 nick nick 0 13. Sep 12:53 file lrwxrwxrwx. 1 nick nick 1 13. Sep 12:53 test -> . [nick@localhost 1]$ rm test/ rm: das Entfernen von 'test/' ist nicht möglich: Is a directory [nick@localhost 1]$ rmdir test/ rmdir: konnte 'test/' nicht entfernen: Not a directory [nick@localhost 1]$ rm -rf test/ [nick@localhost 1]$ ll insgesamt 0
All gone 🙂
Not only the dir was gone but basically my whole ~/.local/share/ directory was empty. I symlinked gnome-boxes to ., so the current dir, thus rm -rf gnome-boxes deleted the current dir. Eff.
How to prevent this.
* Use unlink. It’s saver as it only calls the unlink function and cannot delete regular files.
* Don’t “tab” complete your commands. A simple “rm gnome-boxes” without the trailing slash would have done the job and saved me the re-installation. Luckily this is done in less than half an our with modern distros, still, I felt like an idiot. Lesson learned.
This was done with a super smart ASF member behind me, whom I showed the funny “Is a directory / Not a directory” error messages. We had a good laugh after deleting my share folder. Facepalm deluxe!
- October 2017 (1)
- August 2017 (2)
- July 2017 (4)
- November 2016 (1)
- October 2016 (1)
- September 2016 (2)
- March 2015 (1)
- December 2014 (1)
- September 2014 (1)
- August 2014 (1)
- February 2014 (1)
- January 2014 (1)
- December 2013 (1)
- November 2013 (1)
- July 2013 (1)
- May 2013 (3)
- April 2013 (1)
- March 2013 (1)
- February 2013 (1)
- January 2013 (1)
- December 2012 (3)
- November 2012 (1)
- October 2012 (3)
- September 2012 (3)
- July 2012 (1)
- May 2012 (1)
- April 2012 (1)
- February 2012 (7)
- January 2012 (1)
- December 2011 (2)
- November 2011 (4)
- October 2011 (5)
- September 2011 (3)
- August 2011 (3)
- July 2011 (2)
- June 2011 (4)
- May 2011 (1)
- April 2011 (2)
- March 2011 (2)
- February 2011 (2)
- January 2011 (6)
- December 2010 (2)
- November 2010 (5)
- October 2010 (7)
- September 2010 (13)
- August 2010 (6)
- July 2010 (4)
- June 2010 (3)
- May 2010 (3)
- April 2010 (2)
- March 2010 (2)
- February 2010 (1)
- January 2010 (1)
- December 2009 (1)
- November 2009 (2)
- October 2009 (5)
- September 2009 (1)
- August 2009 (3)
- July 2009 (5)
- June 2009 (5)
- May 2009 (6)
- April 2009 (3)
- March 2009 (3)
- February 2009 (2)
- January 2009 (1)
- December 2008 (9)
- November 2008 (15)
- October 2008 (15)
- September 2008 (13)