fidzu : Fedora

10 Nov 2025 12:00pm GMT

10 Nov 2025 12:00am GMT

Hello travelers!

Loadouts for Genshin Impact v0.1.12 is OUT NOW with the addition of support for recently released characters like Nefer and for recently released weapons like Dawning Frost, Reliquary of Truth and Sacrificer's Staff from Genshin Impact Luna II or v6.1 Phase 1. Take this FREE and OPEN SOURCE application for a spin using the links below to manage the custom equipment of artifacts and weapons for the playable characters.

Resources

• Loadouts for Genshin Impact - GitHub
• Loadouts for Genshin Impact - PyPI
• Loadouts for Genshin Impact v0.1.12
  • Executable for GNU/Linux distributions
  • Executable for Microsoft Windows

Installation

Besides its availability as a repository package on PyPI and as an archived binary on PyInstaller, Loadouts for Genshin Impact is now available as an installable package on Fedora Linux. Travelers using Fedora Linux 42 and above can install the package on their operating system by executing the following command.

$ sudo dnf install gi-loadouts --assumeyes --setopt=install_weak_deps=False

Changelog

• Automated dependency updates for GI Loadouts by @renovate[bot] in #449
• Fallback to default Tesseract path on Windows by @sdglitched in #450
• Format codebase using ruff and add check in CI by @sdglitched in #451
• Add support for character levels 95 and 100 by @sdglitched in #454
• Automated dependency updates for GI Loadouts by @renovate[bot] in #456
• Change the Tool-Tip labels of Info and Help to match the content by @sdglitched in #457
• Update dependency pillow to v12 by @renovate[bot] in #455
• Introduce the recently added character Nefer to the roster by @gridhead in #459
• Introduce the recently added weapon Dawning Frost by @gridhead in #458
• Introduce the recently added weapon Sacrificer's Staff by @gridhead in #453
• Introduce the recently added weapon Reliquary of Truth by @gridhead in #452
• Automated dependency updates for GI Loadouts by @renovate[bot] in #463
• Update actions/upload-artifact action to v5 by @renovate[bot] in #464
• Automated dependency updates for GI Loadouts by @renovate[bot] in #466
• Stage the release v0.1.12 for Genshin Impact Luna I (v6.1 Phase 1) by @sdglitched in #467

Characters

One character has debuted in this version release.

Nefer

Nefer is a catalyst-wielding Dendro character of five-star quality.

Weapons

Three weapons have debuted in this version release.

Dawning Frost

Nocturnal Dreams - Scales on Crit DMG.

Reliquary of Truth

Essence of Falsity - Scales on Crit DMG.

Sacrificer's Staff

Untainted Desire - Scales on Crit Rate.

Appeal

While allowing you to experiment with various builds and share them for later, Loadouts for Genshin Impact lets you take calculated risks by showing you the potential of your characters with certain artifacts and weapons equipped that you might not even own. Loadouts for Genshin Impact has been and always will be a free and open source software project, and we are committed to delivering a quality experience with every release we make.

Disclaimer

With an extensive suite of over 1518 diverse functionality tests and impeccable 100% source code coverage, we proudly invite auditors and analysts from MiHoYo and other organizations to review our free and open source codebase. This thorough transparency underscores our unwavering commitment to maintaining the fairness and integrity of the game.

The users of this ecosystem application can have complete confidence that their accounts are safe from warnings, suspensions or terminations when using this project. The ecosystem application ensures complete compliance with the terms of services and the regulations regarding third-party software established by MiHoYo for Genshin Impact.

All rights to Genshin Impact assets used in this project are reserved by miHoYo Ltd. and Cognosphere Pte., Ltd. Other properties belong to their respective owners.

09 Nov 2025 6:30pm GMT

07 Nov 2025 5:00pm GMT

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you with both an infographic and a text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in-depth details, look below the infographic.

Week: 03rd - 07th November 2025

Infrastructure & Release Engineering

The purpose of this team is to take care of day-to-day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It's responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces, etc.).
List of planned/in-progress issues

Fedora Infra

