MikeTrendsTrends right now

search

timezones

Trends

  1. 1
    Radio Regentrude Airs Its Daily Scheduleโ—# OnAir 5.10. # NowPlaying *=mod /w pres 09:00 # Rock # Metal 11:00 # Folk 13:00 Timezone 16:00 Folk 18:00 * Platt 19:00MmastodonCultureMusic21 d ago

    German internet radio station Radio Regentrude is running its regular broadcast day, posting its on-air lineup for listeners. The schedule includes rock and metal in the morning, folk sets around midday and evening, a Low German (Platt) programme, a timezone show, and closing rock programmes late at night. The station shares this format daily so followers can tune in for their favourite genres.

  2. 2
    New open source GTK4 tool helps users manage timezonesโ—Awesome little # helper to survive # timezone (s). ๐Ÿ˜…๐Ÿ˜œ https:// github.com/hernantz/timezones/ # gtk4 # libadwaita # openMmastodonTechnologySoftware12 d ago

    Developer hernantz has released a small open source timezones helper built with GTK4 and libadwaita, aimed at Linux users who need to keep track of multiple time zones. The tool is shared on GitHub as free software. Early reactions are lighthearted, with users calling it a fun and handy little utility for surviving time zones.

  3. 3
    Players seek groups for co-op island exploration game Big Walkโ—Daily ๐Ÿ‘ฃ Big Walk ๐Ÿ‘ฃ LFG Thread - October 4, 2026 Looking for a partner or group to explore the island, solve puzzles, orMmastodonCultureGaming12 d ago

    Players of Big Walk, a cooperative exploration game set on an island, are organizing daily matchmaking threads to find partners or groups for October 4, 2026. Participants share how many players they need, their timezones to avoid connection issues, and whether they plan to use voice chat, as they team up to explore the island, solve puzzles, and get lost together.

  4. 4
    Hardcoded timezone bug broke bank reconciliation twice a yearโ–ผReconciliation broke twice a year for months before we found the pattern. Our settlement cutoff was defined as 23:00 locMmastodonBusinessBanking26 d ago

    An engineer describes how a banking settlement cutoff set to 23:00 local time was converted to UTC once at deploy time and hardcoded, so reconciliation silently failed for months after each daylight saving change. The cutoff shifted by an hour when clocks changed, and the pattern was only spotted after repeated twice-yearly breaks.