K‮ly‬e @khird@qoto.org

… and it’s in the books! The season is now archived but I can make corrections if necessary; just let me know if you see any errors. #CFL #CFLoM

The #CFL season is updated at Sports Club Stats. There’s still a week to go, but the remaining games can’t affect the teams’ finishing order at this point. As always, please let me know if I entered anything wrong.

The streak continues into year 18! #TogetherWeRide #YeMenOfCalgary #CFL #CFLoM #CalgaryStampeders

Today Firefox has started having a weird cursor-displacement issue, wondering if anyone can shed some light on it.

Whenever I open a popup menu, the arrow stays where I left it, but the cursor coordinates (i.e. what option gets highlighted and what registers a click) reset to the top left corner. So if I right-click and slide the arrow onto the menu, I'm actually clicking on things like my back and refresh buttons (the same distance down and to the right of the top left corner as the arrow is from the point where I right-clicked to open the menu). For nested submenus (e.g. folders in the Bookmarks menu) the process repeats for every level of popup. However, this only applies to the browser chrome; links on the webpage highlight according to the actual position of the arrow.

The problem doesn't occur until some time (maybe ten minutes to half an hour, I haven't really measured) after browser startup, and resets when I open a new window - temporarily fixing the problem in the original window, too.

I'm flummoxed; search turned up a lot of stuff about people who accidentally turn on caret browsing, but that doesn't really seem to explain these symptoms. Browser version is 64-bit 117.0.1 on Arch. Any suggestions appreciated!

#firefox #error #techsupport

Not sure whether my audio is desynced or if the referee is blowing the whistle way too early in this game.

#cflom

For anyone using the DHCPv6 client app (be.mygod.dhcpv6client) on a recent version of Android, here's something that might save you some frustration - I learned it the hard way.

In theory, you'd only need the app to run occasionally if your leasetimes are reasonably long, so it's tempting to try and save battery by not exempting it from background restrictions. I figured I'd be clever and rig up a trigger to fire it every day plus whenever I reconnected to the network, which is probably cheaper than running a separate app constantly. And lo and behold, my wifi just couldn't hold a connection anymore.

After a lot of troubleshooting, it turns out that, when the app is killed off by the system, the underlying library removes any addresses it's acquired. On its face, this doesn't seem so bad, as the network should revert to IPv4-only after those addresses are removed. But it gets worse: because you stop receiving IPv6 traffic immediately, but the connectivity check takes a while to invalidate the cached IPv6 address it's monitoring, Android will interpret the fact that it's no longer receiving responses as evidence that the network failed. So your phone disconnects from the wifi - and if the whole cycle triggers on every connection, you'll never get more than about a minute of connectivity before it all comes crashing down.

So as far as I can tell, there's no alternative but to exempt it from background restrictions, and leave it running constantly even though you only need it to exchange a couple packets with the router every 24 hours. If anyone figures out a way to overcome this, I'd love to hear about it. Otherwise, I hope this helps someone else facing similar frustrations.

#android
#ipv6
#dhcp
#dhcpv6

I've got the current #CFL season up at http://www.sportsclubstats.com/football/Canada/CFL.html . Please review it and let me know if I entered anything wrong!

Also some of the historical seasons aren't displaying properly - can anyone figure out why? #CFLoM

I really wish TSN would use some other method to indicate the team in possession of the ball. Simply colouring the down and distance isn't helpful when the teams are represented by such similar shades of red. #CFLoM