• Package unretirement
• Account Deletion Request
• koji or src.fedoraproject.org down?
• Fedora 43 System colapse when drag file from file explorer into VSCode
• fedora 43 installation bug
• mirrorlist link for Fedora 43 still points to development directory
• kernel package forks cannot be viewed due to 403 error
• flatpak-indexer is ENOSPC, not running
• Log In Bug
• Adding jpodivin as sponsor to communishift-log-detective
• [CommOps] Open Data Hub on Communishift
• Update distrobuildsync-eln notifications

CentOS Infra including CentOS CI

• migrate MQTT tracker to different host
• Migrate main CentOS Stream/SIGs origin node for mirror CDN to RDU3
• Design and implement new hardware oob alerting for RDU3
• Redirect connect.centos.org

Release Engineering

• Package unretirement
• Broken Qt/gstreamer update because of two updates pushed simultaneously
• Some packages retired in dist-git not getting blocked in koji (again)
• Untag shim-16.1-4 , shim-unsigned-aarch64-16.1-1 and shim-unsigned-x64-16.1-1 from f44
• Unretirement of the dlib package in Fedora 43
• Bodhi updates stalled
• COSMIC Atomic 43 ostree ref not updated
• f43 Fedora-Silverblue-ostree-x86_64-42.torrent has SoaS Live iso file
• Down EPEL mirror fedora.ipacct.com
• Unretire python-duecredit
• Create ELN kiwi target
• 2 bodhi updates with push issues
• f43 kde desktop live torrent has mobile iso also
• python-jupyter-cache build stuck in f44-updates-candidate
• Unretire python-dnslib
• Unretire python-ana
• Retag ejected Bodhi pushes from failed compose (builders fix impact)
• Remove accidential yt-dlp 2025.10.22 branch
• Unretire libQGLViewer
• F43 Final Release Work
• Some updates with unsigned builds stuck in bodhi
• Disable HTTP caches for repomd.xml files for Koji buildroots
• Missing/messed-up logs for FESCo meting 2024-01-29
• Extend duration that ELN buildroot repos are kept to 17 days

If you have any questions or feedback, please respond to this report or contact us on #admin:fedoraproject.org channel on matrix.

The post Infra and RelEng Update - Week 45, 2025 appeared first on Fedora Community Blog.

07 Nov 2025 10:00am GMT

The Fedora community is coming together once again to celebrate the release of Fedora Linux 43, and you're invited! Join us on Friday, November 21, 2025, from 13:00 to 16:00 UTC on Matrix for our virtual Fedora 43 Release Party.

This is our chance to celebrate the latest release, hear from contributors across the project, and see what's new in Fedora Workstation, KDE, Atomic Desktops, and more. Whether you're a long-time Fedora user or new to the community, it's the perfect way to connect with the broader community, learn more about Fedora, and hang out in Matrix chat with your Fedora friends.

We have a lineup of talks and updates from across the Fedora ecosystem, including updates directly from teams who have been working on changes in this release. We'll kick things off with Fedora Project Leader Jef Spaleta and Fedora Community Architect Justin Wheeler, followed by sessions with community members like Timothée Ravier on Atomic Desktops, Peter Boy and Petr Bokoč on the new Fedora Docs initiative, and Neal Gompa and Michel Lind discussing the Wayland-only GNOME experience. You'll also hear from teams across Fedora sharing insights, demos, and what's next for the project.

Registration is free but required to join the Matrix event room. Once registered, you'll receive an invitation in your Matrix account before the event begins.

Sign up on the Fedora Linux 43 Release Party event page. We can't wait to see you there to come celebrate Fedora 43 with us!

07 Nov 2025 8:00am GMT

Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for parallel installation, the perfect solution for such tests, and as base packages.

RPMs of PHP version 8.4.15RC1 are available

• as base packages in the remi-modular-test for Fedora 41-43 and Enterprise Linux ≥ 8
• as SCL in remi-test repository

RPMs of PHP version 8.3.28RC1 are available

• as base packages in the remi-modular-test for Fedora 41-43 and Enterprise Linux ≥ 8
• as SCL in remi-test repository

ℹ️ The packages are available for x86_64 and aarch64.

ℹ️ PHP version 8.2 is now in security mode only, so no more RC will be released.

ℹ️ Installation: follow the wizard instructions.

ℹ️ Announcements:

