Cities Skylines is a very special game. I sunk way too many hours into this and still enjoy it on occasion.
There’s a nifty plugin that allows to overlay a png image with transparency so one could hobble together a map with imported heights data from e.g. NASA and overlay it with streets, rivers and train tracks from e.g. Google Maps.
This results in recreation of real cities within the engine bringing the hardware to it’s limits.
There are also hundreds of downloadable assets in the workshop.
2019 was a fantastic year for Linux gamers. At the end of the decade we had almost two thirds of the top one thousand steam games rated gold and above in terms of Linux compatibility.
Today I had to access my computer via VNC. There are several manuals how to enable VNC on a typical Linux desktop nowadays. It usually involves some sort of clicking on Sharing => Enable Screenshare and you’re done. It’s really that easy.
How would I do this however remote when I can not access my already running desktop computer via VNC? SSH is enabled on my machines since most of my work involves jumping and tunneling my way through various networks to get stuff done. Just forwarding X was not enough today.
Turns out this is really easy as well. The screensharing feature on my distribution is done with Vino. That’s an integrated #VNC server for #gnome and this is exactly what the user starts by enabling the screenshare feature. Since #Vino is part of gnome it can be configured using
So after enabling the screenshare for testing on my laptop I tested for all existing keys by running this listing:
gsettings list-recursively | grep Vino
It’s really short and basically all settings are no-brainers. Only the password had me wondering but it turned out this is just base64 encoded (and also optional). All that is left is running the
vino-server binary in the end. This needs the correct environment variable
$DISPLAY set since our target is a running X session. This one we can determine by executing the command
w and looking for the TTY in use. Hint: It’s
:1 in this case.
beko ~ w 20:35:15 up 5:12, 1 user, load average: 1,92, 2,33, 2,37 USER TTY LOGIN@ IDLE JCPU PCPU WHAT beko :1 15:24 ?xdm? 2:02m 0.00s /usr/libexec/gdm-x-session --run-script /usr/bin/gnome-session
Oh and you should also not connect with the X11 forward option
-X because running the
vino-server with this will result in some really funny endless picture in picture mode that I did totally not try out by mistake 😉
Now that I had all the information I needed I hacked together this little script that does this more or less automatically so I can forget about this again [and look it up two years later in my own blog]. It’s really crude and your mileage may vary. It does not account for multiple users or multiple running X Sessions:
export DISPLAY=$(w -oush | grep -Eo ' :[0-9]+' | uniq | cut -d \ -f 2) echo "Display is $DISPLAY" gsettings set org.gnome.Vino require-encryption true gsettings set org.gnome.Vino use-alternative-port false gsettings set org.gnome.Vino disable-background false gsettings set org.gnome.Vino alternative-port 5900 gsettings set org.gnome.Vino icon-visibility 'client' gsettings set org.gnome.Vino disable-xdamage false gsettings set org.gnome.Vino authentication-methods "['vnc']" gsettings set org.gnome.Vino prompt-enabled false gsettings set org.gnome.Vino require-encryption true #pw is just base64 so basically just echo -n 'awesomeness'| base64 gsettings set org.gnome.Vino vnc-password "YXdlc29tZW5lc3M=" gsettings set org.gnome.Vino view-only false /usr/libexec/vino-server & export VINOPID=$! echo "Try vnc://$HOSTNAME:5900/" echo "vino-server pid may be $VINOPID"
And that’s it. There is no root or sudo involved.
Don’t forget to
kill the pid when done 🙂
Evaluating micro.blog finally myself. All I know of it before was from presentation or FAQ and I recommended it a lot already as your one-stop #Indieweb solution. Time to take a closer look myself. My first trial expired because I never finished the sign up process when confronted with adding credit card information upfront. I hear this is not or no longer required and @manton, creator of all this, kindly reset my trial.
So far I’m pretty impressed. Oh and it’s also powered by #Hugo – my latest favourite toy I started playing around with 😀
This is a good read about SMTP and why it’s a bad idea to roll with the big 5:
We’re currently at a point where it is even difficult to run your own mailserver because small mailservers tend to end up on some blocklist thanks to “bad neighbourhood”. That’d be ips “next” to you. Getting removed again – even for no reason – is a PITA, because there is no unified way of doing so. Happened again and again and while the big 5 won’t bother blocking entire ranges most of the spam bouncing of my own mailserver is indeed from the big mailserves themself. So nowadays I simply stopped caring at all.
My advice for affected people is the same: Use a smaller provider or even run your own. Do not use the mailservices of the big companies. It’s not that hard. Even a consumer NAS can do it.
Dieser Tage dem Housekeeping zum Opfer gefallen: Die Parteizugehörigkeit zur #piratenpartei
Mit dem Wegfall meiner 4-stelligen Mitgliedsnummer 34** erinnere ich mich gerne an die Anfangszeit. Die für mich so wichtigen Kern-Themen sind inzwischen in der Gesellschaft angekommen, womit sich meine Gründe für mein damaliges Engagement erledigt haben. Ich bin davon überzeugt dass vieles deutlich schlimmer hätte kommen können.
Inzwischen ist immerhin ein gewisses Bewusstsein für Datenschutz und Privatsphäre entstanden, was sich in Gesetzen wie dem #GDPR (DSGVO) niedergeschlagen hat.
Wer sich nicht mehr erinnert, wie die Netz-Politik damals in Deutschland aussah, kann das Gedächtnis zum Beispiel im Archiv des AK-Zensur.de auffrischen.
Übrigens: Ich bin sogar weiterhin mit dem Parteiprogramm ganz einverstanden. Trotzdem fühle ich mich nicht mehr zugehörig und habe den Anschluss verloren. Damit ist das alles wieder bei Theater angekommen – und hier findet man den höchsten Unterhaltungswert gerade anderweitig *zwinkersmiley.
There’s a thing that puzzles me every time I visit some doctor, or hospital or dentist. You get it. Everywhere you get to sign a #GDPR (or refuse to, like I do) and next thing happening is you’re sited in a room waiting for your turn. With a computer. Usually with your patient file already opened and on screen.
There is _so_ much you could do now. Like editing, opening other files, install a keylogger or some other device to the net – even wifi. WPS button is on the router next to it – default password on it’s back. System is in most cases horrible out of date and even if the screensaver is on it’s password is usually short, never changed and can be easily guessed or observed. And that’s all in a very sensitive setting. I observed this in various places now and when called out I get that “We’re not computer experts” shrug.
…but you signed that GDPR so all is [probably] good.
Am I the only one bewildered by this?