Ángel
@angel@triptico.com
Location: 40.4235492,-3.6617828
81 following, 93 followers
If you use "AI" generated illustrations on your blog, I immediately suspect you also use "AI" like ChatGPT or DeepSeek to write your blog entries and I will close the browser tab. Ain't nobody got time for slop :)
Asteroid name: 2024 YR4
Probability: 3.07%
Impact date: 2032-12-22.59
Asteroid name: 2010 RF12
Probability: 10.24%
Impact date: 2095-09-05.99
Asteroid name: 2017 WT28
Probability: 1.10%
Impact date: 2104-11-24.69
Source: NASA/JPL Sentry Data API
University professor, circa 2010 : You can’t trust Wikipedia. You cannot use it for your essay.
University professor, circa 2025 : Here are powerpoint sildes on how to use ChatGPT to do your essay.
Personal conclusion: the only problem with Wikipedia was that it was not corporately owned and that it had no marketing budget.
Asteroid name: 2024 YR4
Probability: 2.21%
Impact date: 2032-12-22.59
Asteroid name: 2017 WT28
Probability: 1.10%
Impact date: 2104-11-24.69
Asteroid name: 2010 RF12
Probability: 10.24%
Impact date: 2095-09-05.99
Source: NASA/JPL Sentry Data API
«Troquelar es crear el vínculo entre el mastín y el rebaño».Lo añado aquí después de haber visto el vídeo, para que los que no tenemos ni idea entendamos a qué se refiere (porque la RAE solo habla de cortar con un troquel).
all of David Lynch's feature length works are now available at the internet archive
https://archive.org/details/filmography-david-lynch/
i'm especially noticing that the unsold pilot for the TV series version of Mulholland Drive is in that batch. 👀
It gives a daily report of those asteroids with a reasonable probability of crashing into Earth, in case you are not already afraid enough of the future. Of course, using #snac, what else.
It takes its data from a very cool NASA site, so (again) in these days of uncertanty, I'm not sure how long will it work.
Everyone, take care, and have a great week.
Asteroid name: 2024 YR4
Probability: 2.21%
Impact date: 2032-12-22.59
Asteroid name: 2017 WT28
Probability: 1.10%
Impact date: 2104-11-24.69
Asteroid name: 2010 RF12
Probability: 10.24%
Impact date: 2095-09-05.99
Source: NASA/JPL Sentry Data API
In the span of just weeks, the US government has experienced what may be the most consequential security breach in its history—not through a sophisticated cyberattack or an act of foreign espionage, but through official orders by a billionaire with a poorly defined government role. And the implications for national security are profound.https://www.schneier.com/blog/archives/2025/02/doge-as-a-national.html
The person who signed me up for all these parent-teacher conferences is not the same person who has to go to them today. PAST ME IS ALWAYS FUCKING UP SHIT FOR FUTURE ME
Asteroid name: 2024 YR4
Probability: 2.21%
Impact date: 2032-12-22.59
Asteroid name: 2017 WT28
Probability: 1.10%
Impact date: 2104-11-24.69
Asteroid name: 2010 RF12
Probability: 10.24%
Impact date: 2095-09-05.99
Source: NASA/JPL Sentry Data API
Codeberg - We stay strong against hate and hatred
https://blog.codeberg.org/we-stay-strong-against-hate-and-hatred.html
Discussions: https://discu.eu/q/https://blog.codeberg.org/we-stay-strong-against-hate-and-hatred.html
Everyone, have a great Friday!
All the bad things have won the war.
difficult questions
Enjoy this Wednesday, Stefano, everyone!
https://it-notes.dragas.net/2025/02/08/caching-snac-proxied-media-with-nginx/
#Data #Fediverse #Hosting #ITNotes #Networking #Nginx #NoteHUB #Ownyourdata #Server #Snac #Snac2 #Social #Tipsandtricks #Tutorial #Web
Thank you very much for sharing.
I have long loathed Oracle, mostly for their draconian licensing practices and litigious proclivities. However, occasionally I get tempted by their "hey, we offer a free tier for VPS instances" and think, maybe just maybe it could be fun.
But then I read a thread like this one¹ from @ErikUden and it's a bucket of ice-water to the face, steeling my resolve. No. Never Oracle. Not ever, no matter how tempting "free" may seem.
A few days ago, a client of mine asked me to install an open-source software (which I won’t name for now). The software has only one official installation method: Docker. This is because, as they themselves admit, it has a huge number of dependencies - some quite outdated - that need to be carefully managed and forced into place; otherwise, nothing works.
I tried replicating the same setup on FreeBSD but didn’t succeed, as some dependencies either aren’t compatible or simply refuse to run. I could try finding workarounds, but I can already picture the chaos every time an update is needed.
So, I decided to build it via Docker to get a better sense of what we’re dealing with. The sheer number of dependencies that Node pulls in is impressive, but even more staggering is the number of warnings and errors it spits out: deprecated and unsupported packages, security vulnerabilities, generic warnings- you name it, and there’s plenty of it.
Since my client needs to launch this service but is subject to audits, they want to be fully compliant and ensure security. Given their substantial budget, they offered financial support to the developers (a company, not just a group of hobbyists) to help improve the project either by making it FreeBSD - compatible or, at the very least, by reducing dependencies with critical vulnerabilities. The client was willing to pay a significant sum, and since the improvements would be open-source, everyone would benefit.
The response from the team? A flat-out refusal. They claimed they couldn’t accept any amount of money because many of these dependencies are "necessary and irreplaceable, as parts of the code relying on them were written by people who no longer work on the project, and we can’t rewrite the core of the software.” Then came the part that really got under my skin: they stated they would rather deal directly “with my client, not with me, because in the end, my concerns are just useless and irrational paranoia.”
Translation? Just pay, and you’ll pass compliance checks - never mind the fact that underneath, it’s a tangled mess of outdated and insecure components. And don’t make a fuss about it.
While I can understand some of the challenges the team faces, I might have accepted this response if it had come from a group of volunteers or hobbyists. But if you’re a company whose sole business revolves around a single software product (with no real competition at the moment), this approach is not just short-sighted - it’s outright dangerous for your users’ security and for your own survival as a business.
The result? They lost a paying client who was ready to invest a significant budget into their software. That budget will now go elsewhere. My client is considering hiring developers to build a similar project with better security (they have both the time and the money for it). I’ll do my best to convince them to release it as open-source - at which point, a new “competitor” will emerge in the market.
The Debian Publicity Team will no longer post on X/Twitter. We took this decision since we feel X doesn't reflect Debian shared values as stated in our social contract, code of conduct and diversity statement. X evolved into a place where people we care about don't feel safe. You are very much invited to follow us on https://bits.debian.org , on https://micronews.debian.org/ , or any media as listed on https://wiki.debian.org/Teams/Publicity/otherSN #debian
"OpenAI shocked that an AI company would train on someone else's data without permission or compensation."😆 😆 😆
https://www.404media.co/openai-furious-deepseek-might-have-stolen-all-the-data-openai-stole-from-us/
Investigating the possibility of adding a brand-new service to BSD Cafe - potentially replacing an outdated one that's just not cutting it anymore.
Stay tuned for updates!
Comunicar el qué, preguntaréis. Pues resulta que éramos los últimos comensales en el local y ella, cuando le pedimos la cuenta, se acercó y nos preguntó -muy seria- si podía preguntarnos algo. Le dijimos que sí, claro, y es cuando nos contó lo que le había pasado a su hijo y qué creíamos que tenía que hacer.
En realidad ella sabía cuáles eran los siguientes pasos, como supimos al final, pero necesitaba contarlo. El por qué nos eligió para eso ya ni me lo pregunto porque con mi aspecto a mí me cuentan su vida y milagros todo quisque. Estoy acostumbrado.
La historia del chaval, aspecto japonés y veinte añitos, es que había ido al supermercado en Majadahonda y al salir se había encontrado el coche con un buen viaje en un lateral. Pero bueno, bueno, de los de taller de chapa y varios repuestos. El chico pregunta primero en el super. No han visto nada y no le pueden decir nada porque no tienen cámaras cubriendo la entrada (los cojones). De ahí se va a la policia local que le dice que ellos no se encargan de esos asuntos y que vaya a la guardia civil. En el cuartel, extrañados, le dicen que para cosas de tráfico es la policia local la que se encarga y el pobre vuelve extrañado a preguntar otra vez a la policia. Y allí, tan panchos, le dicen que no, que eso ha ocurrido en el aparcamiento del supermercado y que no tienen jurisdicción para eso, que pregunte al seguro del super.
La madre nos preguntaba qué podía hacer, que la situación le parecía injusta y que creía que era porque su hijo no es español y no le habían atendido. Mi hija y yo intentamos quitarle hierro al asunto aunque estamos seguros de que si el chaval tampoco se maneja bien en el asunto -tenía aspecto "de chino"- y no sabía cagarse en las muelas de alguien, el racismo que no existe en España había influido en que le toreasen y le mandasen de un sitio a otro. A mí no me lo hacen; a mí hija puede porque es joven pero a mí no. Y a muchos otros que ya ni peinamos canas ni nada -porque no hay qué peinar- tampoco[1].
Le recomendamos que acudiese a su seguro para que si tenía servicio de atención legal le dijesen qué había que hacer en este caso y poco más. Se la notaba muy indignada porque ella pagaba impuestos, tenía derecho a atención policial. Y no salía de ahí la señora. Le dijimos que pagase o no pagase si está aquí tienen que atenderla. Que no se hiciese mala sangre, que le había tocado a su hijo un idiota que no había querido atenderle en ese momento (un idiota racista y vago) y que insistiese porque era su derecho humano.
Nos dio pena; está en un país que no es el suyo, con códigos que no termina de aprehender del todo y no por falta de capacidad -que inteligente es-, y le toca lidiar con alguien así. Nos pidió disculpas por interrumpirnos; necesitaba contarlo decía.
Pues espero que haya conseguido algo y no se le quede la sensación agria de no ser considerada persona.
[1]: Esta es otra de las ocasiones en las que me pregunto para qué cojones queremos policía municipal además de hacer pasarelas de chulería total en las calles y portar material militar y acojonar un poco al débil.
/usr/sbin/sendmail
to a direct connection to an SMTP server, so this issue will eventually fix itself.Added support for subscribing to LitePub (Pleroma-style) Fediverse Relays like e.g. https://fedi-relay.gyptazy.com to improve federation. See snac(8)
(the Administrator Manual) for more information on how to use this feature.
Added support for following hashtags. This is only useful if your instance is subscribed to relays (see above).
Added support for a Mastodon-like /authorize_interaction
webpoint entry, that allows following, liking and boosting from another account's Mastodon public web interface. To be able to use it, you must reconfigure your https proxy to redirect /authorize_interaction
to snac (see snac(8)
).
Some fixes to accept Event
objects properly (like those coming from implementations like https://gancio.org/ or https://mobilizon.fr).
Added some caching for local Actor
objects.
Hashtags that are not explicitly linked in a post's content are shown below it.
Fixed broken NetBSD build (missing dependency in Makefile.NetBSD).
The user profile can now include longitude and latitude data for your current location.
Mastodon API: implemented limit= on notification fetches (contributed by nowster), implemented faster min_id handling (contributed by nowster), obey the quiet public visibility set for posts, other timeline improvements (contributed by nowster).
Reduced RSA key size for new users from 4096 to 2048. This will be friendlier to smaller machines, and everybody else out there is using 2048.
If the SNAC_BASEDIR
environment variable is defined and set to the base directory of your installation, you don't have to include the base directory in the command line.
Fixed a bug in the generation of the top page (contributed by an-im-dugud).
Added support for Markdown headers and underlining (contributed by an-im-dugud).
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song Nine Hundred Miles by #BarbaraDane.
Some technical details for those interested:
The entire FediMeteo setup runs on a FreeBSD VM costing around 4 euros per month. It supports almost all major EU countries (plus the UK), with just a few left to complete. Currently, there are 25 separate jails, each running its own instance of snac, totaling 25 instances. The VM load typically stays around 10%, which increases to 30% when updates are published for countries with larger numbers of cities (currently Germany and Italy). The only time the load spikes is when new countries are announced; during that time, all remote instances connect to all cities to download their details.
As for RAM usage, excluding the ZFS cache, it's currently a total of 213 MB. Yes, MB.
"I prefer to meet people where they are" says reasonable-sounding white dude holding court at a table in the back of a Nazi Bar, redux.
There are people out there apparently seriously proposing to spend over *thirty million dollars* and an uncountable amount of labor, to adversarially interoperate with Blue Sky...
https://jwz.org/b/ykgp
In this release:
New file system gefs(4) now enabled in the installer.
CVE-2024-8158 fixed.
ip/ipconfig now support dhcpv6 dynaic allocations and handles prefix expirations.
honeycomb kernel
git fixes
custom sam b2 menu items
AND MORE
For those who are attending #FOSDEM this year, this link to the lyrics of Bella Ciao might come in handy https://en.wikipedia.org/wiki/Bella_ciao#Partisan_version
@CdnCurmudgeon Are you being silly?
Fascism wasn't a phenomenon tied to the geography of DE
In fact, Hitler openly stated he was modeling the US
Hitler really dug prison slave labor exemption, especially when disproportional amount of ppl in prison being black, who are then forced with violence to work
Also, Churchill was an open fascist, unaware of his work in Palestine? Or anything beyond some radio speeches?
Oh yea, the genocide rn, are we rly to pretend you avoided all news about it?
R.I.P. David Lynch
La compra de Twitter (X) de Elon Musk tuvo sus trampas. Se saltó la ley y ahora la SEC (CNMV) lo quiere sentar en el banquillo antes de que Trump y el propio Musk despidan al presidente de la SEC.
Resumo el caso en El Salto. https://www.elsaltodiario.com/elon-musk/regulador-estadounidense-sec-lleva-tribunales-compra-x-twitter
Client: Help, emergency. I have 24 hours to move my workload to another server. What do we do?
Me, five minutes later: "Done. Your workload is now running on the new server."
Client: "How did you move over 200GB with just a minute of downtime, from one provider to another and in a different country?"
Me: "Thanks to FreeBSD, ZFS, and a little bit of proactive planning."
I have a task that replicates all the VMs from one server to another every 15 minutes using zfs-send/zfs-receive. This VM connects to a VPN with two reverse proxies.
Meaning, when I move this VM, we don’t need to change any IPs since it’s not directly exposed.
I powered it off, cloned the differences in seconds, and restarted it.
Client in disbelief.
Me, relaxed and happy.
Thank you, FreeBSD, thank you, ZFS!
#FreeBSD #ZFS #TechSupport #ServerMigration #OpenZFS #SysAdmin #RunBSD
I think that we the artists and the people should not care about if AI is intelligent or not (it's just a semantic discussion with no interesting conclusions), but who benefits and who is damaged from the current hype.
And this is clear: the bigtech is taking the food from our mouths. Sadly, many artists are hypnotised by the new bling. But it's destroying us and robbing our work. We must take action as soon as possible.
I got asked if I could create a #howto for creating a (public) #NAT64 service - just like I did recently for #BoxyBSD. With #DNS64 and #NAT64 you can also reach resource in the legacy internet (#IPv4) on #IPv6 only systems.
While this is based on #unbound and #tayga, there’s also a solution by using the #OpenBSD's native way which is also running on the other gateway. I’ll share a second how to how to do this in OpenBSD and pf.
https://gyptazy.com/howto-create-a-public-dns64-nat64-gateway/
Unless maintaining it was expensive or a hassle, I would keep it.
No sería lo mismo que con un profesional pero seguiríamos teniendo un perfil bajo de gastos. En el teatro, igual que en el software, siempre me ha parecido más valioso el resultado de partir de poco y usar ingenio y talento para resolver.
No sé cómo terminará la cosa pero veo un cisma. Y si hay que "forzar" a que no se suba la cuota y no se contrate al cantamañanas del profesor seguirá habiendo algunos que tampoco querrán estar.
La asociación está sirviendo (y debería servir en el futuro) para llevar el teatro a sitios como prisiones o residencias de ancianos y tener una finalidad social. Muy pocos recursos pero bastantes ganas. Y entre esos pocos recursos está la falta de una dirección teatral. Claro, cinco eurazos al mes de cuota no dan para casi nada y menos para pagar a un profesional ... Hasta ahora.
Ahora algunos han visto la oportunidad de contratar unas horas al mes a uno de los antiguos profesores de teatro municipal y plantearon primero aprobar que queríamos dirección teatral y luego subir la cuota para poder pagarle. Muy bien todo. ¿O no?
No, porque hay algunos que no queremos pagar esa cuota. Tampoco es que podamos hacerlo pero sobre todo no queremos. ¿Qué ocurre con nosotros? Y ahí estuvimos encallados las últimas dos horas de la junta y el motivo por el que hemos tenido que aplazarlo.
Si se aprobase todo eso, y se va a aprobar, significa que para ser socio de Bóvalo, la asociación, se tendrá que pagar una cuota de cuarenta o cuarenta y cinco eurazos o si no ... No se podrá ser socio, ¿no? Si no pagas no puedes pertenecer. Al menos yo lo veo así. Hacer teatro juntos en ese caso no tiene sentido. Unos podrán estar dirigidos y otros no; será estupendo organizar funciones con esa disposición.
Lo cierto es que hay algunos a los que se les sale la sonda y no saben mear.
La derecha y demás morralla llevan tiempo intentando (y consiguiendo) que cuestionar ese pasado en concreto sea molesto o incluso peligroso en algunos sitios y eso nos va a llevar otra vez a tiempos tenebrosos, ya no creo que haya vuelta atrás por desgracia.
Y mira que en los chavales pobres (la mayoría) puedo entender que anhelen la vuelta de ese pasado "mejor" porque futuro no les hemos dejado mucho; ¿pero los ricos? ¿Los hijos y familiares de familias pudentes -ricas- quieren ese pasado mejor porque éste les parece malo? ¿En qué?
Bueno, quizás sea porque como decía Miles Vorkosigan en Barrayar tenían bonitos uniformes y botas de caballería, y eso siempre tira siempre que no exista riesgo como hemos podido ver hace unos días en Carabanchel o en el Garibaldi.
What is this? I've seen it on Tumblr.
I had not seen anyone make the obvious thing, so I made the obvious thing.
lamp✨
My latest cartoon for @newscientist.bsky.social