• PHP 8.4.15RC1 available for testing
• PHP 8.3.28RC1 available for testing

Parallel installation of version 8.4 as Software Collection:

yum --enablerepo=remi-test install php84

Parallel installation of version 8.3 as Software Collection:

yum --enablerepo=remi-test install php83

Update of system version 8.4:

dnf module switch-to php:remi-8.4
dnf --enablerepo=remi-modular-test update php\*

Update of system version 8.3:

dnf module switch-to php:remi-8.3
dnf --enablerepo=remi-modular-test update php\*

ℹ️ Notice:

• version 8.5.0RC4 is in Fedora rawhide for QA
• version 8.5.0RC4 is also available in the repository
• EL-10 packages are built using RHEL-10.0 and EPEL-10.0
• EL-9 packages are built using RHEL-9.6
• EL-8 packages are built using RHEL-8.10
• oci8 extension uses the RPM of the Oracle Instant Client version 23.9 on x86_64 and aarch64
• intl extension uses libicu 74.2
• RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
• versions 8.3.28 and 8.4.15 are planed for November 20th, in 2 weeks.

Software Collections (php83, php84)

Base packages (php)

07 Nov 2025 6:27am GMT

A while back, Emily Omier posted on LinkedIn about what she called "transactional" open source, that is to say, giving contribution gifts. Emily was against it. "The magic of open source," she wrote, "is that it's not purely transactional." Turning contributions to transactional relationships changes the nature of the community. I understand her argument, but I think the answer is more nuanced.

The rewards of gifts

There's nothing inherently wrong with transactional open source. Not every project or contributor wants to work that way, but when they both do, go for it! Everyone has different motivations, so it's important to recognize and reward contributors in a way that is meaningful to them.

Some people may participate solely to earn a t-shirt. That's okay. They still made a contribution they wouldn't have otherwise. Your project benefits from that.

Plus, getting people in the door is the first step in converting them into long-term contributors. A lot of people who come just for a gift won't stick around, but some will. And gifts can lead to more contributions from the existing contributor base, too.

The risks of gifts

Gifts are often (relatively) expensive and logistically-challenging. The money you spend acquiring and shipping gifts is money that your project can't spend on things with a better return, like test hardware. Plus, it can take a long time to get the gift into the hands of the recipient. I've had packages to India take close to a year to reach their destination. With tariff changes, if you're shipping into the US from the rest of the world, your contributor may be on the hook for import fees.

If you order ahead to get volume discounts, you have to store the stuff somewhere. And, of course, you have to know how you're going to decide who gets the gifts. As I wrote in chapter 4 of Program Management for Open Source Projects: "figuring out an equitable way to distribute [1,000 t-shirts] is hard, but it's a good problem to have. It's still a problem to solve, though."

For company-backed projects, there's a risk of using transaction-avoidance as an excuse to be extractive. The argument could go something like this: "we want to be good open source participants, so we won't tarnish the purity of these volunteer contributions by spending our money to give people gifts." The real motivation is to keep the money.

Planning to give contribution gifts

If you've decided that you want to give gifts for contributions, you have to start with a plan. The first thing to understand is "why?" Everything else flows from the answer to that question. What behavior are you trying to encourage? Will the gift you offer induce that behavior? Who will handle the gifts?

You have to know what action or actions will trigger a gift. Is it the first contribution? Every contribution? Contributions to specific under-developed areas (like documentation or tests)? Personal or project milestones?

Next, what gifts will you give? It's important to recognize and reward contributors in a way that is meaningful to them and encourages a sense of belonging. For some people, simple recognition in release notes or a blog post is enough. Some might love a great pair of socks, while others have no more room in their drawer. The environmental impact of cheap thumb drives, USB cables, and t-shirts will harm your reputation with some people. There's no universal answer.

Then there's the question of who will take the time to collect information, distribute gifts, and handle follow-up questions. If a gift doesn't ship for months (or does ship, but takes a long time to be delivered), you'll undoubtedly have people asking about it. Time spent handling this work is time not spent elsewhere.

If you choose to give contribution gifts, it needs to be part of a broader recognition and incentive program. In general, I suggest saving physical gifts for established contributors, but be very liberal with shout outs and digital badges.

This post's featured photo by Jess Bailey on Unsplash.

