Some of the music I listened to this past year, including Charli XCX, Fire-Toolz, @williamfields, Autechre, Kelley Sheehan, and @meljoann!
https://reillyspitzfaden.com/posts/2026/01/music-listened-in-2025/
Some of the music I listened to this past year, including Charli XCX, Fire-Toolz, @williamfields, Autechre, Kelley Sheehan, and @meljoann!
https://reillyspitzfaden.com/posts/2026/01/music-listened-in-2025/
HERE IS YOUR #bash history #recap / #rewind / #year_in_review !!!
grep -v "^[[:space:]]*#" ~/.bash_history |sed -E 's/^ *(sudo|doas) *//g' |awk '{print $1}' |sort |uniq -c |sort -n |tail -n $((LINES-2))
Example from this laptop:
54 updateall
57 nsxiv
58 pipx
63 pkg_info
73 tail
92 git
106 ssh
109 w3m
110 less
127 echo
138 type
194 searchall
214 grep
225 ststatus
275 duck
286 ll
292 vi
341 man
433 cd
453 ls
(Of course, it's not strictly a YEAR in review. Bash can timestamp the history, but most people don't have that turned on by default)
@rl_dane I saw this just before sleep
I tried with #Fish
Fish store history as #YAML
I tweaked the command to make it barely works
Since it's YAML, it's store the timestamps
So, i tried to do an actual #year_in_review
3 hours later, here it is !
https://gitlab.com/pinage404/dotfiles/-/commit/5089def105806afe92684609a004081cf5aa136d
HERE IS YOUR #bash history #recap / #rewind / #year_in_review !!!
grep -v "^[[:space:]]*#" ~/.bash_history |sed -E 's/^ *(sudo|doas) *//g' |awk '{print $1}' |sort |uniq -c |sort -n |tail -n $((LINES-2))
Example from this laptop:
54 updateall
57 nsxiv
58 pipx
63 pkg_info
73 tail
92 git
106 ssh
109 w3m
110 less
127 echo
138 type
194 searchall
214 grep
225 ststatus
275 duck
286 ll
292 vi
341 man
433 cd
453 ls
(Of course, it's not strictly a YEAR in review. Bash can timestamp the history, but most people don't have that turned on by default)
#2025wrapped #Recap #Introduction
A manera de recapitulación y porque hace ya 7 años hice mi #introduccion en esta cuenta de Mastodon va un resumen del año en los multiples proyectos donde colaboro: 👉🏾 cacu, pronombre (el) habito la Ciudad de México - Tecnólogo 👈🏾
As a quick recap—and since I wrote my Mastodon #introduction seven years ago—here’s a summary of the past year across the many projects I’m involved in: 👉🏾 cacu, pronoun (he), living in Mexico City- Technologist 👈🏾
HERE IS YOUR #bash history #recap / #rewind / #year_in_review !!!
grep -v "^[[:space:]]*#" ~/.bash_history |sed -E 's/^ *(sudo|doas) *//g' |awk '{print $1}' |sort |uniq -c |sort -n |tail -n $((LINES-2))
Example from this laptop:
54 updateall
57 nsxiv
58 pipx
63 pkg_info
73 tail
92 git
106 ssh
109 w3m
110 less
127 echo
138 type
194 searchall
214 grep
225 ststatus
275 duck
286 ll
292 vi
341 man
433 cd
453 ls
(Of course, it's not strictly a YEAR in review. Bash can timestamp the history, but most people don't have that turned on by default)
@djangocon I’ve added a list of DjangoCon US 2025 recap articles at the end of my post — but I’m sure I’ve missed some! If you’ve written or seen other recaps, please share the links so I can add them. 🙏
I’d also love your feedback on my article 💚
@djangocon I’ve added a list of DjangoCon US 2025 recap articles at the end of my post — but I’m sure I’ve missed some! If you’ve written or seen other recaps, please share the links so I can add them. 🙏
I’d also love your feedback on my article 💚
I’ve just published a new blog post: *My DjangoCon US 2025* — a collection of my Mastodon posts and photos from the conference in Chicago.
It’s a snapshot of a fantastic week full of talks, friends, and great community vibes.
Read it here 👉 https://www.paulox.net/2025/10/05/my-djangocon-us-2025/
CC @djangocon
Hey Fediverse! 👋
We just wrapped up an amazing FediForum June 2025 a week ago, and BadgeFed was right in the thick of it! Here’s a recap of what we did, what we learned, and what’s next for decentralized badges.
BadgeFed had the honor of presenting and hosting two unconference sessions and showing off our work in one speed demo slots (watch the demo). The energy was fantastic; lots of curiosity, sharp questions, and a real hunger for open standards in the credentialing space.
A big theme at FediForum was specs and open standards. We’re right there with you! That’s why we’ve enhanced our technical documentation to explain exactly how BadgeFed uses ActivityPub and OpenBadges together:
Read more in our DETAILS.md.
We heard you: people want to try BadgeFed! Right now, it’s a solo setup (one admin, one Docker container), but we’re working hard to make it easier for others to deploy, configure, and even federate their own instances. Stay tuned for updates on multi-admin support and streamlined onboarding.
One of the most important pieces of feedback we received was about badge discoverability vs. timeline spam (see the issue). We want badges to be easy to find and share, but we also don’t want to flood the Fediverse with unwanted posts. This is now our top priority, we’re rethinking how verbose BadgeFed should be, and exploring opt-in/opt-out models for badge visibility and hashtag use.
We’re also working on ways to let you embed badges in your blog or add them to your Mastodon profile. More news on that soon!
FediForum was a fantastic experience, huge thanks to everyone who attended, gave feedback, and showed interest in decentralized credentials. Let’s keep building a more open, verifiable, and user-empowered Fediverse!
Badge up, and see you in the timeline! 🏅
You can read the article "BadgeFed @ FediForum June 2025: Unconferences, Demos, and Community Feedback" by @mapachehere as well.
#activitypub #badgefed #fediverse #dotnet #decentralization #open-source #openbadges #identity #fediforum #recapHey Fediverse! 👋
We just wrapped up an amazing FediForum June 2025 a week ago, and BadgeFed was right in the thick of it! Here’s a recap of what we did, what we learned, and what’s next for decentralized badges.
BadgeFed had the honor of presenting and hosting two unconference sessions and showing off our work in one speed demo slots (watch the demo). The energy was fantastic; lots of curiosity, sharp questions, and a real hunger for open standards in the credentialing space.
A big theme at FediForum was specs and open standards. We’re right there with you! That’s why we’ve enhanced our technical documentation to explain exactly how BadgeFed uses ActivityPub and OpenBadges together:
Read more in our DETAILS.md.
We heard you: people want to try BadgeFed! Right now, it’s a solo setup (one admin, one Docker container), but we’re working hard to make it easier for others to deploy, configure, and even federate their own instances. Stay tuned for updates on multi-admin support and streamlined onboarding.
One of the most important pieces of feedback we received was about badge discoverability vs. timeline spam (see the issue). We want badges to be easy to find and share, but we also don’t want to flood the Fediverse with unwanted posts. This is now our top priority, we’re rethinking how verbose BadgeFed should be, and exploring opt-in/opt-out models for badge visibility and hashtag use.
We’re also working on ways to let you embed badges in your blog or add them to your Mastodon profile. More news on that soon!
FediForum was a fantastic experience, huge thanks to everyone who attended, gave feedback, and showed interest in decentralized credentials. Let’s keep building a more open, verifiable, and user-empowered Fediverse!
Badge up, and see you in the timeline! 🏅
You can read the article "BadgeFed @ FediForum June 2025: Unconferences, Demos, and Community Feedback" by @mapachehere as well.
#activitypub #badgefed #fediverse #dotnet #decentralization #open-source #openbadges #identity #fediforum #recap
