mastodon 4.8.0-nightly.2026-10-06Pidgin Lead Developer/Maintainer, Democratic Socialist, Premature Internet Activist, Twitch Affiliate. My opinions are my own. 🐥🐦🐧
I'm not burnt out, I went supernova, but quantum entanglement has kept me functioning.
Greetings Programs!! We're back tonight working on @pidgin@fosstodon.org 3.0 Alpha 3!! Come on by!!
Just a heads up, no stream tonight as i'm going to fulu's "own your sh*t" meetup tonight in Fond Du Lac Wisconsin. If you're in the area and care about #righttorepair and other stuff you should check it out. (Note registration is required).
Greetings Programs!! We're back tonight working on @pidgin@fosstodon.org !! We've got some 3.0 Alpha 3 and some 2.15.0 work I want to get done tonight, so come on by!!
I don't usually post memes here.. but this one needs to be shared far and wide...
Today is just going to be one of those days like yesterday I guess...
I shared the recent @pidgin@fosstodon.org XMPP poll in a number of places and someone responded with this
> (Poll didn’t let me vote w/o an account; posting here instead in case it’s helpful)
I'm never going to be able to appease you people, please just ignore this stuff.
Asking me to do additional work to correlate your data because you can't be bothered to create an account is just fucked.
Greetings Programs!! We're back at it tonight working on @pidgin@fosstodon.org 3.0 Alpha 3!! Come on by!!
I'm so over this #diabetes crap. I was diagnosed back in early June and the more we treat it the more symptoms I seem to be experiencing... For example, last week I started getting constant foot neuropathy which is still on going. And apparently last night I had my first documented nocturnal hypoglycemic event where I slept through my phone going nuts for over an hour until my glucose made it back over 70mg/dl on it's own. According to my fitbit I was in a light sleep at the time.
Greetings Programs!
We back at it again, for the second time today, working on @pidgin@fosstodon.org 3.0 Alpha 2. Earlier today we got DMs working in #Zulip but we found a few things to fix in libpurple which we're going to work on tonight! Come on by!!
It's so weird seeing a @gaim@fosstodon.org in @pidgin@fosstodon.org again...
I will never understand why people decide "help" with something they they refuse to read the back story, try to over simplify the problem, assume the person asking question is an idiot, and so on.
I asked a straight forward question in a development room and I've since explained the problem at least 3 times and written orders of magnitude more about it than anyone that was trying to "help".
The most recent "helper" just completely disappeared after I wrote an additional 350 words 😩
Greetings Programs!! We're back with our last day stream in awhile. That's sad news, but the good news is that's because I've got a new contract starting tomorrow!
Anyways, come on by as we work on @pidgin@fosstodon.org 3.0 Alpha 2! Specifically we're trying to get DMs working with #Zulip today. We're close and hoping to get it done for the April State of the Bird!
This is real pie in the sky stuff, but I hope #milwaukee makes it happen.
https://www.fox6now.com/news/milwaukee-30th-street-bike-pedestrian-trails-proposed-feedback-sought
Great write up on the state of #GitHub and the history of #OpenSource hosting in general. It's also making me consider giving HGKeeper some much needed TLC...
Greetings Programs! We're back tonight working on @pidgin@fosstodon.org 3.0 Alpha 2 and maybe some ops stuff!! Come on by!!
One of these days I'll get a win with a single knock out ... Actually this makes me wonder if it's possible to win with 0 knockouts...
Hey Programs! When watching a streamer, please don't do this... Everyone makes typos. Trying to call a stream on a typo, especially one their compiler will catch, it's a silly thing to do as it's just distracting and not helpful at all.
The best part of all of this too, is that most of them time this is the only thing they'll ever say.
Greetings Programs!! We're back at it tonight working on @pidgin@fosstodon.org 3.0 Alpha 2!! Come on by!!
@jwz@mastodon.social so an autoreconf -i --force is telling me configure.ac:1145: warning: macro 'AM_GNU_GETTEXT' not found in library. But that is defined in /usr/share/gettext/m4/gettext.m4 so it looks like an include issue or something. Still digging.
patch -p1 -i foo.patch from the source root. You still FTBFS on Debian without telling autoconf about the include path, but since that wasn't the "assignment"
--- a/debian/rules 2025-12-04 14:41:56.676490182 -0600 +++ b/debian/rules 2026-09-05 14:16:59.639975007 -0500 @@ -4,7 +4,10 @@ DH_VERBOSE = 1 export DH_OPTIONS=-v
%:
+override_dh_autoreconf:
override_dh_auto_configure: ./configure --prefix=/usr
State of capitalism in the USA.. "best customers get a dollar if you find the coupon, click on the clip button, and then give us your phone number at check out.."
@jwz@mastodon.social regenerating configure with aclocal && autoconf && autoheader gets me a clean configure on deb 13.
Did the OS you created the release tarball on have a gettext version greater than 23 or so?
The "proper" fix for this with newer gettext is to run autopoint before aclocal. Problem is that wants to blow away your po/Makefile.in.in. I don't know if you have anything special in there.
This would copy the gettext macros into aclocal.m4 in the tarballs fixing the problem.
@jwz@mastodon.social autopoint is a new thing from gettext, They install their m4 scripts outside of $prefix/share/aclocal now which is causing the issue and autopoint fixes it.
If you don't have any customization to po/Makefile* id' just blow it away and let gettext to it. dshea has a comment about it https://www.jwz.org/blog/2026/09/xscreensaver-6-16/#comment-272004
This would mean that you also need to autopoint; aclocal; autoconf; autoheader to generate your configure script before releases. That'll make sure all the macros end up in aclocal.m4.
@jwz@mastodon.social this is getting close to not lazy web 😂
I do not publish a public source code repository. I publish releases as tar files (above) and welcome submissions and change requests via email. It's fine. You'll get over it.
@jwz@mastodon.social yeah it's weird, i see them in po/Makefile under potfiles, but then don't end up in the pot file even after make -C po xscreensaver.pot. Using the command from pidgin 2 doesn't seem to make a difference either.
@jwz@mastodon.social I haven't figured out why yet.. But autoreconf -I /usr/share/gettext/m4 --force will work, you'll get a warning that is fixed by adding a AM_GNU_GETTEXT_REQUIRE_VERSION. I tested before and after AM_GNU_GETTEXT and it seemed to work anywhere.
I didn't see anything in the docs about how you're regenerating configure, so this might not actually help?