The post Giving contribution gifts: the risks and rewards appeared first on Duck Alignment Academy.

05 Nov 2025 12:00pm GMT

A few minutes ago I was answering an email in Thunderbird, and I realized one thing that might have been there for years. The date was in the wrong format! (Wrong as in for me, of course).

I use English (US) for my desktop environment, but I change the format of several things because I don't use the metric system, and I need the Euro sign and normal dates. Sorry, but month, day, and year is a weird format.

The "normal" thing would be to use my country format. But if I select a format from Spain, I get dates in Spanish and in a format that I also hate:

What I want is ISO8601 and English. But I don't want to modify each field manually. Too much. The weird trick is to use Denmark (English). I am not kidding. And I am not alone. At all.

Why, you may ask? Look at this beauty. It's just perfect.

Anyway. My problem is with Thunderbird. It looks like it doesn't support having a language and a format from different regions. Thankfully they documented it here.

So now, I have:

• intl.date_time.pattern_override.date_short set to yyyy-MM-dd

• intl.date_time.pattern_override.time_short set to HH:mm

I guess I might need more stuff, but at least for now I don't see a weird date when I am answering emails.

---

P.D: Talking about weird things I like to configure… My keyboards are ANSI US QWERTY. But the layout I use is English (intl., with AltGr dead keys). So I can type Spanish letters using the right alt and a key (e.g: AltGr + n gives me ñ).

05 Nov 2025 8:15am GMT

Last week, as I was writing my trip report about the Google Summer of Code Mentor Summit, I found myself going on a tangent about the program in our community, so I decided to split the content off into a couple of posts. In this post, I want to elaborate a bit on our goal with the program and how intern selection helps us with that.

I have long been saying that GSoC is not a "pay-for-code" program for GNOME. It is an opportunity to bring new contributors to our community, improve our projects, and sustain our development model.

Mentoring is hard and time consuming. GNOME Developers heroically dedicate hours of their weeks to helping new people learn how to contribute.

Our goal with GSoC is to attract contributors that want to become GNOME Developers. We want contributors that will spend time helping others learn and keep the torch going.

Merge-requests are very important, but so are the abilities to articulate ideas, hold healthy discussions, and build consensus among other contributors.

For years, the project proposal was the main deciding factor for a contributor to get an internship with GNOME. That isn't working anymore, especially in an era of AI-generated proposals. We need to up our game and dig deeper to find the right contributors.

This might even mean asking for fewer internship slots. I believe that if we select a smaller group of people with the right motivations, we can give them the focused attention and support to continue their involvement long after the internship is completed.

My suggestion for improving the intern selection process is to focus on three factors:

• History of Contributions in gitlab.gnome.org: applicants should solve a few ~Newcomers issues, report bugs, and/or participate in discussions. This gives us an idea of how they perform in the contributing process as a whole.
• Project Proposal: a document describing the project's goals and detailing how the contributors plans to tackle the project. Containing some reasonable time estimates.
• An interview: a 10 or 15 minutes call where admins and mentors can ask applicants a few questions about their Project Proposal and their History of Contributions.

The final decision to select an intern should be a consideration of how the applicant performed across these aspects.

Contributor selection is super important, and we must continue improving our process. This is about investing in the long-term health and sustainability of our project by finding and nurturing its future developers.

If you want to find more about GSoC with GNOME, visit gsoc.gnome.org

04 Nov 2025 12:54pm GMT

It's worth reflecting on the process of public speaking. Many of us who are practitioners in a field see leaders or well-known figures present and we compare ourselves. That comparison isn't always fair. When an executive stands on stage, they often have an entire team of writers, marketers, and coaches who helped refine the message, build the slides, and critique the delivery. They have access to professional teleprompters and structured practice sessions. Other times, they are in roles where public speaking is a specifically defined function and they have time built into their calendar for preparing and delivering talks. For the rest of us, trying to self-organize that level of time can be difficult and getting that kind of support is a huge ask of friends and colleagues.

My experience delivering my first invited keynote at OpenAlt 2025 this past weekend was a perfect case study in the practitioner's reality. This post is a look behind that curtain.

