This post received a lot of comments and reactions, which is great!
It also proved that my little Raspberry Pi Zero W, powered by NetBSD, could handle the load.
Now - to help me test how much load it can tolerate - please boost and react to this post! 🚀
#FediTest #littleFedi #OwnYourData #NetBSD
RT: https://rpi0w.stefanomarinelli.it/objects/01a03e3d-1e73-7928-b396-db17b7f0f60b
Happy 90th birthday to Margaret Hamilton, who led the development of the on-board flight software for NASA's Apollo Guidance Computer. Here she is in 1969, standing next to listings of the Apollo guidance software she and her MIT team produced.
There is currently some excellent discussion on the oss-security list about the impact of AI-driven vulnerability research. Russ Allbery's post is well worth a read:
#ClimateDiary “Above is a fictional weather forecast for August 18, 2050, broadcast by French television in 2014, intended to warn against the disastrous consequences of global warming.
Below is the weather forecast for June 22, 2026.”
(By @jakubwiech on unmentionable)
This brings out super starkly how #ClimateChange has accelerated so much more quickly than we thought even just 12 years ago.
https://github.com/prometheus-community/node-exporter-textfile-collector-scripts/issues/124
I think that settles it.
Je ne sais pas si il y a une bonne pratique à ce niveau, peut être avec debconf, pour éviter les accès indésirables et demander aux utilisateurices de faire attention
Peut-être écouter sur localhost par défaut.
L'avantage du serveur contre les tâches cron c'est aussi de pouvoir changer la fréquence de rafraîchissement directement en modifiant le polling time dans Prometheus
C'est surtout le premier point qui risque de me faire continuer je pense
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126079
https://people.debian.org/~gagath/posts/2025/10/13/opentracker-10-in-debian-now-with-fifos/