I might have fixed #daylightbot 's GMT/BST "posting-at-a-certain-time" problem. I definitely have not fixed the "all times in text are in UTC" problem because that isn't a bug, it's a feature.
As pointed out by @pete23.com tomorrow is John Cage day in the Central Belt. #daylightbot
so a thing with #daylightbot is that these statements are constructed at random from two relatively short lists and this one in particular has always got more engagement and I love that it does.
folks, I think #daylightbot has an off-by-one error that only kicks in on jan 1st, but by the time I get to fix it I've forgotten what it is. Date/time stuff is hard. We actually get about 22s more than yesterday.
soooo... I am not 100% sure why #daylightbot kicked in today. It isn't supposed to run until the solstice (apart from Sunday) because honestly I need to know days are getting longer, not shorter. Anyway, hello, old friend.
Hello old friend. #daylightbot is such a beacon this time of the year.
quick reminder that (i) #daylightbot only works in UTC, not BST, and (ii) if you're in the UK the clocks go forward an hour overnight tonight.
I should point out that I an struggling to get facets - the thing in the atproto python library that inteprets hashtags as rich text clickable metadata - to work with #daylightbot, but will get there eventually.
You’ve made my day Mike, cheers to the #daylightbot
hm, #daylightbot has kicked off early. it is quite likely it'll say merry xmas on the wrong day, too.
for more info about #daylightbot please read github.com/mikewallis/d...
Now singing #DaylightBot do do dedodo ala #TedLasso