The journey began on a compressed timeline, with just over a week from final confirmation to delivery. The organizers asked for a talk on community and collaboration - a "fuzzy" message that is challenging to nail without a team to brainstorm and refine it with. To this goal they added the request that people leave the talk feeling excited about the conference, even if they didn't "learn anything new." This is the first hurdle for the practitioner: you are your own strategist, writer, and editor.

Then came the realities of life. The preparation week was a chaotic mix of school holidays and a sick child. While introducing my daughter to Star Wars was a joy, it meant that talk preparation happened in fragmented bursts, often late at night. Not a complaint - it's the environment in which most of us do this "extra" work.

I developed a habit of not using slides when there is no real visual requirement for the message. I feel like it focuses both the audience and me on the message of the talk. This was that kind of talk. To manage the terror of speaking without slides, I wrote a full script. But my delivery aids were DIY and not a professional setup. I tried using an iPad instead of printed notes, which turned out to be a mistake. Paper is static and aids spatial memory, while the iPad's scrolling and flawed teleprompter mode were more of a distraction than a help. This is another practitioner reality: we make do with the tools we have, and sometimes learn lessons the hard way.

When it's time to present, last-minute changes and diversions start piling up. A sudden request to introduce myself, or help craft an intro to be said by someone else, required an on-the-fly pivot before the talk even began. Throughout the talk, I made small adjustments and ad-libs to match the energy of the room. The script isn't designed to be read, instead it internalizes the themes and points for me and helps me hit my time goals. The time goal is always a factor when you finally give the talk. When you're not reading a script, there's a temptation to pull in discarded material and risk a rushed ending.

In the end, the talk, "Bring Wood for the Fire," was a success. I received positive feedback from attendees able to cite specific comments that resonated with them, not just generic platitudes. The organizers let me know that I exceeded their goals and they are pleased with the final product. I'm proud that the core message held strong despite the chaotic process and live detours. It tells me I developed a solid message and then internalized the narrative, which is a speaker's ultimate goal. As a practitioner, I may not have a team of professionals, but I can know my story inside and out.

Key takeaways

• Prepare a tight script when skipping slides - it helps you keep time and structure.
• Use static notes (paper or static electronic notes) for spatial memory; avoid scrolling teleprompters unless you're used to them and they sit naturally in your sightline.
• Internalize the narrative so you can adapt and ad-lib without losing the core message.
• Expect last-minute pivots; prepare a flexible intro and a short fallback.

So when you watch a polished keynote, appreciate the craft, but don't use it as a stick to beat yourself with. As practitioners, our process is different. It's messier, more chaotic, and intensely personal. And succeeding within those constraints is a victory worth celebrating.

A recording of the talk, including Czech subtitles, is available on the conference's PeerTube instance. An alternate version is also available on Youtube. I appreciate the organizers uploading these so quickly and for doing the translation.

Note: Updated on 5 November 2025 with the PeerTube Link.

04 Nov 2025 12:50pm GMT

RPMs of Redis version 8.4-rc1 are available in the remi-modular repository for Fedora ≥ 41 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

⚠️ Warning: this is a pre-release version not ready for production usage.

1. Installation

Packages are available in the redis:remi-8.4 module stream.

1.1. Using dnf4 on Enterprise Linux

# dnf install https://rpms.remirepo.net/enterprise/remi-release-<ver>.rpm
# dnf module switch-to redis:remi-8.4/common

1.2. Using dnf5 on Fedora

# dnf install https://rpms.remirepo.net/fedora/remi-release-<ver>.rpm
# dnf module reset  redis
# dnf module enable redis:remi-8.4
# dnf install redis --allowerasing

You may have to remove the valkey-compat-redis compatibilty package.

2. Modules

Some optional modules are also available:

• RedisBloom as redis-bloom
• RedisJSON as redis-json
• RedisTimeSeries as redis-timeseries

These packages are weak dependencies of Redis, so they are installed by default (if install_weak_deps is not disabled in the dnf configuration).

The modules are automatically loaded after installation and service (re)start.

The modules are not available for Enterprise Linux 8.

3. Future

Valkey also provides a similar set of modules, requiring some packaging changes already proposed for Fedora official repository.

Redis may be proposed for unretirement and be back in the Fedora official repository, by me if I find enough motivation and energy, or by someone else.

