~dan's feels

Short notes about my current condition

This page contains short feels which serve as a timeline. I'll post about my progress on different projects, my personal condition and sometimes other off-topic stuff.



13 may 2026

More test units for EnvsBot

  • Added tests for plugins "_admin", "_reg_profile", "birthday_notify" and "dice"
  • Updated minimum version of python to >=3.12

permalink



12 may 2026

Finally moved from ISC DHCP to dnsmasq

I finally managed to move my OpnSense router from the deprecated ISC DHCP to the now recent dnsmasq DNS/DHCP server. dnsmasq now can resolve dynamic IPv6 addresses and has a lot of small other benefits for small home networks.

Merged a few PRs from ~creme 👍:

  • EnvsBot: Persist duck spawn counters across restarts
  • EnvsBot: Refactor poll plugin to use core helpers

I also began to develop a test suite for the EnvsBot. At the moment we have a coverage of 13%. If we reach 70-80% I think we can release the first major version.

permalink



11 may 2026

Monday's progress

Not doing much over the day, just relaxing on the couch. Continuing development when it get's dark.

  • EnvsBot "rooms" plugin: Made eventhandler more robust and JOINED_ROOMS variable more accurate.
  • EnvsBot "tools" plugin: Added "joined rooms" to the ",seen" plugin. Will output an error if user is offline.
  • Updates: Updated my homelab (one day overdue)

permalink



10 may 2026

Second EnvsBot BETA

  • EnvsBot (ducks): FIXED plugin not to ping all users in the ",duck top|friends|enemies|stats" list
  • EnvsBot (karma): FIXED plugin not to ping all users in the ",karma top|bottom|[nick]" list
  • EnvsBot (refactor): Did a little code deduplication
  • EnvsBot v0.4.0-BETA: Second BETA version released
  • EnvsBot "tools" plugin: added ",seen <nick>" command

permalink



09 may 2026

What I've done today

  • EnvsBot: refactored the "_reg_profile" plugin, so now you can add all fields to the bots vCard that XEP-0054 allows by editing the vCards XML directly in the vcard.py file (vcard_sample.py provided).
  • Finally slept from around 04:00 to 15:30.So after my usual starting problems and after a cup of coffee, I now feel rested!

permalink



08 may 2026

Work on EnvsBot continues

  • EnvsBot: Refactor - deleted some duplicate code
  • EnvsBot: Added "acronyms" command (alias "acro") - Example: ',acro lgtm'
  • EnvsBot: extended "acronyms" command with a "acronyms remove <acronym> <description>" to suggest a removal of a wrong acronym.
  • EnvsBot: Did a little bit of code cleaning

permalink



07 may 2026

Development of EnvsBot unpaused

We started the development of the EnvsBot again, after a very brief pause.

I already added the "on|off|status" function to enable/disable plugins to the remaining plugins, so now all plugins can be toggled on/off where applicable for each room.

The "_core" helper plugin was also extended to contain duplicate code which partly still needs to be implemented in some plugins.

TODO:

  • [X] deploy changes to EnvsBot

permalink



06 may 2026

What am I doing today?

  • [X] revise website more ("feels" integration)
  • [X] setup urlscan to reliably get URLs from emails in NeoMutt
  • [X] Fix /copyurl plugin in profanity to use OSC 52 with primary paste buffer
  • [X] Added CoC to NeoVim to check Syntax

permalink



05 may 2026

Webmention support in ttbp progresses

I managed to change the ttbp "feels" blog script to show webmentions! But no need to change anything. You can leave the divfooter.txt empty or nonexistent and it has the same behavior as before. If you add for example

<div class="notementions" href="{permalink}"></div>

it will add that empty <div> tag with the permalink at the bottom of the feels entry's <div>, so now my "feels" should support webmentions.

Update: It seems bridgy doesn't find my public message with the permalink, but it does find my reply to it, including the link. Strange...

permalink



04 may 2026

EnvsBot Development Slowdown

I'm a little exausted although it's the beginning of the week and I haven't done much over the weekend. Maybe because the intense work on the EnvsBot for the last weeks.

We decided to leave the bot running and stop active development for some time, except bug fixes of course. We've really done a lot during the last 2 month and decided to take a break.

But don't panic: Development will continue after we had the time to take some breath.

permalink

[To The Top]