Tobias Frech

Whenever I use an #LLM it really annoys me it's offering multiple choices. So it puts the burden of checking and filtering out invalid responses back on me. It's practically impossible to follow a chain of thought in a conversation. Why did they call it a chat? Probably because it will always stay on the surface of things and never turn into a thoughtful discussion.

@vince@infosec.exchange it's not a private IP space. Just a regular IP the cloud provider uses for their VMs. The IP is specific to our VM. We once had to request it to be removed from a block list. But that only happened once in three years.

@Bibliothecaris@social.edu.nl We can't provide direct feedback for these products but we have been running and are running our own outgoing SMTP server for years now. Contrary to popular believe it works even with MSFT, Google and other email providers. You have to have SPF, DKIM and DMARC correctly set up. There are important details like the reverse DNS entry of the sending IP matching all this and so on. But it is doable. There are free services to test your setup and provide valuable feedback.

@energisch_@troet.cafe @BioSchweiz@troet.cafe ich denke der Grundgedanke ist, dass man ein Netz hat, durch das sowohl Energie her als auch abtransportiert werden kann. Gespeichert könnte es zum Beispiel in Eisspeichern oder tiefen Kavernen werden. Im Übergang zwischen fest und flüssig lässt sich auch viel Energie speichern. Der Trick ist, dass mit Wärmepumpen außerhalb dem Bereich gearbeitet werden kann, den wir sonst zum Erwärmen oder Abkühlen aus der persönlichen Erfahrungen kennen.

@SonstHarmlos@franken.social Boah, die Gegner haben Argumente! Vielleicht lohnt es sich, zuzuhören? Rechenzentren müssen eine unterbrechungsfreie Notstromversorgung haben. Dazu könnten sich doch auch Batterien eignen. Wieso das nicht mit einem netzdienlichen Betrieb der Batterie kombinieren? Verehrte Projektplaner, versteht doch bitte "nicht fossil" als langfristig hilfreiche Randbedingung.

I got a quite extensive answer back from a question to an LLM. So I went and checked the docs on the suggested solutions. In the docs I find this gem:
> Consequently, j.u.l. to SLF4J translation can seriously increase the cost of disabled logging statements (60 fold or 6000% increase) ... Please note that ... it is possible to completely eliminate the 60-fold translation overhead for disabled log statements with the help of LevelChangePropagator.

@icing@chaos.social yes, it's update and fixed in security for the stable distributions now. The notification was sent out at Wed, 06 May 2026 15:04:16 +0000. It's still an excellent example of a problem which should be solved. Releasing CVEs should _not_ be delayed until every distribution or product incorporating the components affected has updated.

@icing@chaos.social The Docker Official Image of httpd 2.4 has been updated to 2.4.67 just two days ago because of this CVE. And still nothing about this CVE announced on https://www.debian.org/security/ #httpd #debian

Time to relax from a busy week and a busy day today. Thanks to everybody at #jcon2026 for the great days filled with a lot of talks with great community folks. And also thanks to my #Java friends @ #iJUG and all the #JUG organisers.

@danirabbit@mastodon.online Recently we were discussing if it's more like asbestos or like plastic (and microplastics). How much thought should be put into stuff like this before it's rolled out globally? Can we simply go ahead and try to fix the problems later?

@jwildeboer@social.wildeboer.net @ArneBab@rollenspiel.social @zymurgic@mastodon.online can confirm, this works surprisingly well and there are tools to help you with setting it up, debugging and monitoring it.

@mre@mastodon.social excellent points! If I am new to a team I first try to "Build a Reputation". It's an excellent basis to then "Say 'I Don’t Know'". By this I hope to break down the barrier so that the team is enabled to learn new things and come up with new and better solutions.

@JavaLandConf@ijug.social Today is the last day to submit for the CfP for #javaland2024 Don't miss the opportunity to visit the Nürburgring!

@javaaktuell@ijug.social Zu Markus‘ Eclipse Corner habe ich noch diese beiden Links mit der Versionsmatrix zwischen #JakartaEE und WildFly bzw. JBoss: JBoss EAP: https://access.redhat.com/articles/113373 WildFly: https://docs.wildfly.org/ Und ja, JBoss EAP 8 ist noch in der Beta und soll in der ersten Hälfte 2023 final werden. Mit Subscription dann auch mit Support.