Log
Found myself writing a bunch of #Go code to track every time I switch my heating system ON and OFF, just to log hours and consumption. Is this a symptom of some kind of weird illness?
Today, I said NO to a customer. I think it’s the first time I’ve done it so explicitly. They’ve been trying for months to push me into a space where I feel anything but comfortable, and I realized it wouldn’t be good for either of us. I still feel a bit weird about it… guess it’s just lack of practice.
Porque los raritos que vivimos en un terminal también disfrutamos de nuestro #ViernesDeEscritorio. Sí, es #macos con #kitty y #tmux con varios panes (#nvim #mutt #htop).
I’ve set up #Matrix again with all kinds of bridges, just because I couldn’t be bothered to switch apps. Now I have everything at my fingertips in the console.
I feel like we closed a door yesterday that had been open for six years. Grateful for everything I’ve learned and sad because I fear it will be a while before we can actively work together again.
Yesterday, my eyes sparkled once more, even if just for a little while. They already know who they are—no need to say much more.
#Kindle Book, tap near the top of the page to open up the Menu. Then, tap on the “Aa” symbol.
Then, tap on where you see “More”.
From there, you will see an option for “Reading Progress”. Tap on that. You’re welcome.
I always forget where it is!
“Nothing changed my career for the better more than letting go of the fear of never being good enough and instead embracing the joy of knowing I can always find something to get better at”
—
Jason Lengstorf
Have I taken on too much by building a timeline reader directly from my #PDS? Not sure if it’s too much, but I wanted to refresh my #Django skills, and one thing led to another. Images aren’t showing yet, and I can’t interact with the timeline, but you have to start somewhere… I guess.
Today, I’ve been hit with imposter syndrome in a pretty strong way. Suddenly, I felt like a tiny, insignificant ant in a world full of people much better than me. It has passed a little now, just a little.
En nuestra instancia #BOFHers de #Mastodon (https://mastodon.bofhers.es) buscamos soluciones para mantener la actividad. Con 80 usuarios y 300+ GB de disco, en una VM de 8 GB RAM y 8 vCPUs, las actualizaciones son cada vez más complicadas, requiriendo casi el doble de espacio en disco, a pesar de nuestras tareas programadas para reducir cachés, assets y previews.
Agradecemos boost y/o cualquier consejo, sugerencia o aportación para que #BOFHers siga siendo un espacio activo para todos.
Desde que agregamos el clean diario va algo mejor:
Filesystem Size Used Avail Use% Mounted on
/dev/xxx 492G 146G 323G 32% /xxx/mastodon
Habría que quitarle 30Gb de los dumps diarios, que también están ahí
load average: 2.61, 2.07, 2.32
El cleanmedia diario:
# tail -n 100 cleanmedia.log
3155/3155 |=========| Time: 00:02:08
Removed 3155 media attachments (approx. 3.71 GB)
1807/1807 |=========| Time: 00:01:09
Removed 1807 preview cards (approx. 343 MB)
No quiero entrar en comparaciones ni tampoco digo que no sea necesario todo esto, pero me parecen unos requisitos - de entrada - demasiado exagerados para interactuar con #activitypub .