And one last batch of travel pictures for today: I liked writing the image descriptions for these, they are a good place to talk also about how the pictures came about and what they are showing: not just a river, a dusk, a city.
These were taken before the other ones in this thread, in Poland and Riga on my way south.
Do you remember the Slovenian floods last year? I'd spent the floods in Ljubljana in a great hostel and joined some family afterwards in the north to hike in the national park.
It was a pleasant surprise how easy it is to get to hiking trails in the national park. 2€ bus fare to the park itself and free shuttle service within it - and the best thing about it: the national bus service in Slovenia is owned by DB.
> Um die Vorteile von Interfaces (multiples Subtyping) und abstrakten Klassen (Bereitstellung einer Implementationsbasis, Schablonenmethode) zu verbinden, ist es gängige Praxis, ein Interface bereitzustellen und mit einer Basisimplementation in Form einer abstrakten Klasse zu ergänzen.
Finished my #website for now. After setting up #nixos on the server, hardening #SSH access and writing a static site with #Pelican, I've now finished the last piece: a mirror of the my most important account's #RSS/#ATOM feeds on the site, updated daily.
Either this post and the article referenced was perfect or people just aren't engaging with the contents of the posts here like they used to.
When I posted this article originally, there was a lively discussion here that led me to summarize some of the very good and interesting points made back then in a follow-up post.
Now, in the wake of a disaster caused by the problem this article is addressing, we don't have the time on this network anymore to engage with ideas beyond a mere press of a button?
I'm not accussing anyone who boosted this or favorited this individually - if I was I'd have to find myself guilty as well. It is just a sorry development to me - perhaps there is just too much "content" on here by now for anyone to meaningfully and critically engage with any single piece of it.
https://discuss.coding.social/t/unionize-free-software-found-software-guilds/59 the recent #XZ disaster has prompted me to reread my own article from two years ago next month on "Free Software Unions". While I'd put some of the details in there differently today, I think the core point still stands: that free software maintainers are vulnerable to exploitation, both from Big Tech and, as is now evident, malicious attackers. And that the only way to protect them is to join into mutual support, solidarity groups.
Due to the #XZ dependency vulnerability, I've been looking for lists of projects that need maintainers and contributors. I found this website, which appears reasonably up-to-date: https://seeking-maintainers.net/
But both the list there and the GitHub maintainer-wanted topic appear far too small for the size of the problem.
Haben #ICE Züge eine gut genuge Klimaanlage, um bei Vollauslastung die CO2 Konzentration unter einem kritischen Level zu halten? Ich fühle mich nicht so, als wäre dem so.
#GDPR / #DSGVO Question: if I'm filmed by CCTV, that material would contain both my appearance and location. Would this material thus be considered personally identifiable information under the #GDPR and could I request this material from CCTV operators, such as the #DB or #ÖPNV? And would they then have to search all there material they have for me and provide me those recordings?
Just a thought: the mindset exams train me on is actually very unhelpful and dangerous when doing actual work.
When having an exam, oral or written, everything I do must be right and when I make a mistake, I'm incentivized to argue and spin the mistake to make it look less like a mistake, instead of accepting it and learning from it.
When there are actual stakes involved though, not just the whims of an examiner to please, this same attitude is not just counterproductive, but outright dangerous. Being open about mistakes is a basic prerequisite to working in a team, with clients or in a company and it's the absolute opposite of what I need to do when writing exams, papers, etc.
I decided to use #Pelican as #SSG, because it uses #Python and #Jinja2, so I didn't need to relearn and was able to concentrate my efforts on modifying the theme and removing all JS and CSS I didn't need.
Next I want to experiment with #HTMX to integrate some dynamic elements into my website.
From now on, until I stop paying for the domain or the VPS, my website will be: https://jorisgutjahr.eu
I was wrong. I'm running into an issue with my ssh config. I get some issue with ssh public key authentication: When I try to connect, pubkey auth fails and I have to use a password (which I want to eventually disable).
On the client it fails in sign_and_send_pubkey stage saying agent refused operation.
On the server it fails because the host key type "they" sent are not supported.
The weird thing is: neither my client nor the server use the host key types listed in this log message - so I'm pretty much at the stage of trying to look into openssh's source code to figure out the exact conditions for this error and get pubkey ssh auth working.
I'm currently trying to setup my own VPS to run a static website and some other services, mostly for personal use. I was tired of using the pages feature of various forges for this and wanted the flexibility to also run some stuff server-side.
Do any of you have a suggestion for what to do with a small VPS like that?
Das ist wirklich super Timing. Deshalb ist es ein Problem, wenn wir unsere wichtigsten Dokumente nicht runterladen können sondern nur online benutzen können.
I think inline #documentation is an important tool to making software readable. It makes software maintainable, encourages future development and makes it easier to join the project as a developer.
This is why I advocate for #mastodon to start encouraging inline documentation with #yardoc, requiring it for any new PRs and serving this API documentation on joinmastodon.org.