I may also try to solve packaging issues for other modules (e.g. RediSearch). For now, module packages are very far from Packaging Guidelines, so obviously not ready for a review.

4. Statistics

redis

redis-bloom

redis-json

redis-timeseries

04 Nov 2025 12:48pm GMT

The official dates and location are set for Flock to Fedora 2026, the premier annual conference for Fedora Project contributors. The event will take place from 14-16 June 2026, in Prague, Czechia.

For Flock 2026, we are returning to the Vienna House by Wyndham Andel's Prague, located at:

Stroupeznickeho 21
Prague, 150 00
Czech Republic

While all three days will be full conference days, the arrangement of the schedule will change slightly in 2026. Sunday, 14 June, will be designated as Day 0, featuring workshops, team meetups, and hands-on contributor sessions. The main conference activities, including streamed content, the opening keynote, and other sessions, are scheduled for Monday, 15 June, and Tuesday, 16 June.

Coordinated Scheduling with DevConf CZ

Following community feedback from last year, Flock 2026 has been scheduled to align more closely with DevConf.CZ. The conference will conclude just before DevConf.CZ begins in Brno (18-20 June 2026). This compressed travel schedule is intended to make it easier for community members who wish to attend both events.

Call for Proposals & Conference Themes

The Call for Proposals (CFP) for Flock 2026 will open in early December 2025 and close shortly after FOSDEM 2026 (31 January - 1 February). Speaker confirmations are scheduled to be sent in March 2026.

For Flock 2026, we are taking a more focused approach to session content. The Fedora Council, FESCo, and the Mindshare Committee are shaping key themes for the CFP. All presentation and workshop submissions should align with one of these themes. More details will be shared when the CFP opens.

Planning for Flock 2026

Here is what you need to know to plan your attendance:

• Registration: Conference registration is scheduled to open in January 2026.
• Sponsorship: Is your company or organization interested in sponsoring Flock 2026? Our sponsorship prospectus for Flock 2026 is now available on the Flock 2026 website. Organizations interested in supporting Flock and the Fedora community are encouraged to review the prospectus and contact the organizing team with any questions.
• Hotel Block: A discounted block of rooms is arranged at the conference hotel. More information about the discounted hotel block can be found on the Flock website.
• Travel Day & Connections: 17 June is designated as a free travel day between Flock to Fedora 2026 and DevConf.CZ. Frequent bus and train connections are available for travel between Prague and Brno.
• Sponsored Travel: We intend to offer sponsored travel again for Flock to Fedora 2026. More details will follow in December 2025.

Get Involved & Ask Questions

The official Flock to Fedora 2026 Matrix room, #flock:fedoraproject.org, is the best place to connect with organizers and other community members. We encourage you to join the channel for the latest updates and to ask any questions you may have.

Flock to Fedora 2026 web site

A Note on Our Flock to Fedora 2026 & 2027 Plans

We recognize that returning to the same city and venue for a second consecutive year is a departure from Flock's tradition. This decision was made intentionally with two key goals in mind.

First, by working with a familiar venue, our organizing team can optimize its processes and plan further in advance. This stability for Flock to Fedora 2026 will give us more opportunity to improve our internal processes and explore new ways to incorporate community input into the design of Fedora's flagship contributor conference.

Second, this allows us to plan for a significant change in 2027. The Flock organizing team is committed to exploring new locations for Flock 2027, with a particular focus on regions outside of North America and Europe. We acknowledge the travel difficulties many of our contributors in regions like LATAM and APAC face. We learned valuable lessons from past planning cycles and are eager to achieve this goal, while also recognizing that unforeseen circumstances can impact our plans. We will work with community members in these regions to explore possible options and conduct thorough research on pricing and availability for 2027.

We look forward to seeing you in Prague for Flock 2026, 14-16 June.

- The Flock to Fedora Planning Team

04 Nov 2025 8:00am GMT

02 Nov 2025 7:52pm GMT

I didn't do a recap last week (because I was on PTO on friday and monday) and thought about not doing one today either (I was on PTO friday/yesterday), but I thought of a few good items to talk about. :)

01 Nov 2025 5:25pm GMT

31 Oct 2025 1:00pm GMT