Hey <!channel>! :wave: We would like to invite y...
# announcements
a
Hey <!channel>! 👋 We would like to invite you to join our upcoming webinar on “Mastering authorization in Fintech” 💻 Edgar Rivera and Daniel "phrawzty" Maher will walk through how to map business requirements of fintech products to authorization logic, accounting for dynamic trading rules, global market windows, and real-time risk assessment. Then they’ll show how to manage that complexity without cluttering your codebase or making things harder to maintain. May 6, 2025 at 5pm CEST / 8am PDT 🔗 👉 Register for the webinar here 📩 Recording available for all registrants
cerbie 4
👍 1
🌟 2
👍🏼 1
a
Hi, Anna. There seems to be no definitive link to select to register for the webinar. Maybe I've missed it, but I had a relook and it still eludes me. Please advise, thanks.
a
Hey @Andre Du Plessis! Here’s the link https://www.cerbos.dev/ebooks-webinars/mastering-authorization-in-fintech 😊 Thanks for the comment, will make an update to original post so it’s more visible 💪
a
Awesome, thank you!
Oops, ok, maybe it's Firefox, but it's the same page as per your original post by the looks of it. Where it says "register for the webinar" there's no actionable link. Let me go test it in Chrome quickly.
It seems to be Firefox & DDG causing issues. The fields to complete one's details simply do not appear as they do in Chrome. My bad.
d
@Andre Du Plessis 👋 I just tested in Firefox 137.0.2 (my daily driver fwiw) and the registration element appears as expected. What version/platform are you on?
a
Hi @Daniel Maher. I'm on Win 10, FF Dev 138.0b9, using DuckDuckGo as SE. I've had similar issues with other sites now and then, and sometimes the combination together with a few tweaked settings (which I sometimes forget about while using it as my go-to) seems to cause "weird-looking/behaving" issues once in a while. "Content blocking" was the cause in this case. It's not a problem, but I was quite surprised to notice that the <div id="webinar-form-1"></div> remains completely "mute", even when I try finding the form elements using the dev inspector drill-down on my browser stack, till I noticed the warning and err rep about the reasons behind the apparent fail after inspecting it. All sorted, I quickly completed the registration via Chrome yesterday.